EIBM LANDD: A failure occurred during initialization.
EThe protocol manager could not be opened. The return code is %1.
EThe protocol manager would not accept a request.
EThe protocol manager would not supply a configuration image.
EThe protocol manager would not accept module registration.
ENo MAC driver bindings were specified in PROTOCOL.INI. IBM LANDD did not load.
EThere are too many MAC drivers to bind. IBM LANDD did not load.
EThere are more values specified for keyword %1 than allowed. IBM LANDD did not load.
ESystem resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM IEEE 802 (LANDD) did not load.
EThe value specified as the node address for MAC %1 is not a valid hexadecimal number.
EThe value specified for the node address is not valid for adapter %1. IBM LANDD did not load.
EThe ETHERAND parameter configured for adapter %1 is not DIX or 802.3. IBM LANDD did not load.
EThe unrecognized keyword %1 was found in PROTOCOL.INI.
EA value is required for keyword %1 in PROTOCOL.INI.
EThe value specified for parameter %1 is not valid.
EThe value specified for parameter %1 is not valid.
EDuplicate parameter %1 was found in PROTOCOL.INI.
EThe IBM LANDD section was not found in PROTOCOL.INI.
EThe LANMSGDD device driver could not be opened. The return code is %1.
EAn unexpected error was returned from a SetTimer request.
EAn unexpected error was returned from a request to allocate GDT selectors. The return code is %1.
EAn unexpected error was returned from a request to map GDT selectors. The return code is %1.
EAn unexpected error was returned from a PhysToVirt request. The return code is %1.
EAn unexpected error was returned from a PhysToVirt request.
EAn unexpected error was returned from a GetDOSVar request.
EThe operating system installed is not compatible with this program.
EAn unexpected error was returned when the program tried to lock a memory segment.
EAn unexpected error was returned from a VirtToPhys request.
EAn unexpected error was returned when the program tried to allocate memory for the group SAP receive Buffer. The return code is %1.
EAn unexpected error was returned when the program tried to request a GDT for the group SAP recieve buffer.
EThe system is unable to map the group SAP receive buffer to a GDT. The return code is %1.
EThe %1 MAC is an 802.3 protocol but is configured for DIX.
EThe %1 MAC is a DIX protocol but is configured for 802.3.
EThe %1 MAC will not accept the configured node address.
EThe %1 MAC was not able to bind. Return Code = %2.
WAn unexpected error occurred when the program tried to set the %1 MAC packet filter.
WAn unexpected error occurred when the program tried to set the %1 MAC lookahead size.
WAn error occurred when the program tried to set the %1 MAC node address.
WIBM LANDD was unable to open the %1 MAC driver.
WIBM LANDD received an open adapter request before the %1 MAC bind completed.
IIBM LANDD was successfully bound to MAC: %1%2%3.
EIBM LANDD encountered an internal error when the program attempted to reference %1 MAC by the logical adapter number.
EDuplicate node addresses exist on the network for %1 MAC.
IAdapter %1 was initialized and opened successfully.
IAdapter %1 is using node address %2.
IIBM LANDD is accessing IBM %1 LAN Interface.
IAdapter %1 is using node address %2. The Token-Ring format is %3.
EAn unexpected error was returned when the program tried to transmit the duplicate node address test. The %1 MAC return code is %2.
EThe OpenAdapter request to the %1 MAC Driver did not complete within the required time limit.
EAn error occurred while attempting to load NETBEUI.
EThere is no section for NETBEUI in PROTOCOL.INI.
INETBEUI: Using a 32-bit data segment.
IIBM OS/2 NETBIOS %1
EA version of the redirector was detected that is not compatible with the version of NETBIOS %1.
EThe configuration parameters defined in PROTOCOL.INI exceed the 64KB work area. NETBIOS %1 support has ended.
INETBIOS %1 is loaded and operational.
IIBM OS/2 NETBEUI %1
IAdapter %1 has %2 NCBs, %3 sessions, and %4 names available to NETBIOS applications.
IPress Enter to continue.
IIBM OS/2 LANMSGDD %1 is loaded and operational.
WThe default path is not valid. The default directory will be changed to the root directory.
EAn error occurred while attempting to open or write to file %1. Check for insufficient disk space.
WFFST/2 is installed but is not started. LANTRAN.LOG is being created.
IVector
IIBM OS/2 LANDLLDD %1 %2
EThe IBM LANDD device driver is not installed.
EAn unexpected error was returned from an AllocPhys request.
EAn unexpected error was returned from a DosGetInfoSeg request.
EAn unexpected error was returned from a PhysToGDT request.
IIBM OS/2 LANDLLDD is loaded and operational.
EIBM OS/2 LANDLLDD is not installed.
EIBM OS/2 LANDLLDD: There is not enough memory available for CCB3 areas.
EAdapter %1: NETBIOS is not operational.
ENo configuration section was found in the PROTOCOL.INI file for either NETBIOS or NETBEUI.
ENETBIOS does not recognize device driver %1.
EAn error occurred when the program tried to open network device driver %1.
EA syntax error was detected for ADAPTER %1 in the NETBIOS section of PROTOCOL.INI.
ENo MAC driver bindings were specified in PROTOCOL.INI. IBM NETBEUI did not load.
EThere are too many MAC drivers to bind. IBM NETBEUI did not load.
ESystem resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM NETBEUI did not load.
EAn unexpected error was returned from a request to allocate GDT selectors. The return code is %1.
EThe operating system installed is not compatible with this program.
EThe value specified for the node address is not valid for adapter %1. IBM NETBEUI did not load.
EMore values than allowed are specified for keyword %1. IBM NETBEUI did not load.
WNETBIOS name-in-conflict was received for NETBIOS local name %1 (ASCII format). The name-in-conflict frame was transmitted by node address %2.
I%1 %2 %3
WA NETBIOS name-in-conflict has occurred. The same NETBIOS name was detected at node addresses %1 and %2.
WA request to use a free NETBEUI GDT selector failed. The resource is not available.
WA NETBIOS link was disconnected because a NETBIOS acknowledgment was not received within the response timer (T1) value.
WNETBEUI has been notified of a change in network status. A critical network status notification may cause the adapter to close.
WA request to use a free NETBEUI UI-Frame descriptor failed. The resource is not available.
WNamecaching has been disabled because insufficient datagrampackets have been configured.
EAn error occurred while attempting to load TCPBEUI.
EThere is no section for TCPBEUI in PROTOCOL.INI.
ITCPBEUI: Using a 32-bit data segment.
IIBM OS/2 TCPBEUI %1
ENo MAC driver bindings were specified in PROTOCOL.INI. IBM TCPBEUI did not load.
EThere are too many MAC drivers to bind. IBM TCPBEUI did not load.
ESystem resources are not available to hold the current parameter configuration in PROTOCOL.INI. IBM TCPBEUI did not load.
EAn unexpected error was returned from a request to allocate GDT selectors. The return code is %1.
EThe operating system installed is not compatible with this program.
EThe value specified for the node address is not valid for adapter %1. IBM TCPBEUI did not load.
EMore values than allowed are specified for keyword %1. IBM TCPBEUI did not load.
EErrors occurred while attempting to initialize TCPBEUI.
ITCPBEUI: completed initialization and is bound to TCP/IP network interface %1.
ETCPBEUI: Domain Name Server not found but DOMAINSCOPE was specified in PROTOCOL.INI.
ITCPBEUI: Logical adapter %1 is bound to TCP/IP interface %2.
ETCPBEUI: Error mapping TCPBEUI bindings to TCP/IP bindings.
ETCPBEUI: The TCP/IP loopback address is not defined.
ITCPBEUI: Logical adapter %1 is trying to bind to TCP/IP interface %2.
WTCPBEUI: A name-in-conflict has been reported for local name %1 from address %2.
WTCPBEUI: A name-in-conflict has been detected for remote name %1 at address %2 and address %3.
EAn error occurred while updating the following file: %1 Make sure that this file is not in use in any other OS/2 or DOS session. Return to this session and select Retry to continue configuration. Select Exit if you want
to end configuration.
EAn error occurred while reading the following file: %1 Make sure that this file is not in use in any other OS/2 or DOS session. Return to this session and select Retry to continue configuration. Select Exit if you want
to end configuration.
EAn error occurred while copying from subdirectory %1 to subdirectory %2. Make sure that files being copied are not in use in either of these subdirectories in any other OS/2 or DOS session. Return to this session and select
Retry to continue configuration. Select Exit if you want to end configuration.
EThe value for the %1 field must be between %2 and %3. (or) The value for the %1 field must be one of the following: (or) The value for the %1 field must be between %1 and %2 in steps of %3. (or) The length of the %1 field cannot
be longer than %2 characters.
EThe PROTOCOL.INI file was not found at the path specified. Select OK and respecify the full path.
EThe network adapter drivers were not found at the path specified. Select OK and respecify the full path.
EAll LAN Adapter and Protocol Support combinations in the Current Configuration list must contain at least one protocol driver. Select OK and make sure all combinations are complete.
EYou have selected to change a network adapter that has a protocol driver associated with it. You must remove all associated protocol drivers before removing this network adapter.
EYou cannot have duplicate logical adapter numbers for a protocol driver using multiple network adapters. Select OK and then change one or more of the adapter numbers.
EA decimal number must be entered. (or) A hexadecimal number must be entered.
EAn error occurred while attempting to update %1.
EAn error occurred while attempting to read %1.
EAn error occurred while copying from subdirectory %1 to subdirectory %2.
EThe configuration parameters supplied to LTSVCFG are incorrect. Defaults will be used for all adapters.
EIBM LANVDD: A request for internal memory failed.
EIBM LANVDD: A failure has occured which prevents LANVDD from operating in this Virtual Dos Machine, Int5C support is terminated for this VDM.
EThe 802.2 protocol stack and the NetBIOS device drivers are not available. Virtual NetBIOS and Virtual 802.2 support are not available to VDMs.
IIBM LANVDD is loaded and operational.
ELANPDD was unable to register with the Virtual Dos Machine Manager.
IIBM LANPDD is loaded and operational.
EA failure occurred which has prevented %1 from being installed.
EIBM LANVDD: The system could not obtain or map a GDT Selector.
EThe number of Dos Sessions which LANVDD can support has been exceeded.
EThe Virtual Dos Machine Manager could not allocate a Software Hook required for LANVDD's internal operations.
EThe operating system installed is not compatible with this program.
E The OS/2 802.2 device driver, LANDD.OS2, is not available. DOS 802.2 support is ended for all VDMs.
I*** No DOS 802 Status Memory Elements are available.
E LANVDD.OS2 was unable to map a virtual address to a linear address in system memory.
E A status indication was received for an unknown application ID.
E A status indication was lost or ignored.
E LANVDD is unable to access DOS memory.
E The maximum number of OS/2 802.2 user applications was reached.
E The maximum number of OS/2 802.2 SAPs was reached.
E LANVDD was unable to allocate the requested OS/2 SAP buffers.
E LANDD did not complete a LANVDD BufferFree request successfully.
E LANVDD was unable to allocate internal memory elements.
E A LANVDD buffer allocation request was cancelled.
E LANVDD received a DLC status indication for a SAP that LANVDD did not open.
E LANVDD was unable to simulate local busy to a DOS application.
(.txt)