User Guide

LANSUP-DOS Messages 213
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
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.