 |
|
|
|
Driver Error Messages
Table of Contents
Message PCNTNW-DOS-1: The LSL is not loaded.
Meaning The Link Support Module program (LSL.COM) is not loaded.
Action Load the LSL.COM before loading the driver.
Message PCNTNW-DOS-2: The LSL has no more room for a board using Frame <string>
Meaning The maximum number of boards, whether virtual or physical, has been registered with the Link support layer. The DOS ODI
LSL can support up to eight boards.
Action Reduce the number of active boards in the systems by unloading a board or by decreasing the number of frame types activated
by MLID.
Message PCNTNW-DOS-3: Could not find PCNTNW MLID to unload
Meaning A request was made to unload PCNTNW MLID, but the MLID is not loaded.
Action None
Message PCNTNW-DOS-4: A TSR is loaded above the PCNTNW MLID.
Meaning You tried to unload the PCNTNW MLID from memory, but the PCNTNW MLID detected another Terminate-and Stay-Resident program loaded
above the MLID. For the PCNTNW MLID to safely unload, TSRs that were loaded after it must be unloaded first.
Action Either load the other TSR before loading the PCNTNW MLID or unload the TSR before trying this operation.
Message PCNTNW-DOS-5: PCNTNW MLID could not be unloaded; the operation was aborted.
Meaning The PCNTNW MLID was attempting to remove the resident PCNTNW MLID from memory. The PCNTNW MLID was unable to successfully shut down the resident PCNTNW MLID. A hardware failure has probably occurred.
Action Check the hardware. If the hardware is faulty, replace it.
Message PCNTNW-DOS-6: The adapter did not initialize. PCNTNW did not load.
Meaning The hardware did not initialize correctly. The PCNTNW did not load.
Action Check the hardware. Make sure that the hardware setting of the board matches the card's settings in the NET.CFG file.
Message PCNTNW-DOS-7: You need another PCNTNW MLID Section Heading in the NET.CFG file in order the load the MLID again.
Meaning You tried to load the PCNTNW MLID a second time. Normally, you would do this so that you could use two or more boards
in the workstation. When two or more of the same type of network boards
are installed in the workstation, 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 reboot the workstation.
Message PCNTNW-DOS-8: A NET.CFG is required to load the MLID again.
Meaning You tried to load the PCNTNW MLID a second time. Normally, you would do this so that you could use two or more boards
in the workstation. When two or more of the same type of network boards
are installed in the workstation, 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 reboot the workstation.
Message PCNTNW-DOS-9: The NET.CFG entry has been ignored.
Meaning The PCNTNW ignored the NET.CFG entry.
Action You may want to modify the NET.CFG file to delete or change the entry in question.
Message The PCNTNW MLID has been successfully removed.
Meaning A request was made to unload an PCNTNW MLID, and the PCNTNW MLID was removed from memory.
Action None
Message PCNTNW-DOS-11: The MLID does not support frame <string>. The protocol keyword has been ignored.
Meaning The "PROTOCOL" option was specified in the NET.CFG for an 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 board documentation for supported frame types.
Message PCNTNW-DOS-12: The protocol keyword must have a frame type. Entry ignored.
Meaning The "PROTOCOL" option was specified in the NET.CFG for an 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 look similar to the following:
LINK DRIVER PCNTNW
PROTOCOL IPX 8137 ETHERNET_II
Action Specify a frame with the "PROTOCOL" option.
Message PCNTNW-DOS-13: The MLID could not register Protocol ID <string> for protocol stack <string> for frame type.
Meaning The PCNTNW MLID could not register the specified Protocol ID.
Action Verify the protocol information in the NET.CFG file.
Message PCNTNW-DOS-14: This version of LSL is not supported.
Meaning The PCNTNW MLID cannot run correctly using this version of the LSL.
Action Update your LSL.COM to a newer version.
Message PCNTNW-DOS-15: The frame type is already activated for frame <string>. The NET.CFG entry has been ignored.
Meaning Two "Frame" keywords under the same main section heading specified the same frame type. A specified frame type may be specified only once per driver.
Action Remove the duplicate "Frame" keyword entry.
Message PCNTNW-DOS-16: The node address was incorrectly specified in NET.CFG.
Meaning 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 node 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, all of which will be invalid.
Action Change the NET.CFG file so that a valid node address is specified.
Message PCNTNW-DOS-79: LAPP Driver can NOT run on the PCnetISA Card.
Meaning The LAPP driver is intended for use with the PCnet-ISA+ adapter card.
Action Run the LAPP driver only if you have a PCnet-ISA+ adapter card installed.
Message PCNTNW-DOS-17: An invalid keyword was specified in NET.CFG on line xx.
Meaning The keyword specified in NET.CFG file is incorrect.
Action Check the keyword in question. Make sure that the keyword is correctly spelled.
Message PCNTNW-DOS-18: The frame type specified in NET.CFG is not supported.
Meaning The "PROTOCOL" option was specified in the NET.CFG for an 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 documentation for supported frame types.
Message PCNTNW-DOS-19: An invalid Ethernet node address is specified in NET.CFG. The MLID modified the incorrect address bits.
Meaning The NET.CFG has an invalid node address. The PCNTNW MLID modified and corrected the address.
Action You may want to correct the node address line in the NET.CFG file.
Message PCNTNW-DOS-50: The board cannot be found.
Meaning The board is either not physically present or not configured correctly.
Action Make sure that the board is physically present in the system. Also check the hardware setting of the board (I/O, IRQ, DMA)
against the NET.CFG settings. If this message still appears, replace
the board.
Message PCNTNW-DOS-54: The board did not respond to the initialization command.
Meaning The board initialization failed.
Action Replace the board.
Message PCNTNW-DOS-58: The board did not respond to the initialization command.
Meaning The DMA and IRQ settings may be incorrect with the hardware settings. Otherwise, the EEPROM may be corrupted.
Action Verify the DMA & IRQ settings in NET.CFG match the hardware jumper settings or verify that the EEPROM on-board is programmed
correctly.
Message PCNTNW-DOS-59: Buffers could not be locked.
Meaning An attempt was made to lock buffers for direct access. The attempt failed.
Action Check the memory manager documentation and make sure that it supports a memory manager VDS (Virtual DMA Server). If in doubt,
either use another memory manager or do not use it.
Message PCNTNW-DOS-60: PnP device DMA number mismatch.
Meaning The DMA number specified in NET.CFG mismatches with the DMA number assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action Remove the DMA number in NET.CFG.
Message PCNTNW-DOS-61: PCI device IRQ number mismatch.
Meaning The IRQ number specified in NET.CFG mismatches with the IRQ number assigned by the PCI BIOS.
Action Remove the IRQ number in NET.CFG.
Message PCNTNW-DOS-63: PnP device IRQ number mismatch.
Meaning The IRQ number specified in NET.CFG mismatches with the IRQ number assigned by the PnP Configuration Manager or by the
on-board EEPROM if PnP is disabled.
Action Remove the IRQ number in NET.CFG.
Message PCNTNW-DOS-64: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident the PCnet board.
Message PCNTNW-DOS-65: Device not found at IOADDRESS.
Meaning The PCnet device cannot be found at the IO Address specified in NET.CFG.
Action Verify that the IO Address in NET.CFG matches with the board. Otherwise, remove the PORT keyword from NET.CFG.
Message PCNTNW-DOS-66: PCI scan can only execute on a 386 and higher processor.
Meaning The PCI bus is not available on your system. The PCI bus is only supported on a 386 or higher processor.
Action Do not specify PCI for BUSTYPE with your current system setup.
Message PCNTNW-DOS-67: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Use the BUSTYPE keyword to specify PCI1 or PCI2 values if
the PCI mechanism is known for your system. Otherwise, replace the
PCI board.
Message PCNTNW-DOS-68: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the VL board is physically installed properly. Otherwise, replace the VL board.
Message PCNTNW-DOS-69: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA+ board.
Message PCNTNW-DOS-70: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA board.
Message PCNTNW-DOS-71: ISA DMA number out of range.
Meaning The PCnet-ISA board only supports four DMA channels.
Action Specify a valid DMA number in NET.CFG to match the jumper setting on the PCnet-ISA board. Refer to the Software Keyword
section of this manual for the available range of values.
Message PCNTNW-DOS-73: PCI BIOS not present.
Meaning The PCI system does not have PCI BIOS support. The driver will try to scan the bus to find AMD's PCI driver.
Action None.
Message PCNTNW-DOS-74: VESA scan can only execute on a 386 or higher processor.
Meaning The VESA bus is not available on your system. The VESA bus is only supported on a 386 or higher processor.
Action Do not specify VESA for BUSTYPE with your current system setup.
Message PCNTNW-DOS-75: Unsupported bus ID specified.
Meaning The bus ID number specified in NET.CFG is not supported by Novell.
Action Correct the bus ID number in the NET.CFG.
Message PCNTNW-DOS-76: Wrong bus ID specified.
Meaning The bus ID number specified in NET.CFG is different from the bus type found in the system.
Action Correct the bus ID number in the NET.CFG.
Message PCNTNW-DOS-77: Driver does not support slave mode.
Meaning The hardware is configured as a slave board.
Action Change to a bus master board.
Message PCNTNW-DOS-79: LAPP Driver can NOT run on the PCnetISA Card.
Meaning The LAPP driver is not intended for use with the PCnet-ISA adapter card.
Action Run the LAPP driver only if you have any PCnet adapter card except PCnet-ISA installed.
Message PCNTNW-DOS-80: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove DMA from NET.CFG.
Message PCNTNW-DOS-81: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove DMA from NET.CFG.
1) Babbling Transmitter
This counter indicates that the transmitter has been transmitting longer than the time required to send the maximum size frame. This counter is incremented if 1,519 bytes or greater are transmitted.
2) Fatal Rx Int.
This counter is incremented if the driver receives a frame > 1,518 bytes. Ethernet networks should not contain frames >
1,518 bytes.
3) PCnet Reset
This counter is incremented when the board goes through a reset.
4) Max Collision
This counter is incremented when there is a collision on the Ethernet Network.
5) Memory Error
This counter is incremented when the board does not get bus master resource in the system.
6) Missed Packet
This counter is incremented when the board misses an incoming packed from the network due to low resources.
7) Rx Frame Error
This counter is incremented when the board receives a frame with CRC error.
8) Tx Late Collision
This counter is incremented when a late collision (after 51.2 micro seconds) occurs on the Ethernet network.
9) Tx Retry
This counter is incremented when the board transmitter fails to transmit a frame after attempting to transmit for 16 times due to
repeated collisions.
10) Tx Time Out
This counter is incremented when the transmitter in the board could not transmit a packet, within an allowed time, on the network due to very heavy traffic conditions.
11) TX Buffer Error
This counter is incremented when the controller does not find the ENP flag in the next buffer and does not own the next buffer.
12) TX Underflow Error
This counter is incremented wlhen the transmitter has truncated a message due to data late from memory.
13) Rx Buffer Error
This counter is incremented when the controller does not own the buffer while data chaining a received frame.
Message PCNTNW-OS2-1:The LSL is not loaded.
Meaning The Link Support Module program (LSL.SYS) is not loaded.
Action Load the LSL.SYS before loading the driver.
Message PCNTNW-OS2-21: Could not add MLID Protocol ID.
Meaning The PCNTNW MLID could not register the specified Protocol ID.
Action Verify the protocol information in the NET.CFG file.
Message PCNTNW-OS2-22: Could not allocate memory. Virtual board did not load.
Meaning The driver could not allocate memory for the virtual board.
Action Check the system configuration.
Message PCNTNW-OS2-54: The board did not respond to the initialization command.
Meaning The board initialization failed.
Action Replace the board.
Message PCNTNW-OS2-56: This interrupt is already used and cannot be shared.
Meaning This interrupt is already used and cannot be shared.
Action Change the IRQ in NET.CFG. For PCnet-ISA, verify the jumper setting matches with IRQ in NET.CFG.
Message PCNTNW-OS2-58: The board did not respond to the initialization command.
Meaning The DMA and IRQ settings may be incorrect with the hardware settings. Otherwise, the EEPROM may be corrupted.
Action Verify the DMA & IRQ settings in NET.CFG match the hardware jumper settings or verify that the EEPROM on-board is programmed
correctly.
Message PCNTNW-OS2-59: Buffers could not be locked.
Meaning An attempt was made to lock buffers for direct access. The attempt failed.
Action Check the memory manager documentation and make sure that it supports a memory manager VDS (Virtual DMA Server). If in doubt, either use another memory manager or do not use it.
Message PCNTNW-OS2-60: PnP device DMA number mismatch.
Meaning The DMA number specified in NET.CFG mismatches with the DMA number assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action Remove the DMA number in NET.CFG file.
Message PCNTNW-OS2-61: PCI device IRQ number mismatch.
Meaning The IRQ number specified in NET.CFG mismatches with the IRQ number assigned by the PCI BIOS.
Action Remove the IRQ number in NET.CFG file.
Message PCNTNW-OS2-63: PnP device IRQ number mismatch.
Meaning The IRQ number specified in NET.CFG mismatches with the IRQ number assigned by the PnP Configuration Manager or by the on-board EEPROM if PnP is disabled.
Action Remove the IRQ number in NET.CFG file.
Message PCNTNW-OS2-64: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident the PCnet board.
Message PCNTNW-OS2-65: Device not found at IOADDRESS.
Meaning The PCnet device cannot be found at the IO Address specified in NET.CFG.
Action Verify that the IO Address in NET.CFG matches with the board. Otherwise, remove the PORT keyword from NET.CFG.
Message PCNTNW-OS2-66: PCI scan can only execute on a 386 and higher processor.
Meaning The PCI bus is not available on your system. The PCI bus is only supported on a 386 or higher processor.
Action Do not specify PCI for BUSTYPE with your current system setup.
Message PCNTNW-OS2-67: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Use the BUSTYPE keyword to specify PCI1 or PCI2 values if the PCI mechanism is known for your system. Otherwise, replace the PCI board.
Message PCNTNW-OS2-68: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the VL board is physically installed properly. Otherwise, replace the VL board.
Message PCNTNW-OS2-69: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA+ board.
Message PCNTNW-OS2-70: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA board.
Message PCNTNW-OS2-71: ISA DMA number out of range.
Meaning The PCnet-ISA board only supports four DMA channels.
Action Specify a valid DMA number in NET.CFG to match the jumper setting on the PCnet-ISA board. Please refer to the Software Keyword section of this manual for the available range of values.
Message PCNTNW-OS2-73: Unable to allocate memory.
Meaning The driver could not allocate memory for the virtual board.
Action Check the system configuration.
Message PCNTNW-OS2-74: VESA scan can only execute on a 386 and higher processor.
Meaning The VESA bus is not available on your system. The VESA bus is only supported on a 386 or higher processor.
Action Do not specify VESA for BUSTYPE with your current system setup.
Message PCNTNW-OS2-80: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove DMA from NET.CFG file.
Message PCNTNW-OS2-81: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove DMA from NET.CFG file.
Message PCNTNW-NW-054: The board did not respond to the initialization command.
Meaning The board did not respond when the software tried to initialize it.
Action Make sure that the board is physically present in the system. Check the I/O address and other settings and make sure that these jumper values match the software driver settings.
Message PCNTNW-NW-58: The board did not respond to the initialization command.
Meaning The DMA and IRQ settings may be incorrect with the hardware settings. Otherwise, the EEPROM may be corrupted.
Action Verify the DMA and IRQ settings in NET.CFG match the hardware jumper settings, or verify that the EEPROM on-board is programmed
correctly.
Message PCNTNW-NW-59: Buffers could not be locked.
Meaning An attempt was made to lock buffers for direct access. The attempt failed.
Action Check the memory manager documentation and make sure that it supports a memory manager VDS (Virtual DMA Server). If in doubt,
either use another memory manager or do not use it.
Message PCNTNW-NW-66: The cable might be disconnected on the board.
Meaning The BNC cable may not be connected to the BNC connector on the board.
Action Connect the BNC cable to the board.
Message PCNTNW-NW-071: The matching virtual adapter could not be found.
Meaning You tried to load another instance of the driver with a different I/O address. This new board could not be found.
Action Make sure that the board is physically present. Also check the I/O settings of the board with the settings supplied to the driver.
Message PCNTNW-NW-072: A resource tag in unavailable.
Meaning The driver tried to allocate some resources. These resources were unavailable.
Action Try to add and/or free some memory in the system. Reboot and restart the system.
Message PCNTNW-NW-073: Unable to allocate memory.
Meaning The driver failed to allocate the memory needed for normal operation.
Action Add more memory in the system or else free some memory resources in the system and reboot the machine.
Message PCNTNW-NW-074: The hardware interrupt cannot be set.
Meaning An attempt was made to initialize a given hardware interrupt. The attempt was not successful.
Action Check the hardware system. Make sure the board jumpers are set to correct interrupt numbers. Also make sure that no other device is using this interrupt in the system.
Message PCNTNW-NW-075: The MLID cannot be registered with the LSL.
Meaning An error occurred while the driver was trying to register with Link Support Layer.
Action Check the version of Netware Operating System. Make sure that this driver is for the version of Netware you are running. Restart the complete system.
Message PCNTNW-NW-076: The polling procedure cannot be added.
Meaning An error occurred while the driver was adding polling procedure to the Netware Operating System. polling routines.
Action Check the version of Netware Operating System. Make sure that this driver is for the version of Netware you are running.
Restart the complete system.
Message PCNTNW-NW-077: The event notification cannot be registered.
Meaning The driver failed to register its event notification routines with the Netware operating system.
Action Check the version of Netware Operating System. Make sure that this driver is for the version of Netware you are running.
Restart the complete system.
Message PCNTNW-NW-078: The firmware file cannot be read.
Meaning The driver tried to read a firmware file. The read process failed.
Action Make sure that the support files accompanying the driver are present. Reboot and restart the complete system.
Message PCNTNW-NW-079: The MLID did not initialize MSMTx Free Count.
Meaning The MSMTx Free Count is not initialized correctly.
Action Restart the system. If error is still present report it to the Card Manufacturers.
Message PCNTNW-NW-084: Unable to allocate memory below the 16 megabyte boundary.
Meaning A request was made to allocate memory below 16 megabyte. The request failed to complete successfully.
Action Free some memory below 16 megabyte or add some more memory below 16 megabyte boundary.
Message PCNTNW-NW-086: The driver parameter block is too small.
Meaning The driver parameter block is too small.
Action Restart the system. If the error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-087: The media parameter block is too small.
Meaning The driver media parameter block is too small.
Action Restart the system. If error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-091: The hardware configuration conflicts.
Meaning You tried to load a new frame type for the existing adapter. The hardware assumption made in doing so are incorrect.
Action Check the manual of your card and also check the physical hardware. Make sure that your hardware configuration matches
the software settings.
Message PCNTNW-NW-092: Cannot schedule AES without an HSM routine.
Meaning The Netware Operating System needs a Hardware Support Module routine before it can schedule an AES event.
Action Restart the system. If the error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-093: Cannot schedule interrupt time call back without an HSM routine.
Meaning The driver needs a Hardware Support Module routine before it can schedule an interrupt time call back.
Action Restart the system. If the error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-094: Cannot set hardware interrupt without an HSM routine.
Meaning The driver needs a hardware interrupt call back routine before it sets the interrupt.
Action Restart the system. If the error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-095: Cannot add polling without an HSM routine.
Meaning The driver needs an HSM polling routine before it can start the polling process.
Action Restart the system. If the error is still present, report it to the Card Manufacturer.
Message PCNTNW-NW-026: The MSM in unable to parse a required custom keyword.
Meaning An incorrect parameter keyword was entered by the user.
Action Check the manual and make sure the keyword entered is correctly spelled. Reload the driver.
Message PCNTNW-NW-126: The group bit in the node address override was cleared.
Meaning The IEEE address has a group bit indicating that an address belongs to a group of station. This bit is only used for destination address and not source address. You tried to enter a source address with this bit set. The driver cleared the group bit of the source address.
Action None.
Message PCNTNW-NW-127: The local bit in the node address override was set.
Meaning The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address
override capabilities of this driver to enter a new address then the local
bit should be set. You entered an address without the local bit set. The
driver has set the local bit.
Action None.
Message PCNTNW-NW-164: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident the PCnet board.
Message PCNTNW-NW-165: Device not found at IOADDRESS.
Meaning The PCnet device cannot be found at the IO Address specified in NET.CFG file.
Action Verify that the IO Address in NET.CFG matches with the board. Otherwise, remove the PORT keyword from NET.CFG file.
Message PCNTNW-NW-167: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Use the BUSTYPE keyword to specify PCI1 or PCI2 values, if the PCI mechanism is known for your system. Otherwise, replace the PCI board.
Message PCNTNW-NW-168: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the VL board is physically installed properly. Otherwise, replace the VL board.
Message PCNTNW-NW-169: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA+ board.
Message PCNTNW-NW-170: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the ISA board is physically installed properly. Otherwise, replace the PCnet-ISA board.
Message PCNTNW-NW-180: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove DMA from NET.CFG file.
Message PCNTNW-NW-181: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove DMA from NET.CFG file.
1) Heart Beat Error
This error indicates that a collision input on the AUI failed to activate within 20 network bit times after terminating transmission. This indicates a transmitter problem.
2) Memory Time Out
This counter is incremented when the board does not get bus master resource to read or write to memory in the systems
3) Tx Babbling Error
This counter indicates that the transmitter has been transmitting longer than the time required to send the maximum size frame. This counter is incremented when 1,519 bytes or greater are transmitted.
4) Tx Under Flow Error
This error indicates that a frame transmission was aborted because the board could not get the data from memory in time.
5) Tx Buffer Error
This error indicates that the frame buffers which were queued for transmission were not set up correctly by the software.
6) Rx ECBs Over 16 MBytes Count
This is a standard statistics counter counting receive Event Control Blocks which are located above 16 MBytes.
7) Tx ECBs Over 16 MBytes Count
This is a standard statistics counter counting transmit Event Control blocks which are located above 16 MBytes.
8) Packet Used 2ECBs
This is a statistic counter indicating that a packet used two Event Control Blocks.
9) Rx ECBs Double Copy Count
If the receive Event Control Blocks are located above 16 MBytes and the network adapter card is a 16-bit adapter card (i.e., PCnet-ISA, PCnet-ISA+, or PCnet-ISA II), then the system needs to copy the received packets to the Rx ECBs. This statistics counter counts these events.
10) Tx ECBs Double Copy Count
If the transmit Event Control Blocks are located above 16 MBytes and the network adapter card is a 16-bit adapter card (i.e., PCnet-ISA, PCnet-ISA+, or PCnet-ISA II), then the system needs to copy the transmit packets to the Tx ECBs. This statistics counter counts these events.
Message PCNTND-DOS-1:Unable to open Protocol Manager.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-6: Out of memory while allocating buffers.
Meaning The driver failed to allocate buffers.
Action Check your system configuration, including TX/RX Buffers in PROTOCOL.INI file.
Message PCNTND-DOS-7: Protocol Manager device error.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-8: Bad status for Protocol Manager.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-9: Cannot find PROTOCOL.INI entry.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-10: Protocol Manager ioctl failed.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-11: Protocol Manager registration failed.
Meaning The NDIS stack is not configured correctly.
Action Check and correct your configuration.
Message PCNTND-DOS-13: Physical address from VDS is above 16M, cannot handle it.
Meaning The PCnet-ISA cannot handle buffers above 16 Megabytes. (16-bit addressing)
Action Modify your system configuration to load the driver below 16 Megabytes.
Message PCNTND-DOS-15: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message PCNTND-DOS-16: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Otherwise, replace the board.
Message PCNTND-DOS-17: PCI scan can only execute on a 386 and higher processor.
Meaning The PCI bus is not available on your system. The PCI bus is only supported on systems with a 386 or higher processor.
Action Do not specify PCI for BUSTYPE with your current system.
Message PCNTND-DOS-18: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the PCnet-ISA+ board is physically installed properly. Otherwise, replace the board.
Message PCNTND-DOS-19: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the PCnet-32 board is physically installed properly. Otherwise, replace the board.
Message PCNTND-DOS-20: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the PCnet-ISA board is physically installed properly. Otherwise, replace the board.
Message PCNTND-DOS-21: Board failed checksum test. Please run configuration utility.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident board.
Message PCNTND-DOS-22: PCNET DMA doesn't match protocol.ini.
Meaning The specified DMA setting does not match the hardware setting for the PCnet device.
Action Remove the DMA setting from PROTOCOL.INI or match the DMA setting in PROTOCOL.INI with the hardware jumper setting.
Message PCNTND-DOS-23: WARNING: PCNET IRQ found =
Meaning The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.
Action Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting in PROTOCOL.INI with the hardware jumper setting.
Message PCNTND-DOS-24: PCNET IRQ doesn't match protocol.ini
Meaning The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.
Action Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting in PROTOCOL.INI with the hardware jumper setting.
Message PCNTND-DOS-25: PCI scan specified, PCI bus not found!
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Otherwise, replace the board.
Message PCNTND-DOS-26: Interrupt handler is not working, please check your protocol.ini
Meaning IRQ handler is not working. It is possible that PROTOCOL.INI does not match the hardware (PCnet-ISA only).
Action Check your hardware jumper settings.
Message PCNTND-DOS-27: ISA IRQ number out of range
Meaning The PCnet-ISA only supports eight IRQ channels.
Action Specify a valid IRQ number in PROTOCOL.INI to match the jumper setting on the ISA board. Refer to the Software Keyword section of this manual for the available range of values.
Message PCNTND-DOS-28: ISA DMA number out of range
Meaning The PCnet-ISA only supports four DMA channels.
Action Specify a valid DMA number in PROTOCOL.INI to match the jumper setting on the ISA board. Refer to the Software Keyword section of this manual for the available range of values.
Message PCNTND-DOS-29: WARNING: DMA number is not necessary for PCI device
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove the DMA setting in PROTOCOL.INI.
Message PCNTND-DOS-30: WARNING: DMA number is not necessary for VESA device
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove the DMA setting in PROTOCOL.INI file.
Message PCNTND-DOS-31: DMA number is already in use by another PCNET device
Meaning The specified DMA number is already in use by another PCnet device.
Action Modify the DMA setting on the hardware and/or modify the DMA setting in PROTOCOL.INI file.
Message PCNTND-DOS-32: IRQ number is already in use by another PCNET device.
Meaning The specified IRQ number is already in use by another PCnet device.
Action Modify the IRQ setting on the hardware and/or modify the IRQ setting in PROTOCOL.INI file.
Message PCNTND-DOS-33: PCNET device with specified IOBASE is already in use.
Meaning The specified IO Address number is already in use by another PCnet device.
Action Modify the IO Address setting on the hardware and/or modify the IO Address setting in PROTOCOL.INI file.
Windows NT
Windows NT error messages are logged into a log file. The user may view the file with the Event Viewer. Error messages appear with the "PCNTN3" prefix followed by a "Missing Configuration Parameter" message and several hex numbers. The hex numbers must be converted to decimal in order to correspond to the error numbers used in this manual.
Message PCNTN3-9: IO base address is already in use by another PCNET device.
Meaning The specified IO Address number is already in use by another PCnet device.
Action Modify the IO Address setting on the hardware and/or modify the IO Address setting in the setup dialog box.
Message PCNTN3-13: IRQ and/or DMA number is already in use by another PCNET device.
Meaning The specified IRQ and/or DMA is already specified by another PCnet device.
Action Modify the IRQ and/or DMA settings in the setup dialog box.
Message PCNTN3-17: PCI scan specified, PCI bus not found.
Meaning PCI scan specified on a non-PCI system..
Action Modify the bus to scan in setup dialog box to the correct bus to scan.
Message PCNTN3-18: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Otherwise, replace the board.
Message PCNTN3-19: LanceOpenAdapter failed.
Meaning The configuration is setup incorrectly.
Action Re-run the setup program.
Message PCNTN3-20: Device at specified IO base address not found.
Meaning The PCnet device cannot be found at the specified IO Address.
Action Verify that the IO Address matches with the board. Otherwise, remove the IO Address specification from the setup.
Message PCNTN3-21: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message PCNTN3-22: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the PCnet-ISA+ board is physically installed properly. Otherwise, replace the board.
Message PCNTN3-23: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the PCnet-32 board is physically installed properly. Otherwise, replace the board.
Message PCNTN3-24: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the PCnet-ISA board is physically installed properly. Otherwise, replace the board.
Message pnt0-1: PCI search specified, PCI bus not found!
Meaning PCI scan specified on non-PCI system.
Action Run netconfig to correct BUS to scan.
Message pnt0-2: PCI search specified, PCI device not found!
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Run netconfig to search for another PCnet device or verify that the PCI board is physically installed properly.
Message pnt0-6: Can't allocate memory for the board during interrupt! Please check your Streams parameters
Meaning System is out of Streams memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of Streams blocks for the failing size.
Message pnt0-7: Can't allocate memory for the board during reset! Please check your Streams parameters.
Meaning System is out of Streams memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of Streams blocks for the failing size.
Message pnt0-8: PNP search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA+ board is physically installed properly.
Message pnt0-9: VESA search specified, device not found!
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-32 board is physically installed properly.
Message pnt0-10: ISA search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA board is physically installed properly.
Message pnt0-11: device not found!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-12: device failed checksum test!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-13: add_intr_handler failed! Interrupts already enabled.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-19: IRQ found for PCnet hardware doesn't match space.c!
Meaning This is a warning message in regards to the IRQ found in the system.
Action Ignore this message if you are sure this is what you want or otherwise run netconfig to modify the IRQ settings.
Message pnt0-20: add_intr_handler failed! Unknown interrupt type.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-21: add_intr_handler failed! Out of range interrupt number.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-22: add_intr_handler failed! Out of range IPL
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-23: add_intr_handler failed! Vector already occupied.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-24: add_intr_handler failed! Vector already shared at different IPL.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-25: DMA found for PCNET hardware doesn't match space.c!
Meaning There is an error with the DMA number found and space.c.
Action Run netconfig to set the correct DMA setting.
Message pnt0-26: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove the DMA number setting for the PCI board.
Message pnt0-27: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove the DMA number setting for the VL board.
Message pnt0-28: DMA number is already in use by another PCNET device.
Meaning The specified DMA number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-29: IRQ number is already in use by another PCNET device.
Meaning The specified IRQ number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-30: device with specified IOBASE is already in use.
Meaning The specified IO Address is already in use by another device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-31: IO address is not necessary for PCI device.
Meaning The IO Address is not necessary for the PCI device.
Action Remove the assigned IO Address for the PCnet-PCI device.
Message pnt0-1: PCI search specified, PCI bus not found!
Meaning PCI scan specified on non-PCI system.
Action Run netconfig to correct BUS to scan.
Message pnt0-2: PCI search specified, PCI device not found!
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Run netconfig to search for another PCnet device or verify that the PCI board is physically installed properly.
Message pnt0-6: Can't allocate memory for the board during interrupt! Please check your Streams parameters.
Meaning System is out of Streams memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of Streams blocks for the failing size.
Message pnt0-7: Can't allocate memory for the board during reset! Please check your Streams parameters.
Meaning System is out of Streams memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of Streams blocks for the failing size.
Message pnt0-8: PNP search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA+ board is physically installed properly.
Message pnt0-9: VESA search specified, device not found!
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-32 board is physically installed properly.
Message pnt0-10: ISA search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA board is physically installed properly.
Message pnt0-11: device not found!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-12: device failed checksum test!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-13: add_intr_handler failed! Interrupts already enabled.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-19: IRQ found for PCnet hardware doesn't match space.c!
Meaning This is a warning message in regards to the IRQ found in the system.
Action Ignore this message if you are sure this is what you want or otherwise run netconfig to modify the IRQ settings.
Message pnt0-20: add_intr_handler failed! Unknown interrupt type.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-21: add_intr_handler failed! Out of range interrupt number.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-22: add_intr_handler failed! Out of range IPL.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-23: add_intr_handler failed! Vector already occupied.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-24: add_intr_handler failed! Vector already shared at different IPL.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-25: DMA found for PCNET hardware doesn't match space.c!
Meaning There is an error with the DMA number found and space.c.
Action Run netconfig to set the correct DMA setting.
Message pnt0-26: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove the DMA number setting for the PCI board.
Message pnt0-27: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove the DMA number setting for the VL board.
Message pnt0-28: DMA number is already in use by another PCNET device.
Meaning The specified DMA number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-29: IRQ number is already in use by another PCNET device.
Meaning The specified IRQ number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-30: device with specified IOBASE is already in use.
Meaning The specified IO Address is already in use by another device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-31: IO address is not necessary for PCI device.
Meaning The IO Address is not necessary for the PCI device.
Action Remove the assigned IO Address for the PCnet-PCI device.
Message pnt0-1: PCI search specified, PCI bus not found!
Meaning PCI scan is specified on non-PCI system.
Action Run netconfig to correct BUS to scan.
Message pnt0-2: PCI search specified, PCI device not found!
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Run netconfig to search for another PCnet device or verify that the PCI board is physically installed properly.
Message pnt0-6: Can't allocate memory for the board during interrupt parameters!
Meaning System is out of memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of blocks for the failing size.
Message pnt0-7: Can't allocate memory for the board during reset!
Meaning System is out of memory blocks.
Action Ask your system administrator to run "crash" utility and increase number of blocks for the failing size.
Message pnt0-8: PNP search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA+ board is physically installed properly.
Message pnt0-9: VESA search specified, device not found!
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-32 board is physically installed properly.
Message pnt0-10: ISA search specified, device not found!
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Run netconfig to search for another PCnet device or verify that the PCnet-ISA board is physically installed properly.
Message pnt0-11: device not found!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-12: device failed checksum test!
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message pnt0-13: add_intr_handler failed! Interrupts already enabled.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-14: Can't locate hardware.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet adapter card is installed or replace the resident PCnet card.
Message pnt0-15: No more devices to open!
Meaning The driver cannot find any more PCnet devices.
Action Verify that additional PCnet adapter cards are present or replace the PCnet card that fails to respond.
Message pnt0-17: Device fault... Reset initiated!
Meaning The driver has been reset due to a device fault.
Action Replace the PCnet adapter card.
Message pnt0-19: IRQ found for PCnet hardware doesn't match pnt.conf!
Meaning This is a warning message in regards to the IRQ found in the system.
Action Ignore this message if you are sure this is what you want or otherwise run netconfig to modify the IRQ settings.
Message pnt0-20: add_intr_handler failed! Unknown interrupt type.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-21: add_intr_handler failed! Out of range interrupt number.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-22: add_intr_handler failed! Out of range IPL.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-23: add_intr_handler failed! Vector already occupied.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-24: add_intr_handler failed! Vector already shared at different IPL.
Meaning The IRQ specified or found conflicts with other devices in the system.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-25: DMA found for PCNET hardware doesn't match pnt.conf!
Meaning There is an error with the DMA number found and pnt.conf.
Action Run netconfig to set the correct DMA setting.
Message pnt0-26: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove the DMA number setting for the PCI board.
Message pnt0-27: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove the DMA number setting for the VL board.
Message pnt0-28: DMA number is already in use by another PCNET device.
Meaning The specified DMA number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-29: IRQ number is already in use by another PCNET device.
Meaning The specified IRQ number is already in use by another PCnet device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-30: device with specified IOBASE is already in use.
Meaning The specified IO Address is already in use by another device.
Action Modify your hardware settings and/or run netconfig to match the hardware settings.
Message pnt0-31: IO address is not necessary for PCI device.
Meaning The IO Address is not necessary for the PCI device.
Action Remove the assigned IO Address for the PCnet-PCI device.
Message PCNTPK-DOS-1: PCNTPK [-n] [-d] [-w] <INT=packet_int_no>
[IRQ=int_no] [IOADDR=io_addr] [DMA=dma_no]
[BUSTYPE=bus] [DMAROTATE] [TP] [LED0=xx] [LED1=xx] [LED2=xx]
[LED3=xx]
Meaning The command line entered with associated parameters is incorrect.
Action Refer to the board user manual and make sure that the command line and its associated parameters are correct.
Message PCNTPK-DOS-2: Unable to reset the PCnet device.
Meaning The software could not reset the board.
Action Verify that a PCnet board is physically installed properly or replace the PCnet board.
Message PCNTPK-DOS-3: Unable to initialize the PCnet device.
Meaning The software could not initialize the board.
Action Check the I/O address, Interrupt, and DMA settings of the board. Make sure that the driver settings of these three parameters
match the hardware setting. If the settings are correct, and you still get this message, then replace the board.
Message PCNTPK-DOS-4: VDS memory allocation failed.
Meaning The driver could not allocate memory for the virtual board.
Action Check the system configuration.
Message PCNTPK-DOS-5: There is already a packet driver at xxxx.
Meaning The driver is already loaded at this memory location.
Action Do not load the driver again.
Message PCNTPK-DOS-6: <IRQ=int_no> should be between 0 and 15 inclusive.
Meaning The specified IRQ is out of range for the PCnet board.
Action Use valid IRQ values. Refer to the Software Keyword section of this manual for valid ranges.
Message PCNTPK-DOS-7: Packet driver failed to initialize the board.
Meaning The board initialization failed.
Action Replace the board.
Message PCNTPK-DOS-8: <INT=packet_int_no> should be in the range 0x60 to 0x80.
Meaning The specified software interrupt is out of the allowable range.
Action Modify the INT value.
Message PCNTPK-DOS-9: DMA number is not necessary for PCI device.
Meaning The PCnet-PCI board does not require a DMA setting.
Action Remove the DMA setting.
Message PCNTPK-DOS-10: DMA number is not necessary for VESA device.
Meaning The PCnet-32 board does not require a DMA setting.
Action Remove the DMA setting.
Message PCNTPK-DOS-11: PnP device DMA number mismatch.
Meaning The specified DMA number mismatches with the DMA number assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action Remove the DMA setting.
Message PCNTPK-DOS-12: PCI device IRQ number mismatch.
Meaning The specified IRQ number mismatches with the IRQ number assigned by the PCI BIOS.
Action Remove the IRQ setting.
Message PCNTPK-DOS-13: VESA device IRQ number mismatch.
Meaning The specified IRQ number mismatches with the IRQ setting designated by the on-board EEPROM.
Action Remove the IRQ setting.
Message PCNTPK-DOS-14: PnP device IRQ number mismatch.
Meaning The specified IRQ number mismatches with the DMA number assigned by the PnP Configuration Manager or by the on-board
EEPROM if PnP is disabled.
Action Remove the IRQ setting.
Message PCNTPK-DOS-15: Device not found.
Meaning The driver cannot find any PCnet device.
Action Verify that a PCnet board is installed or replace the resident PCnet board.
Message PCNTPK-DOS-16: Device not found at IOADDRESS.
Meaning The PCnet device cannot be found at the IO Address specified.
Action Verify that the specified IO Address matches with the board. Otherwise, remove IOADDR keyword during installation.
Message PCNTPK-DOS-17: PCI scan can only execute on a 386 and higher processor.
Meaning The PCI bus is not available on your current system. The PCI bus is only supported on systems with a 386 or higher processor.
Action Do not specify PCI for BUSTYPE during installation.
Message PCNTPK-DOS-18: PCI scan specified, device not found.
Meaning The driver cannot locate the PCnet-PCI board on the PCI bus.
Action Verify that the PCI board is physically installed properly. Otherwise, replace the board.
Message PCNTPK-DOS-19: VESA scan specified, device not found.
Meaning The driver cannot locate the PCnet-32 board on the VL bus.
Action Verify that the VL board is physically installed properly. Otherwise, replace the board.
Message PCNTPK-DOS-20: PnP scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA+ board on the ISA bus.
Action Verify that the PCnet-ISA+ board is physically installed properly. Otherwise, replace the board.
Message PCNTPK-DOS-21: ISA scan specified, device not found.
Meaning The driver cannot locate the PCnet-ISA board on the ISA bus.
Action Verify that the PCnet-ISA board is physically installed properly. Otherwise, replace the board.
Message PCNTPK-DOS-22: ISA DMA number out of range.
Meaning The PCnet-ISA only supports four DMA channels.
Action Specify a valid DMA number to match the jumper setting on the ISA board. Refer to the Software Keyword section of this manual for the available range of values.
Message PCNTPK-DOS-23: ISA IRQ number out of range.
Meaning The PCnet-ISA only supports eight IRQ channels.
Action Specify a valid IRQ number to match the jumper setting on the ISA board. Refer to the Software Keyword section of this manual
for the available range of values.
Message Packet driver is at segment xxxx.
Meaning The memory address where Packet Driver is loaded is xxxx.
Action None.
Message Packet interrupt number xxxx.
Meaning The interrupt number used by the Packet Driver is xxxx.
Action None.
Message My Ethernet address is xxxx.
Meaning The Ethernet address of this station is xxxx.
Action None.
Message My ARCnet address is xxxx.
Meaning The ARCnet address of this station is xxxx.
Action None.