CONTENTS
1 INTRODUCTION
2 GENERAL INSTALLATION INFORMATION
2.1 Dual Mode Drivers
2.2 Naming Convention
2.3 I/O Parameters
2.3.1 Interrupt Number
2.3.2 Slot Number
2.3.3 I/O Base Address
2.3.4 Transceiver
2.3.5 Searching Adapters.
2.3.6 Installing Several Adapter Instances.
2.4 EtherTeam16i and WAN AT Adapters
3 NDIS2 DRIVERS FOR ICL ETHERTEAM16I
3.1 LAN Manager 2.x
3.2 Windows For Workgroups 3.1
3.3 IBM LAN Server 2.0 and 3.0
4 NT DRIVER FOR ICL ETHERTEAM16I
4.1 Installation of the Driver
4.2 Advanced Installation Features
4.3 Driver Error Codes
5 WINDOWS 95 DRIVER FOR ICL ETHERTEAM16I/32
5.1 Installation of the Driver
5.2 Advanced Installation Features
6 WINDOWS FOR WORKGROUPS 3.11 DRIVER FOR ICL ETHERTEAM16I/32
6.1 Installation of the Driver
6.2 Advanced Installation Features
7 NETWARE DRIVERS FOR ICL ETHERTEAM16I
7.1 DOS ODI Workstation Driver
7.1.1 NetWare 3.12 or NetWare 4.x Client
7.1.2 NetWare 3.11 Client
7.2 OS/2 ODI Workstation Driver
7.3 NetWare 386 ODI Server Driver
7.3.1 NetWare 3.12 or NetWare 4.x Server
7.3.2 NetWare 3.11 Server
7.4 NetWare NT Client
7.5 NetWare IPX 2.X Server Driver
7.6 Remote Program Load
8 SCO UNIX LLI driver for SCO UNIX 3.2v4.x
8.1 SCO UNIX Driver Files
8.2 Installing The SCO UNIX Driver
8.3 Configuring The SCO UNIX Driver
9 ETHERTEAM16I IEEE 802.1E PROM
9.1 Updating BOOTDD.SYS
10 FTP PACKET DRIVER FOR ICL ETHERTEAM16I
10.1 Installation of the Driver
11 NT DRIVER FOR ICL ETHERTEAM LOOPBACK ADAPTER
11.1 Installation of the Driver
11.2 Advanced Installation Features
11.3 Driver Error Codes
1 INTRODUCTION
This EtheTeam16i/32 LAN Support Software Disk v2.3 contains the following
software products for the ICL EtherTeam16i and EtherTeam32 EISA adapters.
- NDIS2 Drivers for LAN Manager, Windows for Workgroups and IBM Lan Server.
- NDIS3 Drivers for Windows for Workgroups 3.11, Windows NT and Windows 95.
- Novell NetWare Drivers for DOS and OS/2 Clients, 3.x and 4.x ODI Server
and 2.x IPX Server.
- SCO UNIX LLI Driver for SCO UNIX 3.2v4.x
- FTP Packet Driver
- Necessary Installation Information files.
- EtherTeam16i/32 Configuration Utility.
- EtherTeam16i Diagnostics Program
- EtherTeam16i Monitor Program
The NetWare Drivers are Novell certified and the NDIS Drivers are Microsoft
certified.
2 GENERAL INSTALLATION INFORMATION
2.1 Dual Mode Drivers
All EtherTeam16i Drivers have been modified so that they support also the
EtherTeam32 EISA Adapter. The changes done to the existing EtherTeam16i
drivers are:
1. Support to use the I/O Base Addresses of EtherTeam32 Adapters installed
in EISA slots.
2. Support to use the extended set of IRQ numbers for EtherTeam32 Adapters.
3. Support to use 32-bit I/O Data Transfer for EtherTeam32 Adapters.
2.2 Naming Convention
The drivers have been originally written to EtherTeam16i, and their
adaptation to the EtherTeam32 has been only to modify them so that they
provide the new features mentioned in the previous section.
Because of this, the text "EtherTeam16i" appears in all display and log
messages irrespective of which adapter type they are running. Only the name
of the driver, when loaded, is output as "EtherTeam16i/32".
Later in this documentation, the name EtherTeam16i/32 refers to both
EtherTeam16i and EtherTeam32.
2.3 I/O Parameters
Take care that your EtherTeam16i or EtherTea32m EISA Adapters are properly
configured to your system, and that they do not conflict with any other
adapters.
1. In case of EtherTeam16i, use the EtherTeam16i Configuration Utility to
check and optinally modify the I/O Base Addresses and IRQ Numbers of the
adapters to be installed. The factory defaults of the adapter are:
I/O Base Address : 02A0
IRQ Number : 10
2. In case of EtherTeam32 EISA Adapter, use the EISA Configuration Utility
to install the Adapter to the system.
By default, the I/O Base Address, IRQ Number and Transceiver may be left to
the value AUTO when completing the installation of the driver, especially if
there is only one adapter instance concerned.
2.3.1 Interrupt Number
The interrupt numbers available on EtherTeam32 differ from those on
EtherTeam16i, and are as follows:
EtherTeam32 : 3, 5, 7, 9, 10, 11, 12, 15
EtherTeam16i : 5, 9, 10, 15
It is preferred to leave the Interrupt Number (IRQ) to the default value
AUTO, in which case the driver gets the current IRQ either from the Setup
EEPROM (EtherTeam16i) or EISA Configuration (EtherTeam32).
If explicitly defined, select the Interrupt Number according to the EEPROM
Setup or the EISA Configuration value of your adapter. An explicit definition
of the IRQ cannot override its Setup value.
2.3.2 Slot Number
A new keyword for SlotNumber (SlotNumber or Slot, depending on the driver)
has been added to the NDIS and ODI drivers to specify the EtherTeam32 Adapter
I/O Slot explicitly.
Possible values : 1 .. 8
Default : AUTO
The default value "AUTO" means that the drivers search for an EtherTeam32
adapter from available slots.
If explicitly defined, select the Slot Number according to EISA Configuration
value of your adapter. An explicit definition of the Slot Number cannot
override its Setup value.
2.3.3 I/O Base Address
The available I/O Base Addresses of an EtherTeam16i Adapter are:
0240, 0260, 0280, 02A0, 0300, 0340, 0380
In most of the drivers, an EtherTeam32 Adapter can also be identified by its
I/O Base Address as "X000", where X is the Slot Number.
Possible values : X000, where X = 1..8
Default : AUTO
The default value AUTO means that the drivers search for an existing
EtherTeam16i or EtherTeam32 adapter from available I/O Base Addresses.
If explicitly defined, select the I/O Base Address according to the EEPROM
Setup or EISA Configuration value of your adapter. An explicit definition of
the I/O Base Address cannot override its Setup value.
2.3.4 Transceiver
The value SETUP 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. The value AUTO means that the driver
detects automatically the network connection (provided that the cable is
connected while loading the driver).
2.3.5 Searching Adapters.
If the I/O Base Address or Slot Number is not given explicitly (default), the
drivers search for existing adapters as:
- If an EISA system board is concerned, EtherTeam32 Adapters are first
searched and allocated from slots in the following order:
Slot1, Slot2, Slot3, ... Slot8
2. If no (or not enough) EtherTeam32 Adapters were found, or an ISA system
board is concerned, EtherTeam16i Adapters are then searched and allocated
from I/O Addresses in the following order:
0240, 0260, 0280, 02A0, 0300, 0340, 0380
2.3.6 Installing Several Adapter Instances.
If there is only a single adapter installed, the I/O Base Address (or Slot
Number) can always be left to the value AUTO.
In most of the drivers, the I/O Base Address (or Slot Number) can be left as
AUTO even if several adapters are installed in the system, provided that:
1. In case of the NetWare 386 ODI Server Driver, the NetWare 2.x IPX Server
Driver and the FTP Packet Driver the adapter instances following the
first one must be given explicitly (see the corresponding sections).
2. Adapters installed must be either EtherTeam16i or EtherTeam32 Adapters
(It is possible that there are both EtherTeam16i and EtherTeam32 Adapters
installed in an EISA machine).
3. Do not use any "mixed" definitions for the I/O Base Addresses (or Slot
Numbers). Either define them all explicitly or leave them all AUTO.
2.4 EtherTeam16i and WAN AT Adapters
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.
3 NDIS2 DRIVERS FOR ICL ETHERTEAM16I
The NDIS drivers for EtherTeam16i/32 can be found from the subdirectories
MSLANMAN.DOS\DRIVERS\ETHERNET\ETH16I and MSLANMAN.OS2\DRIVERS\ETHERNET\ETH16I
and have the following file names:
ETH16I.DOS DOS Driver
ETH16I.OS2 OS2 Driver
PROTOCOL.INI Template
OEMSETUP.INF OEM Setup File
NOTE: There is a keyword "PROCESSOR = 286" to be added in PROTOCOL.INI when
(and only when) the OS/2 Driver is run in 286 CPU machine.
3.1 LAN Manager 2.x
To install the NDIS drivers (NDIS2), just use the normal Lan Manager 2.x
installation programs. After prompting and reading the EtherTeam16i/32 LAN
Support Diskette, select the adapter, either EtherTeam16i or EtherTeam32
according to which one you are installing.
By default, the I/O Base Address, IRQ Number and Transceiver may be left to
the value AUTO in PROTOCOL.INI.
3.2 Windows For Workgroups 3.1
To install the Driver for ICL EtherTeam16i/32, do the following:
1. Use the Windows Setup to install the driver. Give the path A:\WFW310 when
prompted for the OEM Driver diskette.
2. Select the adapter, either EtherTeam16i or EtherTeam32 according to which
one you are installing.
By default, the I/O Base Address, IRQ Number and Transceiver may be left
to the value AUTO. Optionally, they may be modified as:
1. Select the I/O Base Address according to the configuration of the
EtherTeam16i/32 Adapter.
2. Select the Interrupt Number according to the configuration of the
EtherTeam16i/32 Adapter.
3. Select the Transceiver, either explicitly (BNC, TP or AUI), or
leaving it as AUTO.
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.
NOTE! After reading the OEM Driver Diskette, both EtherTeam16i and
EtherTeam32 cards should appear in the menu. If this doesn't happen, the
reason for this might be an existing EtherTeam16i definition in your old
NETWORK.INF file (in subdirectory \WINDOWS\SYSTEM). Remove it by commenting
the corresponding line from NETWORK.INF (Before editing NETWORK.INF, take
backup of it for sure).
;icl$eth16i="ICL EtherTeam 16i Adapter",1391,ndis, ......
3.3 IBM LAN Server 2.0 and 3.0
Follow the LAN Server installation instructions and IBM documentation. When
prompted for the additional driver diskette, give the path A:\IBM containing
the *.NIF files and the driver file.
Select the adapter, either EtherTeam16i or EtherTeam32 according to which one
you are installing.
By default, the I/O Base Address, IRQ Number and Transceiver may be left to
the value AUTO.
4 NT DRIVER FOR ICL ETHERTEAM16I
4.1 Installation of the Driver
The NT drivers for EtherTeam16i/32 can be found from the subdirectory
NDIS3\NT and 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/32, do not use the "Detect
Network Adapter" option. It is prefrable to select the EtherTeam16i/32
adapter manually.
To install the NT Driver for ICL EtherTeam16i/32, 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.
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.
Select the adapter, either EtherTeam16i or EtherTeam32 according to which
one you are installing.
By default, the I/O Base Address, IRQ Number and Transceiver may be left
to the value AUTO. Optionally, they may be modified as:
1. Select the I/O Base Address according to the configuration of the
EtherTeam16i/32 Adapter.
2. Select the Interrupt Number according to the configuration of the
EtherTeam16i/32 Adapter.
3. Select the Transceiver, either explicitly (BNC, TP or AUI), or
leaving it as AUTO.
4.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/32 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/32) 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/32 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 "Driver Error Codes", Error Code 0016).
4.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.
0018 = Missing IRQ From Setup
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 "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.
5 WINDOWS 95 DRIVER FOR ICL ETHERTEAM16I/32
5.1 Installation of the Driver
The Windows 95 drivers for EtherTeam16i/32 can be found from the subdirectory
NDIS3\WIN95 and have the following file names:
ETH16I.VXD Windows 95 Driver
NETICL.INF OEM Setup File
There is no automatic detection for EtherTeam16i/32 card in Windows 95
environments. Because of that, it must be installed manually. To install the
Windows 95 Driver for ICL EtherTeam16i/32, do the following:
1. Use the Windows 95 "Control Panel" / "Network" to install the driver.
2. At first select "Add" / "Adapter", then select "Have Disk" and give the
path A:\NDIS3\WIN95 when prompted for the OEM Driver diskette.
3. Select the adapter, either EtherTeam16i or EtherTeam32 according to which
one you are installing.
NOTE! By default, the I/O Base Address, IRQ Number and Transceiver are
left to the value AUTO.
5.2 Advanced Installation Features
There are some keywords detected by the driver which can be accessed from the
"Properties" / "Advanced" menu.
1. Transceiver Select the Transceiver, either explicitly (BNC, TP or AUI),
or leaving it as AUTO.
2. SlotNumber Specifies explicitly the EISA Slot where the EtherTeam32
Adapter is installed. The value AUTO (default) means that the adapter is
searched from the possible EISA Slots.
NOTE! The following 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)
NOTE! For the explanation of the StagedReceive parameter, see the
description of the parameter "StagedReceive" in the section "Advanced
Installation Features" of the Windows NT Driver.
6 WINDOWS FOR WORKGROUPS 3.11 DRIVER FOR ICL ETHERTEAM16I/32
6.1 Installation of the Driver
The Enhanced Mode Windows drivers for EtherTeam16i/32 can be found from the
subdirectory NDIS3\WIN and 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/32, 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.
NOTE! The OEMSETUP.INF can be found also from the OEM Driver Disk root.
2. Select the adapter, either EtherTeam16i or EtherTeam32 according to which
one you are installing.
By default, the I/O Base Address, IRQ Number and Transceiver may be left
to the value AUTO. Optionally, they may be modified as:
1. Select the I/O Base Address according to the configuration of the
EtherTeam16i/32 Adapter.
2. Select the Interrupt Number according to the configuration of the
EtherTeam16i/32 Adapter.
3. Select the Driver. The Enhanced Mode NDIS Driver corresponds to the
NDIS3 Driver and the Real Mode NDIS Driver to the NDIS2 Driver,
respectively.
6.2 Advanced Installation Features
There are some keywords detected by the driver which can be accessed from the
Advanced menu.
1. Transceiver Select the Transceiver, either explicitly (BNC, TP or AUI),
or leaving it as AUTO.
2. SlotNumber Specifies explicitly the EISA Slot where the EtherTeam32
Adapter is installed. The value AUTO (default) means that the adapter is
searched from the possible EISA Slots.
NOTE! The following 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)
NOTE! For the explanation of the StagedReceive parameter, see the
description of the parameter "StagedReceive" in the section "Advanced
Installation Features" of the Windows NT Driver.
7 NETWARE DRIVERS FOR ICL ETHERTEAM16I
These are short installation instructions for EtherTeam16i/32 NetWare
Drivers. For more detailed information, see the proper Novell documentation.
NOTE! The Dedicated DOS IPX Workstation Driver has not been developed for
EtherTeam16i/32. The DOS IPX driver has been 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.
7.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.
7.1.1 NetWare 3.12 or NetWare 4.x Client
Installing DOS Workstation (NetWare Client) may take place using the
corresponding INSTALL utilities. Give the path A:\NETWARE\DOSODI when
prompted for the OEM Driver Diskette.
When seleting the driver parameters, it is not necessary to give the I/O-
Address (or Slot) and IRQ Number explicitly, but they can be left to their
default value (AUTO).
7.1.2 NetWare 3.11 Client
Installing the DOS ODI Workstation Driver for ICL EtherTeam16i/32 is to be
done "manually", as follows:
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.EXE
7.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/32, 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/32).
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/32, 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).
7.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.11 installation only, can be found from the
subdirectory NETWARE\386SRV\3.11 and have the following file names:
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! The NetWare ODI Server Driver is implemented according to specification
3.1, and requires MSM.NLM and ETHERTSM.NLM in order to work.
NOTE! In case of several adapters installed, the I/O Base Addresses must be
given explicitly.
7.3.1 NetWare 3.12 or NetWare 4.x Server
Installing NetWare 3.12 or 4.x Server may take place using the corresponding
INSTALL utilities. Give the path A:\NETWARE\386SRV when prompted for the OEM
Driver Diskette.
It may be that the installation tries to load the ETHERTSM.NLM and MSM.NLM
from the diskette but you can disregard the possible error messages
concerning this.
Depending on how the installation takes place, it may be in some cases
necessary to copy the Network Driver files to a subdirectory on the hard disk
(e.g. to \NETWARE). To do this, copy the files MSM.NLM and ETHERTSM.NLM from
the Netware Installation Diskettes and the LAN Driver ETH16I.LAN from the OEM
Diskette to this subdirectory. Then give path to this subdirectory when
loading the driver.
WARNING! The MSM.NLM, ETHERTSM.NLM and MONITOR.NLM on the 3.11 subdirectory
are for 3.11 installation only. Never use them in 3.12 or 4.x installation.
7.3.2 NetWare 3.11 Server
WARNING! DO NOT INSTALL this driver to NetWare 3.11 Server, unless you are
quite sure that the MSM.NLM (or MSM31X.NLM) of your system are
compatible with the Spec 3.1 ODI driver. The possible
incompatibility may even cause your system to crash!
To be compatible with spec 3.1 ODI Driver, the MSM and ETHERTSM
must be of the version (or later):
MSM.NLM vers 2.14 11.03.93
ETHERTSM.NLM vers 2.14 11.03.93
The incompatibility problem here lies on the fact a combination of
an "old" MSM and a "new" LAN Driver (HSM) runs the system into a
state where all lower priority interrupts will stay disabled after
the first LAN driver interrupt.
Installing the 3.11 ODI Server Driver for ICL EtherTeam16i/32 is to be done
"manually", as follows:
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.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
NOTE! If you have more recent versions of these files, use them instead
of those on EtherTeam16i/32 driver diskette.
3. Load the LAN Driver (The ETH16I.LAN loads MSM and ETHERTSM modules
implicitly), and bind the Network Driver, e.g.
LOAD LSLENH
LOAD C:ETH16I INT=A PORT=2A0
BIND C: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.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
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 LSLENH
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/32 Driver, a new version
of the MONITOR.NLM is required.
7.4 NetWare NT Client
The drivers for EtherTeam16i/32 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/32, 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.
By default, the I/O Base Address, IRQ Number and Transceiver may be left
to the value AUTO. Optionally, they may be modified as:
1. Select the I/O Base Address according to the configuration of the
EtherTeam16i/32 Adapter.
NOTE! In case of several adapters installed, the I/O Base Addresses
must be given explicitly.
2. Select the Interrupt Number according to the configuration of the
EtherTeam16i/32 Adapter.
3. Select the Transceiver, either explicitly (BNC, TP or AUI), or
leaving it as AUTO.
7.5 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/32 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/32 2.x Server
Driver.
To install the 2.x IPX Server Driver for ICL EtherTeam16i/32, 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/32 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/32 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/32 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/32 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.
7.6 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.
8 SCO UNIX LLI driver for SCO UNIX 3.2v4.x
8.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.
8.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.
8.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.
9 ETHERTEAM16I IEEE 802.1E PROM
9.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.
10 FTP PACKET DRIVER FOR ICL ETHERTEAM16I
10.1 Installation of the Driver
To install the FTP Packet Driver, start it with the following command line
syntax :
eth16i [options] <packet_int_no> [<io_addr> [<net_port>]]
No specifications for the I/O-Base Address, Slot Number or Interrupt Number
are needed, but the driver resolves them according to the default values on
the Adapter Setup EEPROM or the EISA Configuration. 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 AUTO Search Mode (Default).
NOTE! The I/O-Base Address of an EtherTeam32 Adapter is given as
"OxN000", where N is the Slot Number, e.g:
load eth16i 0x60 0x3000 -- EtherTeam32 Adapter in Slot 3.
NOTE! In systems where several EtherTeam16i/32 Adapters are installed,
the I/O-Base Addresses of the latter adapter instances must be given
explicitly, e.g:
load eth16i 0x60 -- The 1'st instance is searched.
load eth16i 0x61 0x300 -- The 2'nd instance is specified.
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).
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.