4 NT DRIVER FOR ICL ETHERTEAM16 4.1 Current Status of the Driver 4.2 Installation of the Driver The NT drivers for EtherTeam16 can be found from the subdirectory NDIS3\NT have the following file names: ETHIIE.SYS NT Driver OEMSETUP.INF OEM Setup File ETHIIE.HLP OEM Setup Help File To install the NT Driver for ICL EtherTeam16, do the following: 1. Use the Windows NT Control Panel to install the driver. Give the path A:\NDIS3\NT when prompted for the OEM Driver diskette. 1. Select the interrupt number. The interrupt number of EtherTeam16 is SW selectable and must be defined (there is no default value for it). 2. Select the I/O Base Address according to the jumpering of your adapter. The value AUTO means that the adapter is searched from the possible I/O Base Addresses. NOTE! The I/O Base Addresses can be defined as AUTO although several adapters are installed. In this case, adapter instances are searched and allocated in the following order: 0300, 0310, 0320, 0290 NOTE! In case of several adapters installed, do not use any "mixed" definitions for the I/O Base Address. Either define them all explicitly or leave them all AUTO. 3. Select the Transceiver. The transceiver must be given explicitly (BNC, TP or DIX(AUI)). There is no AUTO mode implemented to detect automatically the network connection. 4.3 Advanced Installation Features There are some keywords detected by the driver which do not appear in the Network from Control Panel, but can be affected by the NT Registry Editor (REGEDT32). NOTE! These are for special purposes only, and are not required in normal installation. To define these parameters, start REGEDT32 from APPLICATIONS and then select the parameters of EtherTeam16 Driver by selecting the driver parameters from the menu as follows: HKEY_LOCAL_MACHINE on Local Machine SYSTEM CurrentControlSet Services ETHIIE01 Parameters If more adapters are installed, then you must select the parameters of the adapter instance concerned, for example of ETHIIE02. You can change the value of a parameter by selecting the parameter field and giving its new value. The current release of the driver contains the following parameters selectable by the REGEDIT32: 1. NetworkAddress Overrides the permanent network address of the card. The value is a hexadecimal string of 12 digits, e.g. 00004B010203. Possible values : Any non-multicast address. Default : The burned-in address of the adapter. 2. FifoDepth Defines the depth of the FIFO on NIC as word transfers. Possible values : 1, 2 or 4. Default : 1. NOTE! Do not touch this parameter. It is for special purposes only. 4.4 Driver Error Codes The driver writes into log information about initialisation or runtime errors. Use the Event Viewer from Administrative Tools to view the contents of the Log. The texts appearing in the Description Field of Event Detail are according to the NDIS standard messages. The value N in the label of the message (e.g. Ethiie0N) tells the adapter instance which has created the message. Because all possible driver errors cannot be described directy with the standard messages, the log also contains more detailed error info in binary format. To get it, view the Data Field as Words. The error code (word) can be found from offset 002Ch. The following is is a list of the errors detected by the driver and stored to the Event Log. Most of these errors are detected during driver initialisation only , but some even runtime. There is a limitation for the number of how many times the runtime errors are logged. 1. Ethiie0N : Does not support the configuration supplied. There is something wrong with the configuration registry. The binary error code in the Event Log is: 0012 = Invalid I/O Address 0013 = Invalid Interrupt Number 0016 = Multiple adapters not supported in multiprocessor system Use the REGEDT32 to check the I/O Address and Interrupt Number (These should never be wrong after Control Panel Setup, unless you have changed them with REGEDT32!). For HW reasons, the current release of the driver supports only one EtherTeam16 adapter in a multiprocessor system. Redefine your system. 2. Ethiie0N : Could not find an adapter. The driver could not find the adapter from the specified I/O-Base address, or from any possible address (if AUTO). The binary error code in the Event Log is: 0011 = Adapter Not Found Check that there is no conflict in the definition of the Base I/O- address, and that it does not overlap with any other adapter (range 10h!). 3. Ethiie0N : Could not connect to the interrup number supplied. The driver could not attach the interrupt handler, when requested the NDIS Wrapper to do it. The binary error code in the Event Log is: 0001 = Could not attach to the interrupt Ensure that no other adapter in the system is not using the interrupt number concerned. 4. Ethiie0N : Has determined that the adapter is not functioning properly. The driver has found the adapter but has failed in trying to initialize it. Or the driver has found an internal error in the Remote DMA while transferring data between the system memory and the adapter memory. The binary error code in the Event Log is: 0014 = Could not initialize the adapter 0019 = Remote DMA transfer error Check that there is no conflict in the definition of the Base I/O- address, and that it does not overlap with any other adapter. If these errors still exists, replace the adapter. 5. Ethiie0N : Could not allocate the resources necessary for operation. This is a collection of SW related errors detected by the driver in communication with the NDIS Wrapper, like: Allocating memory, creating filter data base, etc). The binary error code in the Event Log is: 0002 = Could not create a filter data base 0008 = Could not add a new binding to the filter data base. 0009 = Could not allocate data space for the open binding These errors typically relate to problems with the overall system, not in the NT driver itself. 6. Ethiie0N : Timed out during operation. The driver has detected that there was a pending transmit which did not terminate properly. This represents a fatal HW-error, due to which the hardware was re-initialized. The binary error code in the Event Log is: 0017 = HW Reinitized Due To Transmit Timeout If this error message appears repeatedly, check that the network is in condition.