A.0 Appendix A. Messages
This appendix lists the messages that the LAN Support Program NDIS (LSP
NDIS) driver files can display when being loaded into memory. Messages
originated from LSP NDIS start with DXM.
Three other types of messages may be displayed. These messages are issued
by PROTMAN.DOS (the protocol manager), the NDIS MAC driver, or NETBIND.
Messages generated by PROTMAN.DOS or NETBIND start with PRO00. For
messages displayed by the NDIS MAC driver, please refer to the
Installation and Testing Instructions for your adapter.
A description of some common configuration errors that may cause NDIS
error messages is found in "Common NDIS Configuration Errors" in
topic 6.9.
A.1 Message Format
Figure A-1 shows the format of the sample message:
DXMA0 02E: DOS Version 3.3 or higher required.
The messages are listed in numerical order. See the sections following
this table for descriptions of the LSP NDIS driver, message type, and
message text categories.
+------------------------------------------------------------------------+
| Figure A-1. Message Format |
+-----------+-----------+------------+-----------------------------------+
| LSP NDIS | Message | Message | |
| Driver | Number | Type | Message Text |
+-----------+-----------+------------+-----------------------------------+
| DXMA0 | 02 | E | DOS Version 3.3 or higher |
| | | | required |
+-----------+-----------+------------+-----------------------------------+
A.1.1 LSP NDIS Driver Identifier
The first 5 characters of the message (for example, DXME0) identify the
LSP NDIS driver that originated the message. These drivers are as
follows:
DXMA0MOD.SYS
DXME0MOD.SYS
DXMT0MOD.SYS
DXMJ0MOD.SYS
For a description of these drivers, see "LSP NDIS Driver Summary" in
topic 4.1.
A.1.2 Message Type
The two types of messages are:
E Error
I Information.
A.1.3 Message Text
The message text is a phrase describing the message. The variable
portions of the message are represented by symbols separated from the rest
of the message text by single quotation marks. The description of these
symbols follows:
° The adapter number is represented by 'n'. This number may be 0 or 1
(0 for the primary adapter, 1 for the alternate adapter).
° The term 'data:' represents 24 bytes of the DEVICE= line in the
CONFIG.SYS file. The bytes begin with the abbreviation of the NetBIOS
keyword in error, followed by the "=" and the value of the parameter.
For example, consider the following message:
DXMT0 36E: Invalid keyword value: SS=18
The 'data' in this example is SS=18. The following command is entered
in CONFIG.SYS:
DEVICE=DXMT0MOD.SYS SS=18
SS is the incorrect keyword; you must replace it with a correct
keyword abbreviation, such as S. (Refer to "Keyword Values for
DXMT0MOD.SYS New Parameters" in topic 4.4.2 for a description of the
keywords.)
If an error message is displayed, you will be prompted by the LSP NDIS
driver to "Press F1 to Continue." After pressing F1, wait for the DOS
prompt to be displayed. When it is displayed, you can attempt to correct
the problem by reading the "Explanation" and following the directions
provided as "User Response."
Information relating to parameters can be found in Chapter 4, "Customizing
Driver Parameters for the LAN Support Program NDIS."
A.2 LSP NDIS Driver Message Listings
LSP NDIS can display the messages listed in this section. Each message
number is preceded by the identifier of the LSP NDIS driver. This
identifier (for example, DXMT0) is not shown in the listing because it
varies depending upon which driver displays the message.
+------------------------------------------------------------------------+
| |
| 00I Please wait, opening adapter 'n' |
| |
+------------------------------------------------------------------------+
Explanation: A Token-Ring Adapter is attempting to open.
User Response: This message will always be followed by 32E:. When 32E:
appears, enter the parameter O=N on the command line for DXMT0MOD.SYS.
You can use the Installation Aid to do this. For manual configuration,
see "Manual Configuration of the OPEN.ON.LOAD Parameter" in topic 4.4.3.
+------------------------------------------------------------------------+
| |
| 02E DOS Version 3.3 or higher required |
| |
+------------------------------------------------------------------------+
Explanation: The DOS version is earlier than 3.3.
User Response: The DOS version needs to be changed to Version 3.3 or
higher.
+------------------------------------------------------------------------+
| |
| 04E Program already loaded |
| |
+------------------------------------------------------------------------+
Explanation: This LSP NDIS driver was already installed into memory.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure.
° Check the CONFIG.SYS file to ensure that the LSP NDIS driver is not
listed twice.
+------------------------------------------------------------------------+
| |
| 05E Invalid node address parameter |
| |
+------------------------------------------------------------------------+
Explanation: The address parameter is invalid, an invalid global
parameter was entered, or a comma was placed after a global parameter. (A
global parameter is a non-positional parameter. See "Global and
Positional Parameters" in topic 4.3.4.)
User Response: Perform one of the following actions:
° Use the Installation Aid to update the parameter.
° Edit the CONFIG.SYS file to correct the address parameter or the
global parameter for this LSP NDIS driver. See "Adapter Address" in
topic 4.3.9 for more information about configuring the address
parameter.
° Use the Installation Aid to remove the address parameter from
DXME0MOD.SYS and put the NetAddress parameter in the MAC driver
section of PROTOCOL.INI. See "Network Adapter Address Configuration"
in topic 4.7.1 for more information.
+------------------------------------------------------------------------+
| |
| 06E Error reading message file (DXM.MSG) |
| |
+------------------------------------------------------------------------+
Explanation: The message file, DXM.MSG, is not present or could not be
read for one or more of the following reasons:
° The Interrupt Arbitrator (DXMA0MOD.SYS) was not previously loaded.
° DXM.MSG could not be located.
° The language type of the file does not correspond to the DOS language
type specified by the DXMA0MOD.SYS language parameter.
° DXM.MSG is from the wrong version of the LAN Support Program.
Note: This message is not translated. U.S. English is always displayed.
User Response:
° Make sure that the Interrupt Arbitrator is loaded. Do this in one of
two ways:
- Use the Installation Aid to reconfigure.
- Edit the CONFIG.SYS file to ensure that DXMA0MOD.SYS is listed in
the correct sequence. See "Editing CONFIG.SYS" in topic 3.3.2 for
a description of the correct order of the LSP NDIS drivers in
CONFIG.SYS.
° Make sure that DXM.MSG is present on the working copy in the same
directory as the LSP NDIS drivers.
° If you did not use the Installation Aid, be sure that you renamed
DXMMSG.ccc to DXM.MSG on the working copy (ccc represents the language
parameter for DXMA0MOD.SYS).
° Make sure that you got the message file and the LSP NDIS drivers from
the same version of LSP NDIS.
+------------------------------------------------------------------------+
| |
| 16E Invalid minimum SAP parameter |
| |
+------------------------------------------------------------------------+
Explanation: The parameter value is out of range.
User Response: Perform one of the following actions:
° Use the Installation Aid to restore the parameter to its default value
of 0 or to set the parameter to a valid value (the range is 0-127).
° Edit the CONFIG.SYS file to correct the parameter.
For a description of the minimum SAP parameter, see"MINSAP" in
topic 4.3.12 .
+------------------------------------------------------------------------+
| |
| 17E Invalid minimum link station parameter |
| |
+------------------------------------------------------------------------+
Explanation: The parameter value is out of range.
User Response: Perform one of the following actions:
° Use the Installation Aid to restore the parameter to its default value
of 0 or to set the parameter to a valid value (the range is 0-254).
° Edit the CONFIG.SYS file to correct the parameter.
For a description of the minimum link station parameter, see "MINLINK" in
topic 4.3.13.
+------------------------------------------------------------------------+
| |
| 20E Invalid work-size parameter |
| |
+------------------------------------------------------------------------+
Explanation: The work space parameter is not correct.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameter.
° Edit the CONFIG.SYS file to correct the work space parameter.
For a description of the work space parameter, see "Work Space" in
topic 4.3.10.
+------------------------------------------------------------------------+
| |
| 22E Error Communicating with Protocol Manager |
| |
+------------------------------------------------------------------------+
Explanation: Protocol Manager (PROTMAN.DOS) was not loaded or
DXME0MOD.SYS encountered an error while communicating with PROTMAN.DOS.
User Response:
° Use the Installation Aid to reconfigure.
° If the message reappears, make sure that PROTMAN.DOS is listed in the
CONFIG.SYS file in front of any other LSP NDIS drivers.
° Check to be sure that PROTMAN.DOS can find PROTOCOL.INI. PROTMAN.DOS
must be located in the directory specified on the DEVICE=PROTMAN.DOS
line in CONFIG.SYS or PROTOCOL.INI must be copied to the \LANMAN
directory. See "Using the /I: Parameter" in topic 3.3.4 for more
information.
+------------------------------------------------------------------------+
| |
| 23E Error Reading PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: DXME0MOD.SYS encountered an error while trying to parse the
PROTOCOL.INI memory image.
User Response:
° Use the Installation Aid to reconfigure. Be sure you specify the
primary and alternate adapters correctly.
° Check the named section of the PROTOCOL.INI file for the protocol
driver. It is named [DXME0_MOD], [DXME0_NIF], [DXMJ0MOD_MOD], or
[DXMJ0MOD_NIF]. Make sure that the DriverName = parameter and that
the Bindings = parameters are set correctly. See "Editing the
PROTOCOL.INI File" in topic 3.5 for more information about the
Bindings = parameters.
° Check the PROTOCOL.INI file for a syntax error or irrelevant data.
+------------------------------------------------------------------------+
| |
| 32E Initialization or open error on adapter 'n' |
| |
+------------------------------------------------------------------------+
Explanation: The adapter cannot be opened at the NetBIOS interface at
load time. The parameter O=N must be specified.
User Response: Be sure to specify the OPEN.ON.LOAD parameter as N (No).
(See "Manual Configuration of the OPEN.ON.LOAD Parameter" in topic 4.4.3
and "Setting the OPEN.ON.LOAD Parameter in DXMT0MOD.SYS" in topic 6.4 for
more information.)
+------------------------------------------------------------------------+
| |
| 33E Cannot mix OLD.PARMS.x and 'new' keywords |
| |
+------------------------------------------------------------------------+
Explanation: Both new and old parameters are mixed on the NetBIOS driver
parameter line.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameters for NetBIOS.
° Edit the CONFIG.SYS file to ensure that the parameter types are not
mixed.
See "Keyword Values for DXMT0MOD.SYS Old Parameters" in topic 4.4.1 and
"Keyword Values for DXMT0MOD.SYS New Parameters" in topic 4.4.2 for more
information about the keywords.
+------------------------------------------------------------------------+
| |
| 34E Invalid keyword: 'data' |
| |
+------------------------------------------------------------------------+
Explanation: The keyword used is invalid.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameters for NetBIOS.
° Edit the CONFIG.SYS file to ensure that the keyword is correct.
See "Keyword Values for DXMT0MOD.SYS Old Parameters" in topic 4.4.1 and
"Keyword Values for DXMT0MOD.SYS New Parameters" in topic 4.4.2 for more
information about the keywords.
+------------------------------------------------------------------------+
| |
| 35E Duplicate keyword: 'data' |
| |
+------------------------------------------------------------------------+
Explanation: This keyword is used twice on the NetBIOS driver parameter
line.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameters for NetBIOS.
° Edit the CONFIG.SYS file to remove the keyword listed twice.
See "Keyword Values for DXMT0MOD.SYS Old Parameters" in topic 4.4.1 and
"Keyword Values for DXMT0MOD.SYS New Parameters" in topic 4.4.2 for more
information about the keywords.
+------------------------------------------------------------------------+
| |
| 36E Invalid keyword value: 'data' |
| |
+------------------------------------------------------------------------+
Explanation: The value listed is invalid for its keyword.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameters for NetBIOS.
° Edit the CONFIG.SYS file to ensure that the value is correct.
See "Keyword Values for DXMT0MOD.SYS Old Parameters" in topic 4.4.1 and
"Keyword Values for DXMT0MOD.SYS New Parameters" in topic 4.4.2 for more
information about the keywords.
+------------------------------------------------------------------------+
| |
| 37E Adapter support required |
| |
+------------------------------------------------------------------------+
Explanation: No adapter support has been loaded.
User Response: Perform one of the following actions:
° Use the Installation Aid to reconfigure the parameter.
° Edit the CONFIG.SYS file to ensure that an adapter support device
driver is listed.
+------------------------------------------------------------------------+
| |
| 40E Invalid transmit/swap parameter |
| |
+------------------------------------------------------------------------+
Explanation: The transmit/swap parameter is not correct.
User Response: Take one of the following actions:
° Use the Installation Aid to reconfigure the parameter.
° Edit the CONFIG.SYS file to correct the transmit/swap parameter.
For a description of the transmit/swap parameter, see "Transmit/Swap" in
topic 4.3.11.
+------------------------------------------------------------------------+
| |
| 41E The protocol manager could not be opened. The return code is |
| 'retcode'. |
| |
+------------------------------------------------------------------------+
Explanation: One of the following events occurred:
° The system service DosOpen request to the PROTMAN.DOS driver failed.
° Another device driver has opened PROTMAN with exclusive rights and
failed to close it.
User Response: Check your CONFIG.SYS file and ensure that the PROTMAN.DOS
driver is active. For additional information about the return code
('retcode') displayed with the message for a specific cause, refer to the
error codes for interrupt 21H function calls listed in the DOS Technical
Reference.
+------------------------------------------------------------------------+
| |
| 42E The protocol manager would not accept a request |
| |
+------------------------------------------------------------------------+
Explanation: The protocol manager failed to honor a request from this
protocol stack.
User Response: Check for additional messages from the protocol manager
that will indicate the cause for failure. Correct the error and try the
operation again.
+------------------------------------------------------------------------+
| |
| 43E The protocol manager would not supply a configuration image |
| |
+------------------------------------------------------------------------+
Explanation: The protocol manager did not honor the request for the
configuration image.
User Response: Verify that the PROTOCOL.INI file exists and that it is
valid, and then retry the operation.
+------------------------------------------------------------------------+
| |
| 44E The protocol manager would not accept module registration |
| |
+------------------------------------------------------------------------+
Explanation: An attempt to register the device name with the protocol
manager was unsuccessful.
User Response: Ensure that the bracketed names in PROTOCOL.INI are unique
and retry the operation.
+------------------------------------------------------------------------+
| |
| 45E No MAC driver bindings were specified in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: There were no medium access control (MAC) names specified on
the Bindings = statement in the IBM NETBEUI section of PROTOCOL.INI.
User Response: Check the section of the PROTOCOL.INI file named
[DXMJ0MOD_MOD] to ensure that a valid MAC driver name is specified on the
Bindings = statement.
+------------------------------------------------------------------------+
| |
| 46E System resources are not available to hold the current |
| parameter configuration in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: The sum of the configuration parameters requires more memory
than the amount available.
User Response: Refer to your network planning and administration guides
for additional information about suggested values. Reduce the resources
required by changing PROTOCOL.INI.
+------------------------------------------------------------------------+
| |
| 47E Will not fit in UMB--Try loading low |
| |
+------------------------------------------------------------------------+
Explanation: There is not enough space in high memory to load the device
driver.
User Response: Change the DEVICEHIGH= statement in CONFIG.SYS to DEVICE=.
+------------------------------------------------------------------------+
| |
| 49E Address error correcting for 386 processor |
| |
+------------------------------------------------------------------------+
Explanation: An internal processing error has occurred.
User Response: Contact your IBM service representative.
+------------------------------------------------------------------------+
| |
| 50E There are too many MAC drivers to bind |
| |
+------------------------------------------------------------------------+
Explanation: The number of MAC drivers specified on the Bindings =
statement in PROTOCOL.INI exceeds the maximum number of devices to bind
(MAXBIND).
User Response: Correct the PROTOCOL.INI file to ensure that the number of
MAC names specified in the Bindings = statement does not exceed 2.
+------------------------------------------------------------------------+
| |
| 51E The unrecognized keyword 'keyword' was found in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: A keyword ('keyword') was found in PROTOCOL.INI that is not
recognized as a valid parameter.
User Response: Review the PROTOCOL.INI file to locate the incorrect
parameter. Correct or delete the unrecognized keyword and retry the
operation.
+------------------------------------------------------------------------+
| |
| 52E A value is required for keyword 'keyword' in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: The keyword ('keyword') specified has required parameters.
No parameter values were found for this keyword.
User Response: Add the correct value to the keyword and retry the
operation.
+------------------------------------------------------------------------+
| |
| 53E The value specified for parameter 'parm' is not valid |
| |
+------------------------------------------------------------------------+
Explanation: The value provided for the parameter ('parm') is not the
correct type or is not a valid value.
User Response: Change the value for the parameter in PROTOCOL.INI.
+------------------------------------------------------------------------+
| |
| 54E The value specified for parameter 'parm' is not valid |
| |
+------------------------------------------------------------------------+
Explanation: The value specified for the parameter ('parm') is either
larger than the maximum allowed or smaller than the minimum allowed for
that parameter.
User Response: Correct the value specified and retry the operation.
+------------------------------------------------------------------------+
| |
| 55E Duplicate parameter 'parm' found in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: The parameter ('parm') occurred more than once in
PROTOCOL.INI. Only one occurrence of the parameter is allowed.
User Response: Change PROTOCOL.INI so that it contains only one reference
to the parameter and retry the operation.
+------------------------------------------------------------------------+
| |
| 56E There is no section for NETBEUI in PROTOCOL.INI |
| |
+------------------------------------------------------------------------+
Explanation: There are no configuration parameters defined for NETBEUI in
PROTOCOL.INI.
User Response: Change PROTOCOL.INI to add a section of configuration
information for NETBEUI. The minimum statements required for this section
are DriverName =, and Bindings =. These statements are in the
[DXMJ0MOD_MOD] section of PROTOCOL.INI. Retry the operation.
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.