Server: NetWare 3.11 server
v1.00
NetWare* 3.11 Server Driver Installation Notes for Intel's
EtherExpress(TM) PRO/100B adapter
==========================================================
Location of driver: \NWSERVER\E100B.LAN
Location of NLM's: On Novell's automated services (LANDRV.EXE)
PATCHMAN.NLM (03-24-94 v2.41)
LSLENH.NLM (12-21-94 v1.20)
MSM31X.NLM (11-23-94 v2.50)
ETHERTSM.NLM (11-29-94 v2.50)
MONITOR.NLM (10-26-92 v1.75)
Sample load commands
--------------------
LOAD C:<PATH>\PATCHMAN
LOAD C:<PATH>\LSLENH
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
LOAD C:<PATH>\E100B SLOT=n FRAME=ETHERNET_802.3
BIND IPX TO E100B NET=xxxxxxxx
General instructions
--------------------
1 Install NetWare 3.11 according to the NetWare 3.11 installation
manual.
2 If you're using standard NetWare 3.11 (not SFT III), make sure your
MONITOR.NLM is dated 10-26-92 (or later). Using an earlier version can
cause server failure (ABENDs) when viewing statistics in monitor.
3 If you don't have the current 311NLMs, download them from one of
Intel's online services (World Wide Web at WWW.INTEL.COM or Intel
BBS). See the Installation Guide for Intel BBS phone numbers.
This program will unpack onto the current directory the required
versions of Novell's NLMs for NetWare v3.11 servers.
4 Load the NLMs:
PATCHMAN.NLM (10-05-93 v2.30)
LSLENH.NLM (10-05-93 v1.01)
MSM31X.NLM (06-28-94 v2.31)
ETHERTSM.NLM (06-28-94 v2.31)
MONITOR.NLM (10-26-92 v1.75)
Make sure you use these (or later) versions. Earlier versions may not
work properly.
5 If you can't log in, copy (before starting the server) the E100B.LAN
driver from the \NWSERVER directory on the Configuration and Drivers
disk to the root directory of the server's hard drive.
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.
6 Modify the server's STARTUP.NCF to include:
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 1536 (or larger)
This preallocates server buffers.
7 Start the server. At the server console, issue the load and bind
statement(s) in this order:
LOAD C:<PATH>\PATCHMAN
LOAD C:<PATH>\LSLENH
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
LOAD C:<PATH>\E100B SLOT=x FRAME=ETHERNET_802.3
BIND IPX TO E100B NET=xxxxxxxx
Where:
SLOT=x specifies the PCI device number. Substitute x with the valid
value for the adapter. You will be prompted if you don't specify a
slot number.
NET=xxxxxxxx is the unique network address for that LAN segment.
The default frame type is 802.3. If your workstations needs to use
the 802.2 frame type, see the section later in this document about
using multiple frame types on one adapter.
8 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
==============
Installing multiple adapters
----------------------------
- If you have multiple adapters in a single server, each adapter must
have a different network 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
- 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/100 adapters in the computer.
Recommended settings:
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.
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
board to bind IPX to.
Example:
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
Optional LOAD line parameters
-----------------------------
FORCEDUPLEX: Specifies the duplex mode the driver uses.
A performance option that lets you choose how the adapter sends and
receives packets over the network.
NOTE: If Auto negotiate is NOT being used then it is required that
SPEED be forced to either 10 or 100 Mbps.
Syntax: Forceduplex=n
where n=
0 (Auto-negotiate)
1 (Half duplex
2 (Full duplex)
Duplex modes:
Auto-negotiate _ the adapter negotiates with the hub how to
send/receive packets, either full or half duplex.
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 full duplex hub that doesn't
do auto-negotiation (a non-NWay* hub).
Half duplex _ the adapter performs one operation at a time. It
either sends or receives.
Default: Forceduplex=Auto-Negotiate
A regular adapter can perform only one operation at a time (half-
duplexing). The PRO/100B adapter has the ability to send and
receive packets at the same time (full-duplexing). In order to reap
the benefits of full duplexing, you MUST have a full duplex hub.
The PRO/100 adapter has the added ability to "talk" to the hub and
determine at which mode to communicate (either full or half
duplex). This is called auto-negotiation. You must have a auto-
negotiating hub (an NWay hub) to get full duplex support with the
FORCEDUPLEX parameter set to 0 (auto-negotiation). If you don't
have an auto-negotiating hub, set FORCEDUPLEX to 2 (full duplex)
and then set the SPEED parameter to either 100 Mbps or 10 Mbps.
If you don't know what kind of hub you're attached to, contact your
LAN Administrator
SLOT: Specifies the slot number.
For PCI adapters, SLOT is derived from DEVICE LOCATION and
doesn't map to the physical location of the adapter. Currently,
the PCI specification doesn't tell you how to determine which
adapter corresponds to a device number. One way to do this is to
load the driver from the command line. You'll be prompted with
valid device numbers for the adapter. Select one of them.
Syntax: SLOT=n (n = 1,2,3,4,...15).
SPEED: 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 100 Mbps.
You must use this parameter if you're setting the FORCEDUPLEX
parameter to either half or full.
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
NODE: Specifies a local node address unique to each adapter. The first
two digits of the address indicate who assigned the address when
the driver loads.
Syntax: NODE=02aa12345678
02aa => Locally administered address, 02 is set by MSM
00aa => Typical Intel address (default)
FRAME: Indicates one of four valid frame types the system is
transmitting and receiving.
Syntax: FRAME=n
n = Ethernet_802.2
Ethernet_802.3
Ethernet_II
Ethernet_SNAP
Default: Ethernet_802.3
THRESHOLD: Represents the threshold for transmits from extender SRAM
FIFO. By default threshold is dynamically set based on driver
activity. This parameter overrides the dynamic feature.
Syntax: THRESHOLD=n (n = number of 8 bytes). For example, 16
represents 16x8 (or 128 bytes)..
Default: 16
The maximum number that you can specify is 200 (200x8=1600
bytes).
* Third-party trademarks are the property of their respective owners.
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.