|
|
|
PCNTW-DOS-1 The LSL is not loaded.
Explanation: The Link Support support module (LSL.COM) is not loaded.
Action: Load LSL.COM then, load the device driver.
PCNTW-DOS-2 The LSL has no more room for a board using Frame
<string>.
Explanation:The maximum number of adapters,
whether virtual or physical,
has been registered with the Link Support Layer.
In the PC Server 325, the
DOS ODI LSL can support up to five PCI Ethernet adapters, plus
the Ethernet controller in the system board.
Action:Reduce the number of active adapters in the systems by
removing an adapter, or by decreasing the number of frame types
activated by Multiple Link Interface Driver (MLID).
PCNTW-DOS-3 Could not find PCNTNW MLID (Multiple Link Interface Driver) to unload.
Explanation: A request was made to unload PCNTNW MLID, but the
MLID (Multiple Link Interface Driver) is not loaded.
Action: None.
PCNTW-DOS-4 A TSR is loaded above the PCNTNW MLID (Multiple Link Interface Driver) .
Explanation: You tried to unload the PCNTNW MLID from memory, but the
PCNTNW MLID detected another Terminate and Stay Resident (TSR) program
loaded above the MLID. For the PCNTNW MLID to unload safely,
you must first unload any
TSR programs that were loaded after you loaded the MLID.
Action: Either unload the other TSR program
before loading the PCNTNW MLID,
or unload the TSR program before attempting this operation.
PCNTW-DOS-5 PCNTNW MLID (Multiple Link Interface Driver) could not be unloaded the operation was aborted.
Explanation: The PCNTNW MLID attempted to remove the resident
PCNTNW MLID from memory, and failed. A hardware error
has probably occurred.
Action: Run the Ethernet diagnostic.
PCNTW-DOS-6
The adapter did not initialize. PCNTNW did not unload.
Explanation: The hardware did not initialize correctly. The
PCNTNW driver
did not load.
Action: Check the hardware. Make sure that the board's
hardware setting
matches its settings in the NET.CFG file.
PCNTW-DOS-7 You need another PCNTNW MLID (Multiple Link Interface Driver) Section Heading in
the NET.CFG file in order to load the MLID again.
Explanation: You tried to load the PCNTNW MLID a second time. Normally,
you would do this so that you could use two or more
Ethernet controllers in the
server. When two or more of the same type of
Ethernet controllers are
installed in the server, an associated PCNTNW MLID section heading
must be specified in the NET.CFG file.
Action: Create a NET.CFG file and add the commands for both PCNTNW
MLID boards to the file. Then, restart the server.
PCNTNW-DOS-8 A NET.CFG is required to load the MLID (Multiple Link Interface Driver) again.
Explanation: You tried to load the PCNTNW MLID a second time. Normally,
you would do this so that you could use two or more
Ethernet controllers in the
server. When two or more of the same type of
Ethernet controllers are
installed in the server, an associated PCNTNW MLID section heading
must be specified in the NET.CFG file.
Action: Create a NET.CFG file and add the commands for both PCNTNW
MLID boards to the file. Then, restart the server.
PCNTNW-DOS-9 The NET.CFG entry has been ignored.
Explanation: The PCNTNW ignored the NET.CFG entry.
Action: Verify that the entries in the NET.CFG file are correct.
The PCNTNW MLID has been successfully removed.
Explanation:A request was made to unload a PCNTNW MLID. The
PCNTNW MLID has been removed from memory.
Action: None.
PCNTNW-DOS-11 The MLID (Multiple Link Interface Driver) does not support frame <string:>.
The PROTOCOL keyword has been ignored.
Explanation: The NET.CFG files specified the
PROTOCOL option
for a PCNTNW MLID. The specified frame type is not supported
by the PCNTNW MLID.
Action: Check the PROTOCOL line in the NET.CFG file for
possible omissions of required dashes and underscores or any
misspellings.
PCNTNW-DOS-12 The protocol keyword must have a frame type. Entry ignored.
Explanation: The PROTOCOL option was specified in the NET.CFG file
for a PCNTNW MLID. The entry failed to specify the associated frame
type for the protocol ID addition. An entry in the NET.CFG file
for the PROTOCOL option should use the following format:
LINK DRIVER PCNTNW
PROTOCOL IPX 8137 ETHERNET_II
Action: Specify a frame with the PROTOCOL option.
PCNTNW-DOS-13 The MLID (Multiple Link Interface Driver) could not register Protocol ID <string>
for protocol stack <string> for frame type.
Explanation: The PCNTNW MLID could not register the specified Protocol ID.
Action: Verify the protocol information in the NET.CFG file.
PCNTNW-DOS-14 This version of LSL is not supported.
Explanation: The PCNTNW MLID cannot run successfully using this version
of the LSL.
Action: Update the LSL.COM to a newer version.
PCNTNW-DOS-15 The frame type is already activated for frame
<string>. The NET.CFG entry has been ignored.
Explanation: Two FRAME keywords under the same main section heading
specified the same frame type. A specified frame type can be
specified only once per driver.
Action: Remove the duplicate FRAME keyword entry.
PCNTNW-DOS-16 The node address was incorrectly specified in NET.CFG.
Explanation: You used the NODE ADDRESS option in the NET.CFG
file to override the node address on the network board. The number
specified was not a valid Ethernet address. An Ethernet address
is six bytes in length.
This error occurs if Bit 0 of the first address byte is a 1. This
bit must always be 0. For example, if the first byte has the following
address, an invalid Ethernet address is generated.
FIRST BYTE
7 6 5 4 3 2 1 0
------------------------
0 0 0 0 0 0 0 1
This byte will produce node addresses in the
0100 0000 0000 to 01FF FFFF FFFF range (in hexadecimal),
all of which will be invalid.
Action:Specify a valid node address in
the NET.CFG file.
PCNTNW-DOS-17
An invalid keyword was specified in NET.CFG on line xx .
Explanation: The keyword specified in the NET.CFG file is incorrect.
Action: Check the keyword in question. Make sure that the keyword
is correctly spelled.
PCNTNW-DOS-18 The frame type specified in the NET.CFG file is not supported.
Explanation: The NET.CFG file specified
the PROTOCOL option
for a PCNTNW MLID. The specified frame type is not supported
by the PCNTNW MLID.
Action: Check the PROTOCOL line in the NET.CFG file for
possible omissions of required dashes and underscores, or any
misspellings. Check the PCNTNW MLID (Multiple Link Interface Driver)
documentation for supported frame types.
PCNTNW-DOS-19 An invalid Ethernet node address is specified in NET.CFG.
The MLID modified the incorrect address bits.
Explanation:
The NET.CFG file has an invalid node address. The PCNTNW MLID
modified and corrected the address.
Action: Verify the node address entries
in the NET.CFG file.
PCNTNW-DOS-50 The board cannot be found.
Explanation: The Ethernet controller is either not configured correctly or is
disabled.
Action: Perform the following steps
PCNTNW-DOS-54 The board did not respond to the initialization command.
Explanation: The Ethernet controller initialization failed.
Action: Perform the following steps
PCNTNW-DOS-58 The board did not respond to the initialization command.
Explanation: The IRQ setting might be incorrect with the hardware
setting, or the EEPROM might be corrupted.
Action: Verify that
the IRQ settings in the NET.CFG file
match the configuration settings in the Configuration/Setup utility programs.
See 'PCI Bus Control' for information on setting the interrupt
requests.
Verify that the EEPROM on the system board is programmed correctly.
PCNTNW-DOS-61 PCI device IRQ number mismatch.
Explanation: The IRQ number specified in the NET.CFG file
does not match with the
IRQ number assigned in the Configuration/Setup utility programs.
Action: Remove the IRQ number in the NET.CFG file.
PCNTNW-DOS-64 The device was not found.
Explanation: The driver cannot find any PCnet device in the server.
Action: Verify that the Ethernet enable jumper is set to the default
(enable) position.
Go to 'Ethernet Diagnostics' to run the diagnostic utility.
PCNTNW-DOS-65 Device not found at IOADDRESS.
Explanation: The device was not found at the IO address
specified in the NET.CFG file.
The driver cannot find
an Ethernet controller in the server.
Action: Verify that the IO address in the NET.CFG file
matches with the
with the board. Otherwise, remove the PORT keyword from
the NET.CFG file.
PCNTNW-DOS-67 PCI scan specified, device not found.
Explanation: The driver
cannot locate the Ethernet controller on the PCI bus.
Action: Perform the following steps
PCNTNW-DOS-75 Unsupported bus ID specified.
Explanation: The bus ID number specified in the NET.CFG file
is not supported by Novell.
Action: Correct the bus ID number in the NET.CFG file.
PCNTNW-DOS-76 Wrong bus ID specified.
Explanation: The bus ID number specified in the NET.CFG file is
different from the bus type found in the server.
Action: Correct the bus ID number in the NET.CFG.
PCNTNW-DOS-80 The DMA parameter is not necessary for PCI device.
Explanation: The board does not require a DMA setting.
Action: Edit the NET.CFG file to delete the DMA parameter.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.