1. E3KIT252.ZIP Driver
2. ERROR.TXT File Contents

ERROR.TXT Driver File Contents (E3KIT252.ZIP)

                              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 run through EZWORKS. If a user is having
a problem installing the EtherWORKS 3 module or establishing a network 
connection the diagnostics can be helpful in determining the problem. A 
diagnostic failure can be the result of an incorrect software installation, 
a resource conflict, or a defective EtherWORKS 3 module.  

    NOTE: Diagnostics will not run if an EtherWORKS 3 driver is
          currently installed.

  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":

  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 EZWORKS 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":

  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 EZWORKS 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":

  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 EZWORKS to
program the module to use another IRQ line.  Refer to the \README.TXT 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 the error message
occurs, 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 EZWORKS '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" 
 
  If this message is appearing it could mean a conflict with the PC's Shadow 
RAM. The user needs to enter his/her BIOS SETUP (on some PC's its the ADVANCED 
BIOS SETUP) and disable any memory area that would conflict with the memory 
area that the EtherWORKS 3 Network Buffer may be using. (This problem may be 
seen on Gateway 2000 P5-66 models)

  BIOS defaults to Shadowing the Upper Memory Blocks on these PCs, in 
particular C0000 and D0000. To enable Etherworks cards to be able to put 
their ROM info into the UMB, you must first create a "hole" in the UMB which 
is not shadowed. You can only create 1 such "hole"- in 16, 32, or 64K sizes.

   The steps to create this "hole" in the UMB(example uses D0000 w/ 2K mode):

        1-During Boot, hit F1 to enter CMOS SETUP 
        2-Select "ADVANCED CMOS SETUP" (return twice) 
        3-Select "DISABLE SHADOW MEMORY BASE" - Set address to 'D0000h' 
        4-Select "DISABLE SHADOW MEMORY SIZE" - Set to '16K' (or to
          amount needed) 
        5-ESC once to return to previous screen 6-Select "WRITE TO
          CMOS AND EXIT"

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