IBM PC Server 325, User Handbook Manual

Page: 174 / 288

Ethernet Controller Messages
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 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 your 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.
160
PC Server 325 User's Handbook