CONTENTS 1 NDIS DRIVERS FOR ICL ETHERTEAM16 2 NETWARE DRIVERS FOR ICL ETHERTEAM16 2.1 DOS ODI Workstation Driver 2.1.1 NetWare 3.11 2.1.2 NetWare 3.12 or NetWare 4.x 2.2 DOS IPX Workstation Driver 2.3 OS/2 ODI Workstation Driver 2.4 NetWare 386 ODI Server Driver 2.4.1 NetWare 3.11 2.4.2 NetWare 3.12 or NetWare 4.x 2.5 Novell NetWare NT Client 2.6 NetWare IPX 2.X Server Driver 3 NDIS 3.0 ENHANCED MODE WINDOWS DRIVER FOR ICL ETHERTEAM16 3.1 Current Status of the Driver 3.2 Installation of the Driver 3.3 Advanced Installation Features 4 NT DRIVER FOR ICL ETHERTEAM16 4.1 Current Status of the Driver 4.2 Installation of the Driver 4.3 Advanced Installation Features 4.4 Driver Error Codes 5 FTP PACKET DRIVER FOR ICL ETHERTEAM16 5.1 Installation of the Driver 6 DIAGNOSTICS 6.1 Installing the ADP to the Hard Disk 6.2 Installing the ADP to the ADP Diskette 6.3 Running the Diagnostics This installation disk contains both the ICL EtherTeam16 NDIS Drivers for LAN Manager, Novell NetWare Drivers, Windows NT Driver, Enhanced Mode Windows Driver, FTP Packet Driver and a Diagnostics program to check the system after installing the EtherTeam16 adapter. 1 NDIS DRIVERS FOR ICL ETHERTEAM16 The NDIS drivers for EtherTeam16 can be found from the subdirectories MSLANMAN.DOS\DRIVERS\ETHERNET\ETHIIE and MSLANMAN.OS2\DRIVERS\ETHERNET\ETHIIE have the following file names: ETHIIE.DOS DOS Driver ETHIIE.OS2 OS2 Driver PROTOCOL.INI Template To install the NDIS drivers (NDIS2) , just use the normal Lan Manager 2.x or Windows for Workgroups installation programs. 2 NETWARE DRIVERS FOR ICL ETHERTEAM16 These are short installation instructions for EtherTeam16 NetWare Drivers. For more detailed information, see the proper Novell documentation. 2.1 DOS ODI Workstation Driver The drivers can be found from the subdirectory NETWARE\DOSODI and have the following file names: ETHIIE.COM Workstation Driver ETHIIE.CFG Configuration Example ETHIIE.INS Installation Information File. 2.1.1 NetWare 3.11 To install the DOS ODI Workstation Driver for ICL EtherTeam16, do the following: 1. Copy the files ETHIIE.COM and ETHIIE.CFG from the Driver Diskette from subdirectory DOSODI to the directory containing the other system files on your Hard Disk, e.g. COPY A:\NETWARE\DOSODI\ETHIIE.COM C:\NETWARE\DOSODI COPY A:\NETWARE\DOSODI\ETHIIE.CFG C:\NETWARE\DOSODI 2. Make modifications to the driver options in ETHIIE.CFG (if needed), and rename ETHIIE.CFG as NET.CFG. 3. Create the AUTOEXEC.BAT file for DOS ODI Workstation. The following COM- files must be included, e.g. C:\NETWARE\DOSODI\LSL.COM C:\NETWARE\DOSODI\ETHIIE.COM C:\NETWARE\DOSODI\IPXODI.COM C:\NETWARE\DOSODI\NETX.COM 2.1.2 NetWare 3.12 or NetWare 4.x Installing DOS Workstation may take place using the INSTALL utility. Give the path A:\NETWARE\DOSODI when prompted for the OEM Driver Diskette. 2.2 DOS IPX Workstation Driver The drivers can be found from the subdirectory NETWARE\DOSIPX and have the following file names: ETHIIE.OBJ Workstation Shell Driver ETHIIE.LAN Configuration Description To install the DOS IPX Workstation Driver for ICL EtherTeam16, do the following: 1. Installation of the driver can take place either from a diskette or from a hard disk. For the diskette method, format an empty diskette with label LAN_DRV_487 (LAN_DRV_487 is the diskette label for ICL EtherTeam16 Driver Diskette for NetWare). Or for the disk method, create a subdirectory LAN_DRV_.487 to the NETWARE directory on your hard disk. 2. Copy the files ETHIIE.OBJ and ETHIIE.LAN from the Driver Diskette from the subdirectory DOSIPX either to the root of the LAN_DRV_487 diskette or to the NETWARE\LAN_DRV_.487 directory on your hard disk (depending on the selected method), e.g. COPY A:\NETWARE\DOSIPX\ETHIIE.OBJ C:\NETWARE\LAN_DRV_.487 COPY A:\NETWARE\DOSIPX\ETHIIE.LAN C:\NETWARE\LAN_DRV_.487 3. Use WSGEN to build up the Shell Driver. When selecting the configuration for the EtherTeam16, configuration 0 can be used in most cases. 4. Create the AUTOEXEC.BAT file for DOS IPX Workstation. The following COM- files must be included, e.g. C:\NETWARE\DOSIPX\IPX.COM C:\NETWARE\DOSIPX\NETX.COM 2.3 OS/2 ODI Workstation Driver The drivers can be found from the subdirectory NETWARE\OS2ODI and have the following file names: ETHIIE.SYS Workstation Driver ETHIIE.CFG Configuration Example To install the OS/2 ODI Workstation Driver for ICL EtherTeam16, do the following: 1. Use the INSTALL utility from the NetWare OS/2 Requester Diskette to install the OS/2 Workstation (if not yet installed). Select e.g. Novell NE2000 to be the driver (The INSTALL program does not know EtherTeam16). 2. Copy the files ETHIIE.SYS and ETHIIE.CFG from the Driver Diskette from subdirectory OS2ODI to the NETWARE directory on your hard disk, e.g. COPY A:\NETWARE\OS2ODI\ETHIIE.SYS C:\NETWARE COPY A:\NETWARE\OS2ODI\ETHIIE.CFG C:\NETWARE 3. Edit the CONFIG.SYS created by the INSTALL utility, replacing the installed driver definition by EtherTeam16, e.g. rem DEVICE=C:\NETWARE\NE2000.SYS DEVICE=C:\NETWARE\ETHIIE.SYS 4. Make modifications to the driver options in ETHIIE.CFG (if needed), and rename ETHIIE.CFG as NET.CFG. Ensure that NET.CFG is found on the search path (or from the root directory). 2.4 NetWare 386 ODI Server Driver The drivers can be found from the subdirectory NETWARE\386SRV and have the following file names: ETHIIE.LAN Server Driver ETHIIE.NCF Load Example ETHIIE.LDI Installation Information File. NOTE! The NetWare ODI Server Driver is implemented according to specification version 3.1, and requires MSM.NLM and ETHERTSM.NLM in order to work. 2.4.1 NetWare 3.11 The subdirectory NETWARE\386SRV\3.11 contains some other files (needed in 3.11 installation only) which you must copy to your system (provided that you do not already have them installed). MSM.NLM Novell Generic Media Support Module v2.14 ETHERTSM.NLM Novell Ethernet Topology Support Module v2.14 MONITOR.NLM NetWare Console Monitor v1.75 LSLENH.NLM LSL Chaining and Filtering Module v1.01 PATCHMAN.NLM Patch Manager for NetWare 3.11 v3.11 NOTE! If you already have these files (or more recent versions of them) in your system, use them instead of those on EtherTeam16i driver diskette. WARNING! DO NOT INSTALL the ETHIIE.LAN driver v1.03 to NetWare 3.11 Server, unless you are quite sure that the MSM.NLM (or MSM31X.NLM) of your system are compatible with the Rev 3.1 ODI driver (their versions should be at least 2.14). The possible incompatibility may even cause your system to crash! The subdirectory NETWARE\386SRV\3.11 still contains the "old" Rev 2.0 of the driver (ETHIIE.102), which you can use in 3.11 installations if you have problems to install the new driver. Rename it as ETHIIE.LAN, and do the installation as desribed below. None of the other modules except ETHIIE.LAN need to be copied or loaded then. To install the 3.11 ODI Server Driver for ICL EtherTeam16, do the following: 1. Copy the file ETHIIE.LAN from the Driver Diskette from subdirectory NETWARE\386SRV to a diskette labeled SYSTEM or into DOS directory on your Hard Disk to a subdirectory where all the system files have been copied initially, e.g. COPY A:\NETWARE\386SRV\ETHIIE.LAN C:\NETWARE 2. If needed, copy also the other files from the Driver Diskette from the subdirectory NETWARE\386SRV\3.11 into the DOS directory on your Hard Disk to a subdirectory where all the system files have been copied initially, e.g. COPY A:\NETWARE\386SRV\3.11\MSM.NLM C:\NETWARE COPY A:\NETWARE\386SRV\\3.11\ETHERTSM.NLM C:\NETWARE COPY A:\NETWARE\386SRV\3.11\LSLENH.NLM C:\NETWARE COPY A:\NETWARE\386SRV\\3.11\PATCHMAN.NLM C:\NETWARE 3. Start the Server, load LSLENH and the LAN Driver (The ETHIIE.LAN loads MSM and ETHERTSM modules implicitly), and bind the Network Driver, e.g. LOAD C:LSLENH LOAD C:ETHIIE INT=5 PORT=300 BIND C:IPX TO ETHIIE NET=xx 4. Establish a connection from a Workstation to the Server and copy the LAN driver file to the SYS:\SYSTEM directory on the Server, e.g COPY A:\NETWARE\386SRV\ETHIIE.LAN F:\SYSTEM 5. Copy also the following files to the SYSTEM directory (provided that you don't have more recent versions of them already installed in your system). COPY A:\NETWARE\386SRV\3.11\MSM.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.11\ETHERTSM.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.11\MONITOR.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.11\LSLENH.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.11\PATCHMAN.NLM F:\SYSTEM 6. Edit AUTOEXEC.NCF to contain loading and binding of the network driver, e.g. LOAD LSLENH LOAD ETHIIE INT=5 PORT=300 BIND IPX TO ETHIIE NET=xx See file ETHIIE.NCF for more about the parameters of the driver and examples of ETHIIE load syntax. 2.4.2 NetWare 3.12 or NetWare 4.x Installing NetWare 3.12 or 4.x Server may take place using the INSTALL utility. Specify the path A:\NETWARE\386SRV for the OEM Driver Diskette. 2.5 Novell NetWare NT Client The drivers for EtherTeam16 NT Client can be found from the subdirectory NETWARE\NT have the following file names: ETHIIE.LAN ODI Driver (Specification 3.1). OEMSETUP.INF OEM Setup File ETHIIE.HLP OEM Setup Help File To install the NetWare NT Client for ICL EtherTeam16, do the following: 1. Use the Windows NT Control Panel to install the driver. Give the path A:\NETWARE\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 must be defined explicitly in case several adapters are installed. 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. 2.6 NetWare IPX 2.X Server Driver The drivers can be found from the subdirectory NETWARE\286SRV\ and have the following file names: AETHIIE.OBJ Server LAN A-Driver BETHIIE.OBJ Server LAN B-Driver CETHIIE.OBJ Server LAN C-Driver DETHIIE.OBJ Server LAN D-Driver AETHIIE.LAN LAN Driver Description To install the 2.x IPX Server Driver for ICL EtherTeam16, do the following: 1. Installation of the driver(s) can take place either from a diskette or from a hard disk. For the diskette method, format an empty diskette with label LAN_DRV_487 (LAN_DRV_487 is the diskette label for ICL EtherTeam16 Driver Diskette for NetWare). Or for the disk method, create a subdirectory LAN_DRV_.487 to the NETWARE directory on your hard disk. 2. Copy the files AETHIIE.OBJ, BETHIIE.OBJ, CETHIIE.OBJ, DETHIIE.OBJ and AETHIIE.LAN from the Driver Diskette from subdirectory 286SRV either to the root of the LAN_DRV_487 diskette or to the NETWARE\LAN_DRV_.487 directory on your hard disk (depending on the selected method), e.g. COPY A:\NETWARE\286SRV\?ETHIIE.OBJ C:\NETWARE\LAN_DRV_.487 COPY A:\NETWARE\286SRV\AETHIIE.LAN C:\NETWARE\LAN_DRV_.487 3. Use Novell installation utilies to build up the program (use INSTALL to generate the Server or ROUTEGEN to generate the External Router). 3 NDIS 3.0 ENHANCED MODE WINDOWS DRIVER FOR ICL ETHERTEAM16 3.1 Current Status of the Driver 3.2 Installation of the Driver The Enhanced Mode Windows drivers for EtherTeam16 can be found from the subdirectory NDIS3\WIN have the following file names: ETHIIE.386 Enhanced Mode Windows Driver OEMSETUP.INF OEM Setup File To install the Enhanced Mode Windows Driver for ICL EtherTeam16, do the following: 1. Use the Windows Setup to install the driver. Give the path A:\NDIS3\WIN 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 Transceiver. The transceiver must be given explicitly (BNC, TP or AUI). There is no AUTO mode implemented to detect automatically the network connection. 3. Select the I/O Base Address according to the jumpering of your adapter. 3.3 Advanced Installation Features There are some keywords detected by the driver which can be accessed from the Advanced menu. NOTE! These are for special purposes only, and are not required in normal installation. 1. NetworkAddress Specifies the Network Address when the permanent Network Address is not used. Must be given as a string of exactly 12 character, enclosed with quotation marks. Possible values : "00004B112233" (for example). Default : Permanent Network Address 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. 5 FTP PACKET DRIVER FOR ICL ETHERTEAM16 5.1 Installation of the Driver To install the FTP Packet Driver, start it with the following command line syntax : ethiie [options] [hardware_irq] [ []]] The EtherTeam16 requires the following optional parameters (the defaults apply if no parameter is given). 1. hardware_irq The HW Interrupt Number, any valid IRQ used by the adapter. The default value is 9(2). 2. io_addr The base I/O address, any valid address (must match with the jumpering on the board). The default value is 0x300. 3. net_port Network connection (Transceiver), either (0 = BNC or TP, 1 = AUI(DIX). The default value is BNC (or TP). 6 DIAGNOSTICS The EtherTeam16 diagnostics included in the installation disk is a subset of the ICL Advanced Diagnostics (ADP). Running ADP Diagnostics requires DOS, so you must create a DOS system (with the ADP) to run the diagnostics. 6.1 Installing the ADP to the Hard Disk The most convenient (and fastest) method to run the ADP is from your hard disk. In order to do this: 1. Make a subdirectory \ADP to the root of your hard disk. 2. Copy the files from the subdirectory \ADP from the driver diskette to the subdirectory \ADP in your hard disk. 3. Make sure that the ANSI.SYS is defined in your CONFIG.SYS (ADP needs ANSI.SYS for its screen handling). 4. You can now run the diagnostics from your hard disk as described later in this section. 6.2 Installing the ADP to the ADP Diskette Another possibility is to create a DOS system diskette and to copy the ADP files from the driver diskette to it. If there is not enough space on the target diskette for both ADP and DOS, only a subset of DOS files is required. NOTE! The instructions below apply for both DOS5 and DOS6. For other DOS versions the DOS file names, CONFIG.SYS and AUTOEXEC.BAT must be changed accordingly. 1. Make an "empty" DOS System Diskette, with command "SYS A:". 2. Copy the necessary DOS files to a subdirectory \DOS on the target ADP diskette. The file DOS.DIR in the subdirectory \ADP\MAKEADP.DSK of the driver diskette lists the minimum set of DOS files needed. There is also a BAT file MAKEADP.BAT in the same subdirectory on the driver diskette which takes care of the copying. 3. Make a subdirectory \ADP on the target ADP diskette. 4. Copy the files from the subdirectory \ADP on the driver diskette to the subdirectory \ADP on the target ADP diskette. 5. Copy the files CONFIG.SYS and AUTOEXEC.BAT from the \ADP\MAKEADP.DSK subdirectory on the driver diskette to the root of the target ADP diskette. 6. The ADP diskette has now been builded and you can run the diagnostics as described later in this section. NOTE! Never use the original Driver Diskette in running the diagnostics. ADP may want to write a log file to the diskette (Write Protected must be off). You may cause damage to your driver diskette! 6.3 Running the Diagnostics Testing the transmit and receive circuitries requires that either a loopback plug is used, or the board is connected to the network. If the loopback is not possible (available only for Thin Ethernet and Twisted Pair Ethetnet), perfect testing should be done by setting another board in the network as an Echo Server. WARNING! It is recommended to run the diagnostics only in networks where there is no other activity. If the EtherTeam16 board in test is connected to the network, ensure that other network activity is stopped. The test definition is done by the "Options" field asked by ADP when the test has been started. However, the basic test configurations are covered by a set of predefined script files. To run the diagnostics, boot the ADP diskette from the drive A: (or change to the \ADP subdirectory if you run ADP from your hard disk). When in DOS prompt state, start ADP by keying "DIAG" and its option. The following predefined tests are available: DIAG BOARD Test the Ethernet Adapter using only the internal loopbacks, excluding the Network connection (no Test Plug or Network connection required). DIAG BNC Test the Thin Ethernet interface (With Thin EtherNet Test Plug, or Network connected). DIAG DIX Test the Thick Ethernet interface (No Test Plug available, the Network must be connected). DIAG TP Test the Twisted Pair Ethernet interface (No Test Plug available, the Network must be connected. If no TP connection is available, use BOARD option instead). DIAG ECHO Sets an EtherTeam16 board as an Echo Server. No extra parameters are needed for Thin or Twisted Pair Ethernet. If the Thick Ethernet interface is used, add /DIX option when the ADP later asks for test options. DIAG XMIT Tests the EtherTeam16 board by transferring data to/from an Echo Server (which must have been started as described in DIAG ECHO!). No extra parameters are needed for Thin or Twisted Pair Ethernet. If the Thick Ethernet interface is used, add /DIX option when the ADP later asks for test options. As a default, the ADP writes no log file (the ADP Diagnostics diskette may be left Write Protected). If you want to enable logging of test results, use DEFINE LOG of ADP to enable it (see later). After start, follow the ADP instructions and helps appearing on the screen. The actions needed are as: * Press F1 to confirm the system configuration. The installed EtherTeam16 card should appear in the list of adapter cards. If not, check the jumpering in order that it is not conflicting with other cards. * Press F1 to start running the diagnostics. After that, if you still want to change logging of test results, press F4 to DEFINE LOG. There press twice ENTER to proceed to the Logging Level field. Set it as 0 or 2, depending if logging will be disabled or enabled, respectively. Alternatively the definition can be done by pressing F1 (ERRORS ONLY) or F4 (DISABLE LOGGING). * Press F1 to start running a diagnostics program. The ADP now enters into prompt waiting for the test number, test options and test loops. Usually the default values apply, so just press ENTER to proceed to the next field. With "arrow up"-key you can go back to the previous field. * Sometimes you must change the test options. For example, to select the Thick Ethernet interface, just add /DIX to the option field and press ENTER. * After selecting the test loops, the diagnostics starts immediately. The proceeding and the results of the test are output on the screen. They are also written to a log file (ADP.LOG), provided that the logging was enabled (see above). If no errors were found during the test, the final message appearing on the screen is: "EtherTeam16 Adapter Ok" If any errors were found during the test, the error message is output on the screen and the final message appearing on the screen is: "EtherTeam16 Adapter Fault"