ÿMKMSGFLTGdçêíðóöùüÿ  #&)ì’y—n q r Õ Ø Š ƒŽ‘”z$ãæÍÎ*Ö›ž¡¤§ªÖ!$$e%6(\*¾,É-ú/Ý0à0ã0R23‚3…3ˆ3‹3Ž3á4ä4ç4ê4í4ð4ó4ö4ù4ü4ÿ455:6Ø7Þ9Ò:¹<¼<¿< =³=¶=Í?V@öBùB¬DAF? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ICause: This is a generic initialization failure message. If the IBMTOKCS device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message. User Action: Resolve the specific error message that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.OS2, is located in the \IBMCOM directory, and that a DEVICE statement for PROTMAN.OS2 exists in the CONFIG.SYS file. ICause: The parameter displayed was found while processing the Token-Ring Network Driver section of PROTOCOL.INI. The parameter is not valid. User Action: Correct the parameter or remove it from PROTOCOL.INI. ICause: The value provided for the parameter is not the correct type or is not a valid value. User Action: Change the value for the parameter in PROTOCOL.INI. ICause: Conflicting parameter values were found while processing the Token-Ring Network Driver section of PROTOCOL.INI. User Action: Examine the configuration parameters and correct the conflicting values in PROTOCOL.INI. ICause: One of the following conditions has caused this error. - The logical primary/alternate setting in the PROTOCOL.INI file does not map to the physical primary/alternate setting. - The adapter is not responding to a request to start. - There is no physical adapter in this machine. User Action: If there is already an adapter in this system, check the logical primary/alternate setting. Check the cable and ensure that the connection to the token-ring network addressable unit (NAU) is functioning properly. Then run the hardware diagnostics for the token-ring adapter to ensure that the adapter and options are correctly installed. If there is no adapter in this machine, install a token-ring adapter or remove the device driver statement from the CONFIG.SYS file. ICause: An unexpected error occurred when the program attempted to open the protocol manager. User Action: Check the drive and directory to ensure that the protocol manager is located in the specified path. ? ICause: The Token-Ring Network adapter encountered a wire fault. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The requested DIR.OPEN.ADAPTER parameter has not allowed enough receive buffer space in the adapter shared RAM area. Action: Reduce the RAM requirements by reconfiguring the parameters in PROTOCOL.INI. The parameters that will reduce the space requirements for the receive buffer are the transmit buffers (if more than 1 is specified). ? ICause: The node address defined is not valid. Action: Specify a valid node address. Refer to the Token-Ring network arhitecture reference for node address restrictions. ICause: The receive buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8. Action: Specify a valid receive buffer length. ICause: The adapter transmit buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable maximum, less than the allowable minimum, or not a multiple of 8. Action: Specify a valid adapter transmit buffer length. ? ? ICause: The adapter was closed because of an unexpected error condition. Action: See the message log, LANTRAN.LOG, for additional information about this error. The error must be corrected before you can use this adapter. ICause: The Token-Ring Network adapter has either detected a monitor contention failure or received a beacon frame from the ring. The problem may be that your adapter speed is different from the speed at which the LAN is running. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: A command forcing the adapter to remove itself from the ring was received. Action: Contact your LAN personnel to determine why the REMOVE command was issued for your machine. ? ICause: The Token-Ring Network adapter has detected a problem on your local lobe between the adapter and the Multistation Access Unit (MSAU). Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The Token-Ring Network adapter has detected one of the following open errors while trying to insert into the LAN: - Ring Failure - Ring beaconing - Timeout Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The Token-Ring Network adapter has detected one of the following open errors during the address verification phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - Duplicate node - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The Token-Ring Network adapter has detected one of the following open errors during the roll call poll phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your system coordinator. ICause: The Token-Ring Network adapter has detected one of the following open errors during the request parameter phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - Parameter request - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ? ? ? ? ? ICause: The Token-Ring Network adapter has detected a lobe media failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The Token-Ring Network adapter has detected a signal loss failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ? ICause: The Token-Ring Network adapter has detected an incorrect ring speed while trying to open the adapter. Action: 1. Add or change the RINGSPEED parameter in PROTOCOL.INI to the correct speed. 2. Add the keyword AUTORINGSPEED to the IBMTOKCS_nif section in PROTOCOL.INI. The adapter will then adjust itself to the proper ring speed. ICause: The Token-Ring Network adapter has detected an insertion timer expiration while trying to open the adapter. This condition indicates that the ring may be congested, experiencing a high bit-error rate, or is losing an unusually high number of tokens or frames. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The Token-Ring Network adapter has detected a ring failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The Token-Ring Network adapter has detected a monitor contention failure or has received a beacon frame from the ring while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The Token-Ring Network adapter has detected a that another station on the ring has an adapter address equal to the address specified for your adapter. Action: Note the identification number of this message and then contact your system administrator. ICause: The Token-Ring Network adapter has detected a parameter request error while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: While attempting to insert into the ring, a command forcing this adapter to remove from the ring was received. Action: Contact your LAN personnel to determine why the REMOVE command was issued for your machine. ? ? ICause: Your workstation is the first station attempting to insert onto the ring in AUTORINGSPEED mode. Action: 1. Either remove the AUTORINGSPEED keyword from PROTOCOL.INI or make sure another workstation is on the network and has set the ring speed. 2. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: Physical insertion of your workstation onto the ring failed. Action: 1. Check the adapter configuration and retry the open request. 2. If the problem persists, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ? ? ? ? ? ICause: A problem was detected on micro-code level "00 00 00 C2 45 50". Action: Request and install engineering change ECA0066, part# 92F9122, on your system, or use the configuration feature of the Lan Adapter and Protocol Support installation program to change the value for the number of transmit buffers to be greater than 1. ? ? ? ? ? ? ? ? ? ? ? ? ECause: Card Services would not give IBMTOKCS access to the I/O ports it requested. Action: Make sure that no other adapters are using the range of I/O ports the Token-Ring card needs. For a primary Token-Ring adapter the range is A20-A23. For an alternate Token-Ring adapter the range is A24-A27. ECause: Card Services would not give IBMTOKCS access to the interrupt request line (IRQ) it requested. Action: Make sure that no other adapters are using the IRQ requested. IBMTOKCS defaults to IRQ 9. To change the IRQ IBMTOKCS uses, add the line INTERRUPT=X to your PROTOCOL.INI file. X can be any one of the following values: 3,4,5,7,9,10,11. The IRQ chosen should not be used by any other device. ECause: Card Services would not give IBMTOKCS access to the shared RAM memory window it requested. Action: Make sure that no other adapters are using the memory window requested. IBMTOKCS defaults the RAM memory window to D800 for the primary adapter or D400 for the alternate adapter. To change the RAM memory window, add the line RAM=XXXX to your PROTOCOL.INI file. XXXX can be any un-used 8k, 16k, 32k, or 64k region in the range C000-DC00. You may also have to adjust the RAMSIZE keyword accordingly. ECause: Card Services would not give IBMTOKCS the configuration it requested. Action: Try a different interrupt line by using the INTERRUPT=X statement in your PROTOCOL.INI file. X can be any un-used interrupt line in the range 3-15. ECause: Card Services would not map the shared RAM memory on the adapter to the requested memory window. Action: Try changing the RAM memory window. IBMTOKCS defaults the RAM memory window to D800 for the primary adapter or D400 for the alternate adapter. To change the RAM memory window, add the line RAM=XXXX to your PROTOCOL.INI file. XXXX can be any un-used 8k, 16k, 32k, or 64k region in the range C000-DC00. You may also have to adjust the RAMSIZE keyword accordingly. ? ? ECause: Card Services would not register the Token-Ring Credit Card Adapter callback handler. ECause: Card Services could not be found. Action: Add the approriate statements to your CONFIG.SYS file so that Card Services is installed. ? ECause: The Card Services function GetCardServicesInfo reported that there are no sockets in your workstation. This can be caused by any of the following: 1. Socket Services not installed, or installed incorrectly; 2. No physical sockets on your workstation. 3. No adapter with sockets installed, or installed incorrectly Action: 1. Make sure you have Socket Services installed correctly. 2. Make sure your workstation has physical sockets. 3. Make sure you have installed the adapter card correctly. ICause: A Token-Ring Credit Card Adapter was not found in any socket in your workstation. Action: Insert the adapter in a socket. ECause: You attempted to boot your workstation without a Token-Ring Credit Card Adapter inserted in a socket. Action: Either insert the adapter in a socket and reboot your workstation, or add the NETADDRESS= parameter to PROTOCOL.INI and reboot your workstation. By adding the NETADDRESS paramater you can insert the Token-Ring Credit Card Adapter after boot up. Make sure the address you use is either a locally administered address or the universallly administered address burned in on your adapter. To find out your universally administered address, run the diagnostics program that is on the diskette that came with your Token-Ring Credit Card Adapter. ? ECause: Card Services would not give IBMTOKCS access to the MMIO memory window it requested. Action: Make sure that no other adapters are using the memory window requested. IBMTOKCS defaults the MMIO memory window to CC00 for the primary adapter or DC00 for the alternate adapter. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any un-used 8k region in the range C000-DC00. ECause: Card Services would not map the MMIO memory on the adapter to the requested memory window. Action: Try changing the MMIO memory window. IBMTOKCS defaults the MMIO memory window to CC00 for the primary adapter or DC00 for the alternate adapter. To change the MMIO memory window, add the line MMIO=XXXX to your PROTOCOL.INI file. XXXX can be any un-used 8k region in the range C000-DC00. ECause: PROTOCOL.INI did not have a section with a DriverName=IBMTCS$ keyword. A common cause of this is not using LAPS to install new drivers. Action: Use LAPS to install the new PCMCIA Token-Ring Adapter Driver.