NW312.TXT Driver File Contents (IEE_100B.ZIP)
Driver Package File Name: IEE_100B.ZIP
3 Server: NetWare 3.12 & 4.10 servers
NetWare* 3.12 and 4.10 Server Driver Installation Notes for Intel's
EtherExpress(TM) PRO/100B adapter
Location of driver: \NWSERVER\E100B.LAN (ODI Assembly Specification
Location of NLMs: Novell's automated services (LANDR9.EXE or greater)
NOTE: LANDRx.EXE is a Novell archive that contains the latest
server NLMs and support files. The x in LANDRx.EXE is subject
to change with each new release of the archive.
These instructions are for use with the ODI Assembly Specification v3.30
NLMs. The \NWSERVER\E100B.LAN driver on this disk is written to this
specification. To load the driver on NetWare 4.10 or 3.12 requires
updated ETHERTSM, MSM and the new NBI.NLM. Obtain these files from
Novell's automated services.
For NetWare 4.10:
NBI.NLM (ver 1.49, 08/30/96 or newer)
MSM.NLM (ver 3.18, 08/22/96 or newer)
ETHERTSM.NLM (ver 3.11, 07/03/96 or newer)
For NetWare 3.12:
NBI31X.NLM (ver 1.49, 08/30/96 or newer)
MSM31X.NLM (ver 3.18, 08/22/96 or newer)
ETHERTSM.NLM (ver 3.11, 07/03/96 or newer)
Note: NBI.NLM (or NBI31X.NLM) must be loaded before MSM and ETHERTSM.
NetWare 3.12 needs MSM31X.NLM renamed to MSM.NLM.
Sample load commands
LOAD C:<PATH>\E100B SLOT=n FRAME=ETHERNET_802.2
BIND IPX TO E100B NET=xxxxxxxx
1 Install NetWare 3.12 or 4.10 according to the NetWare instructions.
2 Copy the PRO/100B server driver (\NWSERVER\E100B.LAN) and any updated
NLMs, to the NetWare server's hard drive.
If you can't log in to the server (before starting the server) copy
the E100B.LAN driver from the \NWSERVER directory on the Intel
Configuration and Drivers disk to the root directory of the server's
If you can log into the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a path on the
load line. If you copy it to another directory, make sure the LOAD
statement includes the correct path.
3 Start the server. At the server console, load NBI, MSM and ETHERTSM
(for NetWare 3.12 load NBI31X, MSM31X and ETHERTSM) in this order.
Next, load and bind the server driver as follows:
LOAD C:<PATH>\E100B SLOT=x FRAME=ETHERNET_802.2
BIND IPX TO E100B NET=xxxxxxxx
SLOT=x Specifies the NBI (NetWare Bus Interface) slot number.
Substitute x with the valid value for the adapter. You will be
prompted with the slot number(s) of installed PRO/100B adapters. The
NBI numbers are different from the slot number indicated in the Intel
NET=xxxxxxxx is the unique network address for that LAN segment.
The default frame type is 802.2. If your workstation needs to use the
802.3 frame type, see the section later in this document about using
multiple frame types on one adapter.
4 Add the load and bind statements you need to the server's AUTOEXEC.NCF
file so the EtherExpress PRO/100B adapter driver loads automatically
each time the server starts.
Hints and tips
1 If the error message MSGetPhysical is encountered:
Upgrade the ETHERTSM.NLM and MSM31x.NLM and be sure to rename
MSM31x.NLM to MSM.NLM
2 Installing multiple adapters:
If you have multiple adapters in a single server, each adapter must
have a different NET number and SLOT number. Also, you may want to
name each adapter. For example:
LOAD C:\E100B SLOT=3 NAME=LAN_A
BIND IPX TO LAN_A NET=222
LOAD C:\E100B SLOT=4 NAME=LAN_B
BIND IPX TO LAN_B NET=333
3 If you have problems loading the driver on multiple adapters and the
initialization fails due to "Insufficient RCBs," increase the number
of buffers allocated to the server. Add the following to STARTUP.NCF:
SET MINIMUM PACKET RECEIVE BUFFERS = 100 (or larger)
SET MAXIMUM PACKET RECEIVE BUFFERS = 500 (or larger)
The MINIMUM value you specify must be at least 30 times the number of
EtherExpress PRO/100B adapters in the computer.
1-3 adapters: 100
4 adapters: 150
The MAXIMUM you can specify depends on the amount of memory in the
server, but it must be greater than the MINIMUM.
4 Installing one adapter with multiple frame types:
When binding multiple frame types to one adapter, enter a LOAD and
BIND statement for each frame type. Each LOAD statement uses the same
SLOT number, but each BIND statement needs a unique network number.
You must also include a name on each load line to avoid being prompted
for the adapter to bind IPX to.
LOAD C:\E100B SLOT=3 FRAME=ETHERNET_802.3 NAME=LAN8023
BIND IPX TO LAN8023 NET=77777
LOAD C:\E100B SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
BIND IPX TO LAN8022 NET=88888
5 Optional LOAD line parameters:
Auto-negotiate: The adapter negotiates with the hub how to
send/receive packets, either full or half duplex. If unsuccessful
at negotiating the duplex, the adapter defaults to half duplex. You
must have an auto-negotiating hub (an Nway* switch) to get full
duplex support with the FORCEDUPLEX parameter set to 0 (auto-
Full duplex: The adapter sends and receives packets at the same
time. This improves the performance of your adapter. Set duplex
mode to full duplex ONLY if you have a switch that supports full
Half duplex: The adapter performs one operation at a time. It
either sends or receives.
Note: The PRO/100B T4 adapter does not support full duplex at 100
Mbps, nor does the T4 adapter support Auto-Negotiation, or
Nway. The PRO/100B TX adapter does not have any of these
Where n=0 auto-negotiate (PRO/100B TX adapter only)
1 half duplex
2 full duplex
Note: If the adapter is set to half or full duplex, set the SPEED
parameter to either 10 or 100. (see SPEED below)
Default: auto-negotiation (PRO/100B TX adapter)
half duplex (PRO/100B T4 adapter)
PRO/100B TX (100 Mbps full duplex):
PRO/100B TX (10 Mbps full duplex):
PRO/100B T4 (100 Mbps full duplex): Not Supported
PRO/100B T4 (10 Mbps full duplex):
For PCI adapters, SLOT is derived from bus number and device
location. Novell determines the slot number for PCI and Plug and
Play adapters using NBI. These slot numbers are different then
the slot numbers used with other drivers or the Intel SETUP
utility. One way to determine the slot number is to load the
driver from the command line. You'll be prompted with valid
device number(s) for the adapter(s). Select one of them.
Syntax: SLOT=n (n = 1,2,3,4,...)
Specifies the speed the driver uses. If you don't use this
parameter, the driver automatically detects the network speed. If
no cable is attached, the driver defaults to 10 Mbps.
NOTE: You must set the SPEED parameter to either 10 or 100 if
you're setting the FORCEDUPLEX parameter to either half or
If you use this parameter, the driver operates at the specified
speed instead of auto-detecting network speed.
Syntax: SPEED=n (n = 10 or 100)
Default: none, the adapter automatically senses speed.
Specifies a local administered address (LAA) unique to each
adapter. Use this option to provide your own unique node address
for the adapter. The node address is a 12-digit hexadecimal
number; the second digit must be one of the following digits: 2, 6,
n = 2, 6, A, E
x = hexadecimal number
Default: The adapter's assigned address
Configures the adapter to process one of the four valid NetWare
Ethernet frame types.
n = Ethernet_802.2
Represents the threshold for transmits from extended SRAM FIFO.
Syntax: TXTHRESHOLD=n (n = number of 8 bytes)
For example, 16 represents 16x8 (or 128 bytes). In this case,
the LAN controller transmits after copying 128 bytes from the
Default: dynamically set
The maximum number you can specify is 200 (200x8=1600 bytes) which
ensures there will not be any underruns.
* Third-party trademarks are the property of their respective owners.