MKMSGFLT8/258;>ADGJMPSVY\_behknqtwz}  "%(+.147:=@CFILORUX[^adgjmpsvy|  !$'*-0369<?BEHKNQTWZ]`cfilorux{~ L UCFIL6h!"4$&'^)a)d)g)j)m)p)s)v)y)|)))))))))))))***++U--L..00'223? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ICause: The attempt to add this MLID protocol ID has failed. The IBM NetWare* Requester Support (ODI2NDI.OS2) will not work. Action: You may have too many protocol IDs defined. Delete those protocol IDs that are not required. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The attempts by IBM NetWare* Requester Support (ODI2NDI.OS2) to obtain memory from OS/2 failed. Action: Contact an IBM service representative. * NetWare is a registered trademark of Novell, Inc. ? ? ? ? ICause: The IBM NetWare* Requester Support (ODI2NDI.OS2) driver was unable to locate the LSL support module. This error usually indicates that the NetWare* Requester is not installed. Action: Ensure that the NetWare* Requester is installed. Also, verify that the LSY.SYS driver statement is in the CONFIG.SYS file and that it precedes the ODI2NDI.OS2 driver statement. An example follows: : DEVICE=\LSL.SYS DEVICE=\DDAEMON.EXE : DEVICE=C:\IBMCOM\ODI2NDI.OS2 : DEVICE=\IPX.SYS : Also ensure that the LSL.SYS driver loaded without errors. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ? ? ? ICause: IBM NetWare* Requester Support (ODI2NDI.OS2) was unable to specify which frames to receive. Action: Some NDIS MAC drivers do not support setting the MAC packet filter. This may be the case for the NDIS MAC driver that you are using. Also, ensure that the MAC driver has loaded and initialized properly and that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The IBM NetWare* Requester Support (ODI2NDI.OS2) has tried to specify the amount of data in the frame that ODI2NDI.OS2 requires to be available for interrogation of the frame. This action will ensure that the frame is owned ODI2NDI.OS2. Action: Some NDIS MAC drivers do not support the setting of this size. This may be the case for the NDIS MAC driver that you are using. Also, ensure that the MAC driver has loaded and initialized properly and that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The attempt by IBM NetWare* Requester Support (ODI2NDI.OS2) to set the node address for the specified adapter was unsuccessful. This error might occur if another protocol, for example IBM 802.2, has set the node address to a value different from the node address configured for ODI2NDI.OS2. Action: Use the LAPS installation program to ensure that all protocols configured to use the adapter are configured for the same node address. If the IBM IEEE 802.2 protocol is configured to use the adapter, but only ODI2NDI.OS2 has the node address configured, ODI2NDI.OS2 should be configured to use the adapter's universal address. Also, some NDIS MAC drivers do not support the setting of a local address. This may be the case for the NDIS MAC driver that you are using. Finally, ensure that the MAC driver has loaded and initialized properly and that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The attempt by IBM NetWare* Requester Support (ODI2NDI.OS2) to open the specified adapter was unsuccessful. Action: Use the LAPS installation program to ensure that the MAC driver has loaded and initialized properly. Also verify that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ? ICause: IBM NetWare* Requester Support (ODI2NDI.OS2) has tried bind to the NDIS MAC driver as specified in the current LAPS configuration but was unsuccessful. Action: Use the LAPS installation program to ensure that the MAC driver has loaded and initialized properly. Also verify that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare* is a registered trademark of Novell, Inc. ? ? ? ICause: IBM NetWare* Requester Support (ODI2NDI.OS2) tried to open the specified adapter, but the open has not yet completed. Action: Ensure that the MAC driver has loaded and initialized properly and that the hardware associated with the MAC driver is operational. Check for any messages that the MAC driver may have displayed or logged. See the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG * NetWare is a registered trademark of Novell, Inc. file. ICause: IBM NetWare* Requester Support (ODI2NDI.OS2) has not been configured in the current LAPS configuration. Action: Use the LAPS installation program to configure IBM NetWare* Requester Support or remove the ODI2NDI.OS2 device driver statement from the CONFIG.SYS file. * NetWare is a registered trademark of Novell, Inc. ICause: IBM NetWare* Requester Support (ODI2NDI.OS2) has not been configured in the current LAPS configuration. Action: Use the LAPS installation program to configure IBM NetWare* Requester Support. * NetWare is a registered trademark of Novell, Inc. ICause: The IBM NetWare* Requester Support (ODI2NDI.OS2) was configured for too many adapters. ODI2NDI.OS2 can be configured for a maximum of 4 adapters. Action: Use the LAPS installation program to decrease the number of network adapters for which IBM NetWare* Requester Support is configured. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The IBM NetWare* Requester Support (ODI2NDI.OS2) could not find the Protocol Manager (PROTMAN.OS2). Action: Ensure that the following statement is in your CONFIG.SYS file: DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: The IBM NetWare* Requester Support (ODI2NDI.OS2) either could no find the PROTOCOL.INI file or encountered an error while trying to open or read this file. Action: Use the LAPS installation program to ensure that you have configured at least one adapter for IBM NetWare* Requester Support. For additional information, see the FFST/2 message log, if you are using FFST/2, or see the LANTRAN.LOG file. * NetWare is a registered trademark of Novell, Inc. ICause: An error occurred when the IBM NetWare* Requester Support (ODI2NDI.OS2) tried to register with the Protocol Manager. Action: Contact an IBM service representative. * NetWare is a registered trademark of Novell, Inc. ICause: The adapter is configured to use both Token-Ring and Ethernet frame types, which is not allowed. Action: Use the LAPS installation program to ensure that IBM NetWare* Requester Support for the specified adapter is configured to use either Token Ring frame types or Ethernet frame types, but not both. * NetWare is a registered trademark of Novell, Inc. ICause: The frame types configured for IBM NetWare* Requester Support (ODI2NDI.OS2) are not compatible with the MAC driver of the specified adapter. For example, Ethernet frame types have been configured for a Token Ring adapter. Action: Use the LAPS installation program to ensure that IBM NetWare* Requester Support for the specified adapter is configured to use frame types that are supported by the adapter. * NetWare is a registered trademark of Novell, Inc. ICause: The node address configured for IBM NetWare* Requester Support (ODI2NDI.OS2) is not correct. Action: Use the LAPS installation program to ensure that IBM NetWare* Requester Support is configured to use a valid node address. A valid node address consists of 12 hexadecimal digits and may be preceded by an I to indicate IEEE node address format or a T to indicate 802.5 node address format. * NetWare is a registered trademark of Novell, Inc. ICause: The node address was not configured for IBM NetWare* Requester Support (ODI2NDI.OS2) and ODI2NDI.OS2 was unable to obtain the node address automatically from the network adapter at boot time. Action: Use the LAPS installation program to configure the NETADDRESS parameter for IBM NetWare* Requester Support. * NetWare is a registered trademark of Novell, Inc. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ICause: More than one parameter was specified on the NWFIXUP command line. Action: Specify no more than one parameter for NWFIXUP. ICause: More than one parameter was specified on the NWFIXUP command line. Action: Specify no more than one parameter for NWFIXUP. ICause: The filespec supplied as a command-line parameter is not valid. The drive or path specification was incorrect, or the file could not be found. Action: Provide a valid filespec as an argument for the command. ? I Cause: NWFIXUP encountered an error which prevented it from completing all operations successfully. Usually this error occurs when you configure NetWare* Requester Support (ODI2NDI.OS2) prior to installing the NetWare* Requester. Action: Make sure you have the NetWare* Requester installed. Refer to the \OS2\INSTALL\LAPSHIST.LOG file for a more detailed description of the error. * NetWare is a registered trademark of Novell, Inc. ICause: A call to the OS/2 DosQCurDisk function returned with an error. Action: Contact an IBM service representative. ICause: A call to the OS/2 DosQCurDir function returned with an error. Action: Contact an IBM service representative. ICause: A call to the OS/2 DosGetInfoSeg function returned with an error. Action: Contact an IBM service representative. ICause: An error occurred during the attempt to open the CONFIG.SYS file and read it into memory. Action: Ensure that the CONFIG.SYS file being used is not marked as read only and is not currently in use by any other process. Ensure that enough free memory (about 128KB) is available to perform the parsing operation. ICause: A line could not be deleted from the parsed CONFIG.SYS file image. The line contains DEVICE = ODI2NDI.OS2. Action: Contact an IBM service representative. ICause: A line containing DEVICE = LSL.SYS could not be located within the parsed CONFIG.SYS file image. Action: Ensure that the correct CONFIG.SYS file is being used. Also, ensure that the NetWare requester has been installed. If the correct file is being used, and if it contains the LSL.SYS invocation, contact an IBM service representative. ICause: An error occurred during the attempt to add a line to the parsed CONFIG.SYS file image. The line contains DEVICE = ODI2NDI.OS2. Action: Contact an IBM service representative. ICause: An error occurred during the attempt to disable a line in the parsed CONFIG.SYS file image. The REM command could not be prefixed to the line containing DEVICE = . Action: Contact an IBM service representative. ICause: An error occurred during the attempt to replace the CONFIG.SYS file with the revised version. Action: Run CHKDSK to determine whether the problem lies with the file system. If no disk problems are found, contact an IBM service representative.