****************************************************************** * ICL EtherTeam 16i LAN Driver Installation Guide * ****************************************************************** CONTENT 1 NDIS DRIVERS FOR ICL ETHERTEAM16I 2 NETWARE DRIVERS FOR ICL ETHERTEAM16I 2.1 DOS ODI Workstation Driver 2.1.1 NetWare 3.1x 2.1.2 NetWare 4.x 2.2 OS/2 ODI Workstation Driver 2.3 NetWare 386 ODI Server Driver 2.3.1 NetWare 3.1x 2.3.2 NetWare 4.x 2.4 NetWare IPX 2.X Server Driver 2.5 Remote Program Load 2.6 Netware NT Client 3 SCO UNIX LLI driver for SCO UNIX 3.2v4.x 3.1 SCO UNIX Driver Files 3.2 Installing The SCO UNIX Driver 3.3 Configuring The SCO UNIX Driver 4 ETHERTEAM16I IEEE 802.1E PROM 5 NT DRIVER FOR ICL ETHERTEAM16I 5.1 Installation of the Driver 5.2 Advanced Installation Features 5.3 Driver Error Codes 6 NDIS 3.0 ENHANCED MODE WINDOWS DRIVER FOR ICL ETHERTEAM16I 6.1 Installation of the Driver 6.2 Advanced Installation Features 7 FTP PACKET DRIVER FOR ICL ETHERTEAM16I 7.1 Installation of the Driver 8. MS LAN Manager 2.1A Remoteboot Server Installation 8.1 Introduction 8.1.1 Installation guidelines 8.2 MS LAN Manager server installation 8.3 RPLSETUP 8.4 Operating system files copying 8.4.1 MS-DOS 5.00 8.4.2 MS OS/2 1.3 8.5 RPLINST 8.6 EtherTeam 16i Driver Adaptation 8.6.1 EtherTeam 16i DOS driver 8.6.2 EtherTeam 16i OS/2 driver 9. Diagnostic Program. This installation disk contains the ICL EtherTeam 16i NDIS Drivers for LAN Manager, Novell NetWare Drivers, SCO UNIX LLI drivers for SCO UNIX 3.2v4.x, eth16i.nif file for IBM LAN Server installation, Configuration Utility, Network Monitor, Windows NT driver, FTP Packet driver and the Diagnostics program. Certification situation at 13.5.1993: - The NetWare Drivers are Novell certified. - The NDIS Drivers are Microsoft certified. NOTE: EtherTeam 16i uses IRQ 10 and IO 2A0-2BF as default IRQ and IO address. WAN_AT uses the same IRQ 10 as default. If you use WAN_AT in the same PC with EtherTeam 16i you must change the IRQ. We can recommend IRQ 15. --------------------------------------------------------------------------- ** 1. NDIS DRIVERS FOR ICL ETHERTEAM16I ** The NDIS drivers for EtherTeam16i can be found from the subdirectories MSLANMAN.DOS\DRIVERS\ETHERNET\ETH16I and MSLANMAN.OS2\DRIVERS\ETHERNET\ETH16I have the following file names: ETH16I.DOS DOS Driver ETH16I.OS2 OS2 Driver PROTOCOL.INI Template OEMSETUP.INF OEM Setup File To install the NDIS drivers (NDIS2) , just use the normal Lan Manager 2.x or Windows for Workgroups installation programs. NOTE: The OEMSETUP.INF file of Windows for Workgroups 3.1 is now stored in the subdirectory A:\WFW310 (to avoid conflict with the OEMSETUP.INF file of Windows for Workgroups 3.11). You MUST give this path when installing the adapter in this environments. NOTE: There is a new keyword "PROCESSOR = 286" to be used when (and only when) the OS/2 Driver is run in 286 CPU environments. ---------------------------------------------------------------------------- ** 2. NETWARE DRIVERS FOR ICL ETHERTEAM16I ** These are short installation instructions for EtherTeam16i NetWare Drivers. For more detailed information, see the proper Novell documentation. NOTE! The Dedicated DOS IPX Workstation Driver has not been developed for EtherTeam16i. The DOS IPX driver is being phased out by Novell, and the DOS ODI Driver is expected to be used in its place in all cases. Novell Labs discontinued the certification of the DOS IPX Drivers in June 1992. * 2.1. DOS ODI Workstation Driver * The drivers can be found from the subdirectory NETWARE\DOSODI and have the following file names: ETH16I.COM Workstation Driver ETH16I.CFG Configuration Example ETH16I.INS Installation Information File. * 2.1.1. NetWare 3.1x * To install the DOS ODI Workstation Driver for ICL EtherTeam16i, do the following: 1. Copy the files ETH16I.COM and ETH16I.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\ETH16I.COM C:\NETWARE\DOSODI COPY A:\NETWARE\DOSODI\ETH16I.CFG C:\NETWARE\DOSODI 2. Make modifications to the driver options in ETH16I.CFG (if needed), and rename ETH16I.CFG as NET.CFG. NOTE! The default frame type of the DOS ODI Driver has now been changed to be 802.2. Some current networks may still use 802.3, so the frame type 802.3 must be given in 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\ETH16I.COM C:\NETWARE\DOSODI\IPXODI.COM C:\NETWARE\DOSODI\NETX.COM * 2.1.2. NetWare 4.x * Installing DOS Workstation may take place using the INSTALL utility. It must be noted that it can't load the drivers from the path on the EtherTeam16i driver diskette, but supposes them to be loaded from a subdirectory \DOS from the root. To support this, it is recommended that you copy the files ETH16I.COM and ETH16I.INS from the EtherTeam16i driver diskette to the NetWare installation diskette containing the other drivers, to its \DOS subdirectory. * 2.2. OS/2 ODI Workstation Driver * The drivers can be found from the subdirectory NETWARE\OS2ODI and have the following file names: ETH16I.SYS Workstation Driver ETH16I.CFG Configuration Example To install the OS/2 ODI Workstation Driver for ICL EtherTeam16i, 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 EtherTeam16i). 2. Copy the files ETH16I.SYS and ETH16I.CFG from the Driver Diskette from subdirectory OS2ODI to the NETWARE directory on your hard disk, e.g. COPY A:\NETWARE\OS2ODI\ETH16I.SYS C:\NETWARE COPY A:\NETWARE\OS2ODI\ETH16I.CFG C:\NETWARE 3. Edit the CONFIG.SYS created by the INSTALL utility, replacing the installed driver definition by EtherTeam16i, e.g. rem DEVICE=C:\NETWARE\NE2000.SYS DEVICE=C:\NETWARE\ETH16I.SYS 4. Make modifications to the driver options in ETH16I.CFG (if needed), and rename ETH16I.CFG as NET.CFG. Ensure that NET.CFG is found on the search path (or from the root directory). * 2.3. NetWare 386 ODI Server Driver * The drivers can be found from the subdirectory NETWARE\386SRV and have the following file names: ETH16I.LAN Server Driver ETH16I.NCF Load Example ETH16I.LDI Installation Information File. The other drivers, required in 3.1x installation only, can be found from the subdirectory NETWARE\386SRV\3.1x and have the following file names: MSM.NLM Media Support Module ETHERTSM.NLM Topology Specific Module MONITOR.NLM Monitor NOTE! The NetWare ODI Server Driver is implemented according to specification version 3.0, and requires MSM.NLM and ETHERTSM.NLM in order to work. * 2.3.1. NetWare 3.1x * To install the 3.1X ODI Server Driver for ICL EtherTeam16i, do the following: 1. Copy the file ETH16I.LAN from the Driver Diskette from subdirectory 386SRV 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\ETH16I.LAN C:\NETWARE 2. Copy the other needed files from the Driver Diskette from subdirectory 386SRV\3.1x 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.1x\MSM.NLM C:\NETWARE COPY A:\NETWARE\386SRV\\3.1xETHERTSM.NLM C:\NETWARE NOTE! If you have more recent versions of these files, use them instead of those on EtherTeam16i driver diskette. 3. Load the LAN Driver (The ETH16I.LAN loads MSM and ETHERTSM modules implicitly), and bind the Network Driver, e.g. LOAD C:ETH16I INT=A PORT=2A0 BIND IPX TO ETH16I NET=xx 4. Establish a connection from a Workstation to the Server and copy the files to the SYSTEM directory on the Server, e.g COPY A:\NETWARE\386SRV\ETH16I.LAN F:\SYSTEM COPY A:\NETWARE\386SRV\3.1x\MSM.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.1x\ETHERTSM.NLM F:\SYSTEM COPY A:\NETWARE\386SRV\3.1x\MONITOR.NLM F:\SYSTEM NOTE! Copy these last 3 files only if you don't have more recent versions of them included in your system. 5. Edit AUTOEXEC.NCF to contain loading and binding of the network driver, e.g. LOAD ETH16I INT=A PORT=2A0 BIND IPX TO ETH16I NET=xx See file ETH16I.NCF for more about the parameters of the driver and examples of ETH16I load syntax. NOTE! In order to monitor properly the EtherTeam16i Driver, a new version of the MONITOR.NLM is required. * 2.3.2. NetWare 4.x * Installing NetWare 4.x Server may take place using the INSTALL utility. As a default, it supposes the drivers to be loaded from NetWare installation diskette containing the LAN Drives, or from the root of a user supplied diskette. To support this, it is recommended that you copy the files ETH16I.LAN and ETH16I.LDI from the EtherTeam16i driver diskette to the NetWare installation diskette containing the other LAN drivers, to its root. Alternatively, you can load the drivers from the EtherTeam16i Driver Diskette by giving the path to the proper subdirectory on it. It may be that the installation in this case tries to load the ETHERTSM.NLM and MSM.NLM from the diskette but you can disregard the possible error messages concerning this. WARNING! The MSM.NLM, ETHERTSM.NLM and MONITOR.NLM on the 3.1x subdirectory are for 3.1x installation only. Never use them in 4.x installation. * 2.4. NetWare IPX 2.X Server Driver * The drivers can be found from the subdirectory NETWARE\286SRV\ and have the following file names: AETH16I.OBJ Server LAN A-Driver BETH16I.OBJ Server LAN B-Driver CETH16I.OBJ Server LAN C-Driver DETH16I.OBJ Server LAN D-Driver AETH16I.LAN LAN Driver Description NOTE! EtherTeam16i cannot be used in 2.x Server for Remote Boot. The new Novell Remote Boot is implemented using RPL Protocol, which in turn requires that the driver must support Apple Talk II. This is not a standard feature, and is not implemented in the current version of EtherTeam16i 2.x Server Driver. To install the 2.x IPX Server Driver for ICL EtherTeam16i, 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_535 (LAN_DRV_535 is the diskette label for ICL EtherTeam16i Driver Diskette for NetWare). Or for the disk method, create a subdirectory LAN_DRV_.535 to the NETWARE directory on your hard disk. 2. Copy the files AETH16I.OBJ, BETH16I.OBJ, CETH16I.OBJ, DETH16I.OBJ and AETH16I.LAN from the Driver Diskette from subdirectory 286SRV either to the root of the LAN_DRV_535 diskette or to the NETWARE\LAN_DRV_.535 directory on your hard disk (depending on the selected method), e.g. COPY A:\NETWARE\286SRV\?ETH16I.OBJ C:\NETWARE\LAN_DRV_.535 COPY A:\NETWARE\286SRV\AETH16I.LAN C:\NETWARE\LAN_DRV_.535 3. Use Novell installation utilies to build up the program (use INSTALL to generate the Server or ROUTEGEN to generate the External Router). The 2.x IPX Server Driver for ICL EtherTeam16i supports DCONFIG, ECONFIG, ROUTEGEN and JUMPERS utilities. In the driver there are defined 4 fixed configurations, 1 AUTO configuration and JUMPERS configuration(s). When selevting configurations, the following mus be noted: 1. If only a single EtherTeam16i Adapter will be installed in the system, the AUTO configuration can be selected (recommended). In this case the driver detects its I/O-Base Address and IRQ number. 2. If several EtherTeam16i Adapters will be installed in the system (e.g. Internal or External Router), then the AUTO Configuration cannot be used. Instead of it, any of the Fixed or JUMPER confifurations must be used. 3. The SETUP value in the Network Connection (Con = SETUP) means that the driver uses the default value from the Adapter EEPROM in selecting the Connection. * 2.5 Remote Program Load * The Novell provided drivers needed for Remote Program Load in NetWare 3.x can be found from the subdirectory NETWARE\RPL and have the following file names: RPL.NLM RPL Protocol Stack RBOOT.RPL Boot Strap Program To install the Remote Program Load (RPL) for NetWare 3.x Server, do the following: 1. Be sure that the RPL.NLM and RBOOT.RPL can be found from the Server in SYS:\SYSTEM and SYS:\LOGIN, respectively. If not, copy them from the Driver Diskette from subdirectory RPL. COPY A:\NETWARE\RPL\RPL.NLM SYS:\SYSTEM COPY A:\NETWARE\RPL\RBOOT.RPL SYS:\LOGIN 2. Load and bind RPL Protocol on the Server (keep in mind that RPL uses frame type 802.2), for example: load eth16i frame=Ethernet_802.2 name=RPL_3.11 load rpl bind rpl to RPL_3.11 3. To complete the setup of remote program load, follow instructions given in Novell NetWare 3.11 "Installation" documentation. ---------------------------------------------------------------------------- * 2.6 NetWare NT Client * The drivers for EtherTeam16i NT Client can be found from the subdirectory NETWARE\NT have the following file names: ETH16I.LAN ODI Driver (Specification 3.1). OEMSETUP.INF OEM Setup File ETH16I.HLP OEM Setup Help File To install the NetWare NT Client for ICL EtherTeam16i, do the following: 1. If needed, use the EtherTeam16i Configuration Utility to check that the I/O Base Addresses and IRQ Numbers of the adapters to be installed do not conflict with any other adapter(s). 2. 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 I/O Base Address according to the EEPROM Setup value of your adapter. The default AUTO means that the adapter is searched from the possible I/O Base Addresses. NOTE! In case of several adapters installed, the I/O Base Addresses must be given explicitly. 2. Select the Interrupt Number according to the EEPROM Setup value of your adapter. The default AUTO means that the Interrupt Number from the Setup EEPROM is used. NOTE! If the Interrupt Number is given explicitly, it can't override the Setup value on the EEPROM but must match with it. 3. Select the Transceiver. The value SETUP here means that the transceiver definition from the Setup EEPROM is used (Its factory setting is AUTO). If the transceiver is given explicitly (BNC, TP or AUI), then it is used. Otherwise (AUTO) the driver detects automatically the network connection (provided that the cable is connected while booting the system). ** 3 SCO UNIX LLI driver for SCO UNIX 3.2v4.x ** * 3.1 SCO UNIX Driver Files * The EtherTeam 16i Driver Software Diskette is supplied in DOS format. Under SCO_UNIX subdirectory there is an image of the file which constitute a SCO UNIX driver custom installable disk. To extract the file to produce a custom installable disk proceed as follows: 1. Take the the EtherTeam 16i Driver Software Diskette to a SCO UNIX system and use "doscp" to copy the file under SCO_UNIX subdirectory onto the SCO UNIX system - suggest you use the /tmp directory e.g. doscp -r /dev/fd0:/SCO_UNIX/IIE.ML /tmp/iie.ml 2. Insert a new, SCO UNIX formatted diskette and use "dd" to re-create the custom installable disk e.g. format /dev/rfd0 cd /tmp uudecode iie.ml uncompress iie.Z dd if=/tmp/iie of=/dev/rfd0 bs=18b You now have the "custom" installable diskette containing the SCO UNIX LLI driver and support files for the netconfig configuration utility. * 3.2 Installing The SCO UNIX Driver * NOTE! Before you install the SCO UNIX LLI Driver for the EtherTeam 16i board, make sure that you have installed the SCO TCP/IP and SCO LLI Drivers packages. The SCO LLI Drivers package is supplied on a separate disk with the SCO TCP/IP network package. - Boot the system in system maintenance mode. - Type custom and select the "Install" option. Press RETURN. - Select the option called "A New Product". Press RETURN. - Select the option called "Entire Product" to install all the necessary software. Press RETURN. - Follow the prompts presented to insert the SCO UNIX driver disk and install the software. - The system will process and install the files. At the end of the installation, quit out of the custom utility. * 3.3 Configuring The SCO UNIX Driver * The SCO UNIX LLI driver for the EtherTeam 16i board is configured using the netconfig utility in system maintenance mode. The netconfig configuration utility is used to configure all of the SCO products that currently use the LLI diskette. You are advised to consult your SCO TCP/IP manuals for additional advise on configuring network drivers using netconfig. The EtherTeam 16i driver for SCO UNIX LLI is known as iie (for ICL EtherTeam 16i). The first iie board is referred to as iie0. You may install and configure up to four EtherTeam 16i boards into your system. If you install more than one iie board into your system, the boards are numbered sequentially starting with 0. Thus iie0, iie1, iie2 and iie3 would refer to the first, second, third and fourth EtherTeam 16i boards respectively, installed and configured into the system. When you use netconfig you build chains that link application software (e.g. NFS) to transport software (e.g. TCP/IP) and network drivers (e.g. EtherTeam 16i- iie). A chain is a simplified way of looking at how different networking software programs and hardware interact. The networking software will not work until the appropriate chains have been created. For example, configuring NFS over TCP/IP over an EtherTeam 16i (iie) driver, would create the following chains: sco_tcp->iie0 nfs->sco_tcp As an example of the configuration process, the configuration of SCO TCP/IP over an EtherTeam 16i driver would proceed as follows: - Type netconfig to invoke the network configuration utility. - Select "Add a new chain". - Select "sco_tcp". A list of available drivers appears. Each driver corresponds to a particular networking board or SLIP or PPP line. - Select "iie0" to select the first EtherTeam 16i board and confirm the chain by entering y at the confirmation prompt. You now begin the actual configuration process for both the EtherTeam 16i driver and SCO TCP/IP. - For the EtherTeam 16i (iie) driver the following information is requested: Enter IRQ (2 5 10 15) [10] or 'q' to quit: Either press RETURN to accept the default IRQ of 10 or type the required IRQ value from the list. - The system will then prompt you with: Enter I/O base address (240 260 280 2A0 300 340 380) [2A0] or 'q' to quit: Either press RETURN to accept the default I/O base address of 2A0 or type the required I/O base address from the list. The configuration process will now continue for SCO TCP/IP which will require you to answer a series of questions. - TCP/IP will request you to enter the following information: Internet address - an address that uniquely identifies your system on the network. In the case of a system with multiple networking boards, each driver must have its own Internet address. An example of a Class B Internet address would be: 132.147.160.1 Netmask - a value that masks the Internet portion of your Internet address, leaving only the host portion. The default for Class B would be: 255.255.0.0 Broadcast address - an address that SCO TCP/IP uses to broadcast packets to the entire network, rather than to a specific destination. You will also be asked if the Broadcast address uses all 1's. If this is accepted, the example for the Class B Broadcast address would be: 132.147.255.255 Gateway status - whether your system serves as a gateway between two networks; only valid in the case of a multiple board system Number of pseudo ttys - the number of pseudo ttys allocated to network programs, such as telnet or rlogin. - After entering the above information the configuration will is complete and you will be presented with the original netconfig prompt. You should complete all the configuration for the chains required and then quit from the netconfig utility. You will be prompted to rebuild the kernel to implement the network configuration, which you should do unless you have other software/driver packages to install. You may initiate the kernel build process at a later date by changing into the directory /etc/conf/cf.d and typing ./link_unix. When you rebuild the kernel you should also allow the kernel environment to be rebuilt and make the new kernel boot by default. After the kernel has been rebuilt you should shutdown the system and reboot using the new kernel. -------------------------------------------------------------------------- ** 4 ETHERTEAM16I IEEE 802.1E PROM ** * 4.1 Updating BOOTDD.SYS * The boot diskette image which the IEEE802.1E PROM downloads into the workstation must include the BOOTDD.SYS driver. The version delivered with the server Remote System Load software may be too old to be compatible with the EtherTeam 16i adapter: BOOTDD v1.4 or later must be used when creating boot images for EtherTeam 16i workstations. An up-to-date version of BOOTDD.SYS can be found on the EtherTeam 16i LAN Support Software Diskette ver 1.2 or later in the directory RSL-802.1E. -------------------------------------------------------------------------- ** 5 NT DRIVER FOR ICL ETHERTEAM16I ** * 5.1 Installation of the Driver * The NT drivers for EtherTeam16i can be found from the subdirectory NDIS3\NT have the following file names: ETH16I.SYS NT Driver OEMSETUP.INF OEM Setup File ETH16I.HLP OEM Setup Help File NOTE: When installing Windows NT with EtherTeam16i, do not use the "Detect Network Adapter" option. It is prefrable to select the EtherTeam16i adapter manually. To install the NT Driver for ICL EtherTeam16i, do the following: 1. If needed, use the EtherTeam16i Configuration Utility to check that the I/O Base Addresses and IRQ Numbers of the adapters to be installed do not conflict with any other adapter(s). 2. Use the Windows NT Control Panel to install the driver. Give the path A:\NDIS3\NT when prompted for the OEM Driver diskette. NOTE! The OEMSETUP.INF (OEMSETNT.INF) can be found also from the OEM Driver Disk root, but in case of "Update" you MUST give the whole path name. 1. Select the I/O Base Address according to the EEPROM Setup value of your adapter. The default 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: 0240, 0260, 0280, 02A0, 0300, 0340, 0380 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. 2. Select the Interrupt Number according to the EEPROM Setup value of your adapter. The default AUTO means that the Interrupt Number from the Setup EEPROM is used. NOTE! If the Interrupt Number is given explicitly, it can't override the Setup value on the EEPROM but must match with it. 3. Select the Transceiver. The value SETUP here means that the transceiver definition from the Setup EEPROM is used (Its factory setting is AUTO). If the transceiver is given explicitly (BNC, TP or AUI), then it is used. Otherwise (AUTO) the driver detects automatically the network connection (provided that the cable is connected while booting the system). * 5.2 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. In fact the StagedReceive (see below) is the only one which may be needed in some situations. To define these parameters, start REGEDT32 from APPLICATIONS and then select the parameters of EtherTeam16i Driver by selecting the driver parameters from the menu as follows: HKEY_LOCAL_MACHINE on Local Machine SYSTEM CurrentControlSet Services ETH16I01 Parameters If more adapters are installed, then you must select the parameters of the adapter instance concerned, for example of ETH16I02. 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. TransmitBufferSize Specifies the amount of Adapter Buffer Memory (as kbytes) reserved for transmit packets. Possible values : 4, 8 or 16 Default : 8 This may be used to define 16k of transmit buffer size in cases where the adapter is supposed to do a lot of transmissions compared to receives. Still it is unclear if any significant improvement in performance can be achieved. 2. 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. 3. MultiProcessor May be used to tell the driver that it can suppose to be running in SingleProcessor environments. When accessing this, the first adapter instance (ETH16I01) must be selected. The definition is then applied to all other adapter instances, if any. Possible values : Yes (MultiProcessor) or No (SingleProcessor) Default : Yes (Multiprocessor) The NT driver has been written to work properly in MultiProcessor environments, which causes a little more overhead to it. This overhead may be decreased by the Singleprocessor definition. However it is unclear if any significant improvement in performance can be achieved. NOTE! Must be used with care, because using SingleProcessor mode in Multiprocessor enviroments causes fatal error conditions. 4. StagedReceive Specifies the default receive stage buffering when multiple protocols are bound. Possible values : No (NonStaged) or Yes (Staged) Default : No (NonStaged) NDIS3 specification requires that the MAC driver must be prepared to copy the packet more than once per receive event. Thus, adapters (like EtherTeam16i) which do not support reading the packet from the adapter several times, must copy the packet into a temporary staging buffer when multiple protocols are bound. Because of performance, EtherTeam16i NT Driver attempts to avoid this staging, and switches to the staged mode only if necessary. The following is a description of how the driver selects the actual receive mode (if there is only one binding, the driver always uses non-staged mode): 1. When a binding is opened, the driver initially selects the staged mode. It also sets a certain threshold value for the number of first packet reads. The purpose of this value is to give the driver time to detect whether it is "safe" to start using non-staged mode. 2. If two bindings attempt to copy the same packet during these first packet reads, the driver stays in the staged mode, otherwise it switches to the non-staged mode. 3. If two bindings attempt to copy the same packet when the driver is in the non-staged mode, the driver encounters an error. The packet cannot be copied another time and the binding is informed about this with an error code (the error info is also written to the log). The driver then switches back to the staged mode, and all the following packets are then received in the staged mode. 4. The driver stays in the selected mode until the binding condition is changed. If the binding which caused the staged mode is closed, or there is only one binding left, the non-staged mode can again be used. The method described above is supposed to work reliably, provided that the protocols can recover reasonably from loosing a single packet just before switching to the staged mode. But if any problems are supposed to be due to loosing the packet, the driver can be set to the staged mode as default (but at the cost of performance). The need for selecting permanently the staged mode can be checked from the Event Log (see section 5.4 "Driver Error Codes", Error Code 0016). * 5.3 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. Eth16i0N) 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. The first 3 of these errors are detected during driver initialisation only , but the last 3 even runtime. There is a limitation for the number of how many times the runtime errors are logged. 1. Eth16i0N : 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 20h!). 2. Eth16i0N : Has determined that the driver is not functioning properly. The driver could not be properly started. Probable reasons for this message are: EEPROM checksum error, IRQ conflict, Network not connected (when the Transceiver was AUTO), or the EtherCoupler could not be started. The binary error code in the Event Log is: 0012 = EEPROM Checksum Error 0013 = IRQ Conflicting With Setup 0014 = Network Not Connected. 0015 = EtherCoupler Not Started. Check the EEPROM Setups, possible I/O-Base Address and IRQ Number conflicts, and that the network is properly connected. 3. Eth16i0N : 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. Eth16i0N : 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. 5. Eth16i0N : Has encountered an internal error and has failed. The probable reason for this message is that the driver was in the non- staged receive mode and was forced to change to the staged mode, loosing however one packet. The binary error code in the Event Log is: 0016 = Non-Staged Receive Error If the protocol cannot handle this type of error properly, set the driver permanently to the staged mode (see section 5.3, "Staged Receive"). 6. Eth16i0N : 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. --------------------------------------------------------------------------- ** 6 NDIS 3.0 ENHANCED MODE WINDOWS DRIVER FOR ICL ETHERTEAM16I ** * 6.1 Installation of the Driver * The Enhanced Mode Windows drivers for EtherTeam16i can be found from the subdirectory NDIS3\WIN have the following file names: ETH16I.386 Enhanced Mode Windows Driver OEMSETUP.INF OEM Setup File To install the Enhanced Mode Windows Driver for ICL EtherTeam16i, do the following: 1. If needed, use the EtherTeam16i Configuration Utility to check that the I/O Base Addresses and IRQ Numbers of the adapters to be installed do not conflict with any other adapter(s). 2. Use the Windows Setup to install the driver. Give the path A:\NDIS3\WIN when prompted for the OEM Driver diskette. NOTE! The OEMSETUP.INF can be found also from the OEM Driver Disk root. NOTE! The I/O Base Address, Transceiver and IRQ Number are commented in the OEMSETUP.INF file, corresponding them to be left as AUTO. If the explicit definitions are wanted to appear in the Setup, remove the comment signs from these lines. 1. Select the I/O Base Address according to the EEPROM Setup value 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: 0240, 0260, 0280, 02A0, 0300, 0340, 0380 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. 2. Select the Transceiver. If the transceiver is given explicitly (BNC, TP or AUI), then it is used. Otherwise (AUTO) the driver detects automatically the network connection (provided that the cable is connected while booting the system). * 6.2 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. In fact the StagedReceive (see below) is the only one which may be needed in some situations. 1. TransmitBufferSize Specifies the amount of Adapter Buffer Memory (as kbytes) reserved for transmit packets. Possible values : 4, 8 or 16 Default : 8 This may be used to define 16k of transmit buffer size in cases where the adapter is supposed to do a lot of transmissions compared to receives. Still it is unclear if any improvement in performance can be achieved. 2. StagedReceive Specifies the receive stage buffering when multiple protocols are bound. Possible values : No (Nonstaged) or Yes (Staged) Default : No (NonStaged) NDIS3 specification requires that the MAC driver must be prepared to copy the packet more than once per receive event. Thus, adapters (like EtherTeam16i) which do not support reading the packet from the adapter several times, must copy the packet into a temporary staging buffer when multiple protocols are bound. Because of performance, EtherTeam16i NT Driver attempts to avoid this staging, and switches to the staged mode only if necessary. The following is a description of how the driver selects the actual receive mode (if there is only one binding, the driver always uses non-staged mode): 1. When a binding is opened, the driver initially selects the staged mode. It also sets a certain threshold value for the number of first packet reads. The purpose of this value is to give the driver time to detect whether it is "safe" to start using non-staged mode. 2. If two bindings attempt to copy the same packet during these first packet reads, the driver stays in the staged mode otherwise it switches to the non-staged mode. 3. If two bindings attempt to copy the same packet when the driver is in the non-staged mode, the driver encounters an error. The packet cannot be copied another time and the binding is informed about this with an error code (the error info is also written to the log). The driver then switches back to the staged mode, and all the following packets are then received in the staged mode. 4. The driver stays in the selected mode until the binding condition is changed. If the binding which caused the staged mode is closed, or there is only one bindind left, the non-staged mode can again be used. The method described above is supposed to work reliably, provided that the protocols can recover reasonably from loosing a single packet just before switching to the staged mode. But if any problems are supposed to be due to loosing the packet, the driver can be set to the staged mode as default (but at the cost of performance). --------------------------------------------------------------------------- ** 7 FTP PACKET DRIVER FOR ICL ETHERTEAM16I ** * 7.1. Installation of the Driver To install the FTP Packet Driver, start it with the following command line syntax : eth16i [options] [ []] The EtherTeam16i requires no additional parameters (the defaults are fetched from the SETUP EEPROM), but optionally the following can be defined: 1. io_addr The base I/O address, either any valid address (must match with the Setup), or 0xFFFF corresponding to search mode (AUTO). In systems where only one EtherTeam16i is installed, it is not necesssary to specify the I/O Base Address, but the driver searches it automatically. 2. net_port Network connection (Transceiver), either any specific (0 = BNC, 1 = AUI, 2 = TP) or detected (3 = AUTO). In AUTO mode the driver can detect the network connection automatically (provided that the cable is connected). ------------------------------------------------------------------------- ** 8. MS LAN Manager 2.1A Remoteboot Server Installation ** * 8.1 Introduction * These instructions try to give you a clear picture, how to install remoteboot for MS-DOS 5.00 and OS/2 1.3 workstations in MS LAN Manager 2.1A network operating system environment. Additionally, it describes how to adapt EtherTeam 16i network card drivers to the remoteboot system configuration. * 8.1.1 Installation guidelines * 1. Install MS LAN Manager server with Netbeui and Remoteboot protocols. Reboot the server. Remoteboot is not started yet. 2. Run RPLSETUP. RPLSETUP will copy LAN Manager files for MS-DOS and OS/2 remoteboot workstations. 3. Copy operating system files manually to RPL subdirectories. MS-DOS 5.00 should be installed first on diskettes and then the installed files copied to remoteboot system directories. OS/2 1.3 files can be copied from the same server. OS/2 remoteboot requires multiple steps; that's why files are copied to two destination directories. 4. Run RPLINST. After RPLINST is completed NET START REMOTEBOOT should work OK. 5. Adapt EtherTeam 16i drivers to remoteboot system. * 8.2 MS LAN Manager server installation * LAN Manager server installation is done according to instructions. Remoteboot server option is installed automatically when Remoteboot protocol is defined. LM 2.1A remoteboot can use only Netbeui and Remoteboot protocols. TCP/IP can be used independently. LAN Manager SETUP program menu selections: Configuration Network Drivers Add New Drivers ICL EtherTeam16i Add New Protocols [X] Netbeui [X] Remoteboot After LAN Manager installation, the computer should be rebooted. LAN Manager server starts but the remoteboot service should not start yet. * 8.3 RPLSETUP * Before running RPLSETUP login to network as administrator, e.g: NET LOGON ADMIN PASSWORD Run RPLSETUP. The RPLsetup program will copy LAN Manager files for selected operating systems. If you will boot MS-DOS, select "Install LAN Manager for MS-DOS Workstations" and if you will boot OS/2, select "Install LAN Manager for MS OS/2 Workstations." RPLSETUP prompts for MS LAN Manager installation diskettes and copies files to C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN (OS/2) C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN.DOS (MS-DOS) Replication of remoteboot files is optional and not required. * 8.4 Operating system files copying * Operating system files for MS-DOS 5.00 and OS/2 have to be copied manually to remoteboot system directories. * 8.4.1 MS-DOS 5.00 * 1) Install MS-DOS 5.00 on diskettes or on another workstation hard disk. 2) Change system files attributes not hidden and rename files (use File Manager) IBMDOS.COM (system file, read-only, not hidden) IBMBIO.COM (system file, read-only, not hidden) COPY IBMDOS.COM MSDOS.SYS COPY IBMBIO.COM IO.SYS 3) Copy all MS-DOS files (with subdirectories) to the directory C:\LANMAN\RPL\RPLFILES\BINFILES\DOS500 * 8.4.2 MS OS/2 1.3 * 1) Create directory C:\LANMAN\RPL\RPLFILES\BINFILES\OS213\DLL. Unpack files from MS OS/2 Installation Disk 5 with commands CD C:\LANMAN\RPL\RPLFILES\BINFILES\OS213\DLL UNPACK A:????GA.DL@ 2) Copy OS/2 operating system files C:\*.SYS to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 C:\DISK.TSD to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 If you have Adaptec SCSI controller in workstations, copy C:\*.VSD to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 C:\*.BID to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 If you are using DOS Box in OS/2 workstation, copy C:\COMMAND.COM to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 3) Copy OS/2 boot files to boot block directory (use File Manager): C:\OS2KRNL to C:\LANMAN\RPL\BBLOCK\OS213 C:\OS2LDR to C:\LANMAN\RPL\BBLOCK\OS213 Change flags of the boot files (use File Manager): C:\LANMAN\RPL\BBLOCK\OS213\OS2KRNL (system file, read-only, not hidden) C:\LANMAN\RPL\BBLOCK\OS213\OS2LDR (system file, read-only, not hidden) 4) Copy the other OS/2 operating system files with subdirectories ( use XCOPY /S ) C:\OS2 to C:\LANMAN\RPL\RPLFILES\BINFILES\OS213 * 8.5 RPLINST * Run RPLINST. RPLinstallation will modify RPL.MAP and RPLMGR.INI and share RPL disk resource. When RPLINST completes without errors, remoteboot service can be started with. NET START REMOTEBOOT. * 8.6 EtherTeam 16i Driver Adaptation * Remoteboot shouldn't be running when configuring RPL files. Run NET STOP REMOTEBOOT if necessary. * 8.6.1 EtherTeam 16i DOS driver * 1) Copy EtherTeam 16i driver from the LAN Support diskette: C:\MSLANMAN.DOS\DRIVERS\ETHERNET\ETH16I\ETH16I.DOS to C:\LANMAN\RPL\BBLOCK\NDIS\ETH16I.DOS 2) Copy and edit PROTOCOL.INI to ETH16I directory: MD C:\LANMAN\RPL\BBLOCK\NETBEUI\ETH16I Copy C:\LANMAN\RPL\BBLOCK\NETBEUI\ETHIIE\PROTOCOL.INI to C:\LANMAN\RPL\BBLOCK\NETBEUI\ETH16I\PROTOCOL.INI Edit PROTOCOL.INI: change strings "ETHIIE" to "ETH16I". 3) Copy and edit boot block files: Copy C:\LANMAN\RPL\BBLOCK\NETBEUI\ETHIIE\*.CNF to C:\LANMAN\RPL\BBLOCK\NETBEUI\ETH16I Edit DOSBB.CNF lines: DAT BBLOCK\NETBEUI\ETHIIE\PROTOCOL.INI to DAT BBLOCK\NETBEUI\ETH16I\PROTOCOL.INI DRV BBLOCK\NDIS\ETHIIE.DOS ~ ~ ~ to DRV BBLOCK\NDIS\ETH16I.DOS ~ ~ ~ 4) Edit C:\LANMAN\RPL\RPL.MAP: replace Ethernet IIe with EtherTeam 16i. Boot block record: yyyyyyyyyyyy BBLOCK\NETBEUI\ETHIIE\DOSBB.CNF 2 6 F ~ DOS~Nokia~EthIIe 00004B ~ ,,, ~ RDOS ~ ~ ~ ~ ~ ~ to yyyyyyyyyyyy BBLOCK\NETBEUI\ETH16I\DOSBB.CNF 2 6 F ~ DOS~ICL~Eth16i 00004B ~ ,,, ~ RDOS ~ ~ ~ ~ ~ ~ Workstation record: 00004B?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT *~New~Nokia~Ethernet~IIe~* ~ ~ ~ to 00004B?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT *~New~ICL~EtherTeam~16i~* ~ ~ ~ 5) You don't need to edit C:\LANMAN\RPL\RPLMGR.INI for the DOS driver. 6) Run NET START REMOTEBOOT. 7) Create profiles and workstations with RPLMGR. Use DOS 5.00 (Default) configuration for EtherTeam16i DOS workstation profiles. * 8.6.2. EtherTeam 16i OS/2 driver * 1) Create LM drivers directory ETH16I and copy ETH16.OS2 driver to that directory: MD C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN\DRIVERS\ETHERNET\ETH16I Copy A:\MSLANMAN.OS2\DRIVERS\ETHERNET\ETH16I\ETH16I.OS2 to C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN\DRIVERS\ETHERNET\ETH16I 2) Edit C:\LANMAN\RPL\BBLOCK\NETBEUI\ETH16I\OS213BB.CNF (copied from ..\ETHIIE): DAT BBLOCK\NETBEUI\ETHIIE\PROTOCOL.INI to DAT BBLOCK\NETBEUI\ETH16I\PROTOCOL.INI DRV BBLOCK\NDIS\ETHIIE.DOS ~ ~ ~ to DRV BBLOCK\NDIS\ETH16I.DOS ~ ~ ~ 3) Edit C:\LANMAN\RPL\RPL.MAP: yyyyyyyyyyyy BBLOCK\NETBEUI\ETHIIE\OS213BB.CNF ~ ~ F ~ OS/2~1.3~Nokia~EthIIe 00004B ~ ,,, ~ ROS213 ~ ~ ~ ~ ~ ~ to yyyyyyyyyyyy BBLOCK\NETBEUI\ETH16I\OS213BB.CNF ~ ~ F ~ OS/2~1.3~ICL~Eth16i 00004B ~ ,,, ~ ROS213 ~ ~ ~ ~ ~ ~ and if you haven't already edited when configuring DOS driver 00004B?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT *~New~Nokia~Ethernet~IIe~* ~ ~ ~ to 00004B?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOS ~ DEFAULT *~New~ICL~EtherTeam~16i~* ~ ~ ~ 4) Edit RPLMGR.INI, insert new configuration sections or edit Nokia Ethernet IIe definitions: [configuration] name = O13ICV (previously OS2NOV) os = OS213 dirname = OS2 dirname2 = OS2IC (previously OS2NO) dirname3 = OS2ICV (previously OS2NOV) dirname4 = OS213 bblink = ROS213 fitfileshared = fits\os213v fitfilepersonal = fits\os213vp comment = OS/2 1.3 ICL EtherTeam 16i VGA (previously .. Nokia Ethernet ...) adapter = 00004B?????? memorysize = 3072 videotype = VGA cputype = 286|386|486 [configuration] name = O13ICE (previously OS2NOE) os = OS213 dirname = OS2 dirname2 = OS2IC (previously OS2NO) dirname3 = OS2ICE (previously OS2NOE) dirname4 = OS213 bblink = ROS213 fitfileshared = fits\os213e fitfilepersonal = fits\os213ep comment = OS/2 1.3 ICL EtherTeam 16i EGA (previously .. Nokia Ethernet ...) adapter = 00004B?????? memorysize = 3072 videotype = EGA cputype = 286|386|486 5) Create configuration directories: MD C:\LANMAN\RPL\RPLFILES\CONFIGS\OS2IC MD C:\LANMAN\RPL\RPLFILES\CONFIGS\OS2IC\LANMAN MD C:\LANMAN\RPL\RPLFILES\CONFIGS\OS2ICV MD C:\LANMAN\RPL\RPLFILES\CONFIGS\OS2ICE 6) Copy files under directory C:\LANMAN\RPL\RPLFILES\CONFIGS: CD C:\LANMAN\RPL\RPLFILES\CONFIGS Copy OS2NO\LANMAN\PROTOCOL.INI to OS2IC\LANMAN Edit PROTOCOL.INI strings ETHIIE to ETH16I Copy OS2NOV\CONFIG.SYS to OS2ICV Edit CONFIG.SYS strings ETHIIE to ETH16I OS2NOE\CONFIG.SYS to OS2ICE Edit CONFIG.SYS strings ETHIIE to ETH16I 7) Run NET START REMOTEBOOT. 8) Create OS/2 profiles and workstations with RPLMGR. Use OS/2 ICL EtherTeam 16i configurations for EtherTeam16i OS/2 workstation profiles. ------------------------------------------------------------------------ ** 9. Diagnostic Program. ** ETH16I.EXE Diagnostics Program can be used to test the EtherTeam 16i adapters. The program includes parameter settings to configure the test environment. In the following sections the most important parameters are explained. ETH16I This is the default start. it starts the test and assumes that the adapter is connected to the network with any of the ports on an COMBO adapter or the TP port on an TP adapter. ETH16I /NONET This parameter runs the test in internal loop back mode. This means that no network connection or test plugs are needed. ETH16I /BNC ETH16I /DIX ETH16I /TP These parameters runs the test selecting the specified port. When running the test in this mode the LAN must be connected to the selected port. ETH16I /ECHO300 /IO2A0 /REC These parameters runs the test in echo mode in one machine with two EtherTeam 16i adapters. One adapter with IO address 300 is selected as the echo adapter and the other adapter with IO address 2A0 is selected as adapter to be tested. The adapter to be tested transmits packets trough the connected LAN port to the echo adapter which echoes the packets back to the adapter to be tested. To run this test both adapters must be connected to the same LAN. Note also that this test may block other traffic on the LAN, so it's wise to use a dedicated LAN for this test. ETH16i /ECHO ( in echo PC ) ETH16i /REC ( in test PC ) These parameters do the same as the previous echo mode test with the exception that the echo adapter and the adapter to be tested are installed into two different PC's. ETH16i ? This parameters shows help text and information about the different parameters for the EtherTeam 16i Diagnostics Program. To read this help it is useful to load in your PC ANSI.SYS to get the texts in more readable format.