The following includes messages from LADSUP.COM.
LANSUP-DOS-X-001: The LSL is not loaded.
Source:
LANSUP.COM
Explanation:
The computer must load the Link Support Layer (LSL) before loading the driver.
Action:
Load the LSL; then load the driver, as in the following example:
C:\NWCLIENT\LSL <Enter>
C:\NWCLIENT\LANSUP <Enter>
LANSUP-DOS-X-002: The LSL has no room for a board using frame type.
Source:
LANSUP.COM
Explanation:
The Link Support Layer™ (LSL™) is configured with resources for a set number of network boards. (The default is 4.) This number has been exceeded.
Action:
Edit the NET.CFG file, and add the MAX BOARDS keyword to reflect the number of network boards to be loaded, as in the following example:
LINK SUPPORT
MAX BOARDS 6
Unload the driver; then reload it as in the following example:
C:\NWCLIENT\LANSUP /u <Enter>
C:\NWCLIENT\LANSUP <Enter>
LANSUP-DOS-X-003: Could not find LANSUP MLID to unload.
Source:
LANSUP.COM
Explanation:
The user or another program was trying to unload the LANSUP driver and was not loaded.
LANSUP-DOS-X-004: A TSR is loaded above the LANSUP MLID.
Source:
LANSUP.COM
Explanation:
Another TSR (terminate-and-stay-resident) program was loaded after the LANSUP driver.
Action:
The drivers must be unloaded in reverse order, as follows:
C:\NWCLIENT\NETX /u <Enter>
C:\NWCLIENT\IPXODI /u <Enter>
C:\NWCLIENT\LANSUP /u <Enter>
Unload the TSRs; then try to unload the LANSUP driver. You can force the LANSUP driver to unload from the command line by using the /F switch after the driver name, as follows:
C:\NWCLIENT\LANSUP /f <Enter>
Use caution when using the /F switch because it could cause the system to hang.
LANSUP-DOS-X-005: LANSUP MLID could not be unloaded; the operation was aborted.
Source:
LANSUP.COM
Possible Cause:
The LANSUP driver could not be shut down and unregistered; consequently, it cannot be unloaded.
Action:
To unload the driver, reboot the system.
LANSUP-DOS-X-006: The adapter did not initialize. LANSUP did not load.
Source:
LANSUP.COM
Possible Cause:
The LANSUP driver encountered an error while loading.
Action:
Corrective action can vary. See the preceding driver-specific message on the screen for specific information about the error that occurred.
LANSUP-DOS-X-007: You need another MLID Section Heading in the NET.CFG file in order to load the MLID again.
Source:
LANSUP.COM
Possible Cause:
The NET.CFG file does not have an individual entry for each driver that is intended to be loaded. This means that one of the drivers is not loaded into memory.
Action:
Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Reload the driver.
LANSUP-DOS-X-008: A NET.CFG is required to load the MLID again.
Source:
LANSUP.COM
Possible Cause:
The NET.CFG file does not have an individual entry for each driver that is intended to be loaded. This means that one of the drivers is not loaded into memory.
Action:
Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Reload the driver.
LANSUP-DOS-X-009: The NET.CFG entry has been ignored.
Source:
LANSUP.COM
Possible Cause:
The NET.CFG file does not have an individual entry for each driver that is intended to be loaded. This means that one of the drivers is not loaded into memory.
Action:
Unload the LANSUP driver. Modify the NET.CFG file to contain a unique entry for each driver to be loaded. This requires an individual Link Driver heading in the NET.CFG file for each driver or each instance of the same driver. Load the drivers again.
LANSUP-DOS-X-011: The MLID does not support frame type. The protocol keyword has been ignored.
Source:
LANSUP.COM
Possible Cause:
An unsupported or incorrectly typed frame type has been specified with the protocol keyword.
Action:
Verify that the frame type assigned in the NET.CFG file under the protocol keyword is valid.
LANSUP-DOS-X-012: The protocol keyword must have a frame type. Entry ignored.
Source:
LANSUP.COM
Possible Cause:
The PROTOCOL keyword entry is incomplete.
Action:
Correct the protocol entry in the NET.CFG file. The proper syntax for the protocol keyword is as follows:
PROTOCOL LANSUP hex_protocol_ID frame_type
LANSUP-DOS-X-013: The MLID could not register Protocol ID number for protocol stack name for frame type frame.
Source:
LANSUP.COM
Possible Cause:
The Link Support Layer (LSL) is configured with resources for a set number of Protocol Identifiers. (The default is 4.) This number has been exceeded.
Action:
Edit the NET.CFG file, and add the MAX STACKS keyword to reflect the number of network boards to be loaded, as in the following example:
LINK SUPPORT
MAX STACKS 6
Unload the driver; then reload it as in the following example:
C:\NWCLIENT\LANSUP /u <Enter>
C:\NWCLIENT\LSL /u <Enter>
C:\NWCLIENT\LSL <Enter>
C:\NWCLIENT\LANSUP <Enter>
LANSUP-DOS-X-014: This version of the LSL is not supported.
Source:
LANSUP.COM
Explanation:
The driver the computer is using supports only Link Support Layer (LSL) versions later than 1.0.
Action:
Unload the LSL and replace it with a newer version.
LANSUP-DOS-X-015: The frame type is already active for frame type.
Source:
LANSUP.COM
Possible Cause:
The frame type is already loaded, and it cannot be loaded repeatedly.
Action:
Edit the NET.CFG file to load the frame type only once for a given network board.
LANSUP-DOS-X-016: The node address was incorrectly specified in the NET.CFG file.
Source:
LANSUP.COM
Possible Cause:
The node address override in the NET.CFG file is too long.
Action:
Edit the NET.CFG file and correct the node address. The node address must be less than or equal to 12 hex digits.
LANSUP-DOS-X-017: An invalid keyword was specified in NET.CFG on line number.
Source:
LANSUP.COM
Possible Cause:
The key word on the line indicated was not recognized.
Action:
Edit the NET.CFG file and correct the spelling of the keyword.
LANSUP-DOS-X-018: The frame type specified in the NET.CFG is not supported.
Source:
LANSUP.COM
Possible Cause:
The frame type specified with the FRAME keyword is not supported by the driver.
Action:
Edit the NET.CFG file and fix frame type.
LANSUP-DOS-X-019: An invalid LANSUP node address is specified in NET.CFG. The MLID modified the incorrect address bits.
Source:
LANSUP.COM
Possible Cause:
The node address specified in the NET.CFG file has set reserved bits.
Action:
Edit the NET.CFG file and correct the node address.
LANSUP-DOS-X-050: [ISA bus | Microchannel] The board cannot be found.
Source:
LANSUP.COM
Explanation:
If the computer is using an ISA bus network board, the network board was not found due to one or more of the following conditions:
Possible Cause:
The network board is not present in the computer.
Action:
Make sure the network board is properly seated into the slot.
Possible Cause:
Another network board is using the same hardware settings as this network board.
Action:
If other network boards are using the same hardware settings, change the settings and try to reload the driver.
Possible Cause:
The network board settings are not the defaults, and they are not defined in the NET.CFG file.
Action:
If the jumper settings are not the defaults, make sure that they match the settings in the NET.CFG file.
Action:
If the computer is not using the NET.CFG file, make sure the jumper settings are set to the defaults.
Possible Cause:
The network board is does not work.
Action:
Replace the network board with one that you know works.
Action:
If the computer is using a microchannel network board, the network board is not in the computer, or the network board’s configuration could not be obtained, do the following:
-
Make sure that the network board is properly seated into a slot.
-
Insert the network board into a slot, and run the Reference diskette to install it.
LANSUP-DOS-X-051: Board RAM failed the memory test.
Source:
LANSUP.COM
Explanation:
The memory test on the network board’s internal static RAM failed.
Action:
Check the network board and other hardware. If necessary, replace the network board.