                              ERROR.TXT
                              =========

  This file contains the error messages displayed by the EtherWORKS 3
diagnostics along with some causes and troubleshooting tips.  

  EtherWORKS 3 diagnostics are normally executed prior to the driver being
loaded to make sure the hardware is functional before attempting to 
connect to the network.  If any of the diagnostic tests fail, the driver
will not load and the network connection cannot be made.  A diagnostic
failure can be the result of an incorrect software installation, a 
resource conflict, or a defective EtherWORKS 3 module.  

  The following is a guide that can help you track down the reason why the 
EtherWORKS 3 module may have failed its diagnostic test.  The text error
messages in quotes are followed by some most likely causes. 

   

"Unable to determine I/O address", 
"Ethernet Address ROM CRC failed",
"Wrong Card ID",
"Failed to detect CRC error",
"Register R/W Test failed",
"EEPROM Checksum Test Failed":

  Check that your network configuration file (PROTOCOL.INI for NDIS users, 
NET.CFG for ODI users) settings match the settings of the EtherWORKS 3 
module.  You can use NICSETUP to view the EtherWORKS 3 module settings.
  
  Make sure there is no I/O conflict.  An I/O conflict is when two modules
live in the same I/O space, which is not allowed.  Try "hardstrapping" the
EtherWORKS 3 module and use NICSETUP to program the module to live in 
another I/O space.  Refer to the README file in this directory for details
about "hardstrapping" the EtherWORKS 3 module.

  If neither of the above works, you may have a defective EtherWORKS 3
module.  Contact your Digital Sales representative.
-------------------------------------------------------------------------- 

"Memory Address Test Failed",
"Memory Knaizuk Test Failed",
"Memory Bitwalk Test Failed",
"Queue, Free Memory Queue Test Failed",
"Queue, Receive Queue Test Failed",
"Queue, Transmit Queue Test Failed",
"Queue, Transmit Done Queue Test Failed",
"Queue, Page Index Register Test Failed",
"Queue, I/O Page Register Test Failed",
"Queue, Memory Page Register Test Failed":

  Check that your network configuration file (PROTOCOL.INI for NDIS users, 
NET.CFG for ODI users) settings match the settings of the EtherWORKS 3 
module.  You can use NICSETUP to view the EtherWORKS 3 module settings.
  
  Make sure there is no memory conflict.  A memory conflict is when two 
modules or software wants to live in the same memory space, which is not 
allowed.  Try "hardstrapping" the EtherWORKS 3 module and use NICSETUP to
program the module to live in another memory space.  Refer to the README 
file in this directory for details about "hardstrapping" the EtherWORKS 3
module.

  Memory managers such as EMM386 or QEMM must be explicitly told not to
use the high memory area where the EtherWORKS 3 module resides.  Each of 
these memory managers has a command to exclude regions of memory.  The 
command to exclude a memory region should be added to the line in 
CONFIG.SYS that installs the memory manager.  Refer to your memory 
manager's manual for detailed instructions.

  If none of the above works, you may have a defective EtherWORKS 3
module.  Contact your Digital Sales representative.
-------------------------------------------------------------------------- 

"IRQ Test failed"
"ICR, Interrupt Enable Test Failed",
"ICR, TNE Mask Test Failed",
"ICR, RNE Mask Test Failed",
"ICR, TXD Mask Test Failed",
"ICR, RXD Mask Test Failed":

  Check that your network configuration file (PROTOCOL.INI for NDIS users, 
NET.CFG for ODI users) settings match the settings of the EtherWORKS 3 
module.  You can use NICSETUP to view the EtherWORKS 3 module settings.
  
  Make sure there is no interrupt line (IRQ) conflict.  An IRQ conflict 
is when two devices want to use the same interrupt line, which is not 
allowed.  Try "hardstrapping" the EtherWORKS 3 module and use NICSETUP to
program the module to use another IRQ line.  Refer to the README file in 
this directory for details about "hardstrapping" the EtherWORKS 3 module.
-------------------------------------------------------------------------- 

"Xmit Status, Xmit Valid bit not set",
"Xmit Status, SQE check failed",
"Xmit Status, ECL failed",
"Xmit Status, LCL failed",
"Xmit Status, ID failed",
"Xmit Status, NCL failed",
"Recv Status, IAM failed",
"Recv Status, MCM failed",
"Recv Status, PLL failed",
"Recv Status, CRC failed",
"Recv Status, DBE failed",
"Xmit Control, STOP Test failed",
"Xmit Control, Q-Mode Test failed",
"Xmit Control, PAD Test failed",
"Xmit Control, IFC Test failed",
"Xmit Control, ISA Test failed",
"CSR, Runt Accept Test failed",
"CSR, Promiscuous Mode Enable Test failed",
"CSR, Multicast Enable Test failed",
"CSR, Transmit Not Empty bit Failed",
"CSR, Receive Not Empty bit Failed",
"CSR, Transmit Disable Test Failed",
"CSR, Receive Disable Test Failed",
"Transmit Packet Size over 1514",
"Receive Packet Size over 1514",
"Transmit Packet Size is zero",
"Receive Packet Size is zero",
"Transmit Failure",
"Receive Failure",
"Transmit Timeout",
"Receive Timeout":

  These errors are network related test failures.  If your network driver
was installed before running the diagnostics, power down the PC and
start again.  If the error messages persist, you may have a defective 
EtherWORKS 3 module.  Contact your Digital Sales representative.
-------------------------------------------------------------------------- 

"CR, Loopback Test Failed",
"CR, Full Duplex Test Failed":

  These errors are supplemental network tests that require loopback 
connectors for Thinwire or a Twisted Pair repeater link for Twisted Pair
testing.  The Loopback and Full Duplex tests are only available when 
diagnostics are run from the NICSETUP 'Diagnostic' menu.   
  In order to test the Thinwire coax port (when present), the 
EtherWORKS 3 module must be removed from the live network and the Thinwire
connector properly terminated with a T-connector and two terminators.
Without proper termination the Loopback or Full Duplex test will fail. 

  To test the Twisted Pair port (when present), the EtherWORKS 3 module
must have a valid link to a Twisted Pair repeater.  The EtherWORKS 3
modules that support TP have a green LED that lights when the link to the
TP repeater is good.  If the green LED is not lit, check your TP cabling
and your TP repeater port.

  To test the AUI (also referred to as Thickwire) connector, the AUI port
must be selected using the gang-jumper on the EtherWORKS 3 module and an 
AUI loopback plug must be installed before running the diagnostics.

  If the error messages persist, you may have a defective EtherWORKS 3 
module.  Contact your Digital Sales representative.

-----------------------------------------------------------------------------

 "Diagnostic result code FF" 
 
  This message has been seen to appear when the module is configured 
incorrectly on EISA machine's. Make sure the EtherWORKS 3 card is
configured correctly under your PC's EISA Configuration Utility(ECU) with
the proper !DEC20x0.CFG file.

  If this message is appearing on an ISA machine check that your network 
configuration file (PROTOCOL.INI for NDIS users, NET.CFG for ODI users) 
settings match the settings of the EtherWORKS 3 module. You can use NICSETUP 
to view the EtherWORKS 3 module settings.
  
  Make sure there is no I/O conflict.  An I/O conflict is when two modules
live in the same I/O space, which is not allowed.  Try "hardstrapping" the
EtherWORKS 3 module and use NICSETUP to program the module to live in 
another I/O space.  Refer to the README file in this directory for details
about "hardstrapping" the EtherWORKS 3 module.

  If neither of the above works, you may have a defective EtherWORKS 3
module.  Contact your Digital Sales representative.
-----------------------------------------------------------------------------
