Driver location: \NETWARE\E100ISA.LAN
Required NLMs for NetWare* 3.12:
This version of E100ISA.LAN auto-loads three Novell NLMs (ETHERTSM, MSM31X, and NBI31X) when you load the E100ISA.LAN driver. You may need to update the versions of these three NLMs currently installed on your NetWare 3.12 file server to:
|(08-22-96 v3.18 or later)|
(07-03-96 v3.11 or later)
(08-30-96 v1.49 or later)
Make sure you use these (or later) versions. Earlier versions may not work properly or may generate the following error message:
"Loader cannot find public symbol: "
If you need these updated Novell NetWare NLMs, you can download the file, 100ILAN.EXE, available on any of Intel's online services.
- From the DOS prompt on the server, copy the PRO/100 ISA adapter driver (\NETWARE\E100ISA.LAN) to the Novell directory on the DOS partition of the server's hard drive (drive C:).
- If necessary, copy the updated Novell NLMs to the Novell directory on the DOS partition of the server's hard drive (drive C:).
- Start NetWare by typing SERVER or the name of your startup batch file.
- Load the updated Novell NLMs.
- LOAD C:\MSM31X
- LOAD C:\NBI31X
- LOAD C:\ETHERTSM
- Load the PRO/100 ISA adapter driver. At the server's colon (:) prompt, type:
- LOAD C:\E100ISA
- Bind the driver. At the server's colon (:) prompt, type:
- BIND IPX TO E100ISA NET=xx
WHERE: xx is the external network number.
At this point you should be able to log into the server from a workstation.
To Make this permanent:
Using Novell's INSTALL program, edit the AUTOEXEC.NCF file to add the LOAD and BIND statements for the EtherExpress adapter.
Installing multiple EtherExpress PRO/100 ISA adapters:
If you have multiple network adapters in a single server, each adapter must have a different NETwork number, a different SERIAL. Also, You must name each adapter using the "NAME=" parameter. For example:
LOAD C:\E100ISA SERIAL=044721 NAME=LANA
NOTE: The serial number is the last six digits of the EtherExpress PRO/100 ISA adapter MAC address.
The MAC address label is on the back of the PRO/100 ISA LAN adapter.
BIND IPX TO LANA NET=10
LOAD C:\E100ISA SERIAL=044735 NAME=LANB
BIND IPX TO LANB NET=20
Installing one EtherExpress card with multiple frame types:
When binding multiple frame types to one card, enter a LOAD statement for each frame type. You must name each board using the "NAME=" parameter. For example:
LOAD C:\E100ISA FRAME=ETHERNET_802.2 NAME=LAN8022
Do not confuse the NETwork number with the internal IPX number. They need to be different. See the NetWare Installation manual for more information.
BIND IPX TO LAN8022 NET=10
LOAD C:\E100ISA FRAME=ETHERNET_II NAME=LANII
BIND IPX TO LANII NET=20
Adding TCP/IP protocol:
If you are using NetWare's TCP/IP NLM, you must load an Ethernet type II frame and bind the EtherExpress adapter to TCPIP. For example:
"Loader cannot find public symbol: "
"Load file referenced undefined public variable"
This error message occurs when the server is loading older versions of ETHERTSM.NLM, NBI31X.NLM or MSM31X.NLM.
Using E100ISA.LAN keyword options:
There are several driver keywords that are supported when loading the PRO/100 ISA driver. For example:
LOAD C:\E100ISA MEDIATYPE=HALF100 RXEARLY=OFF USE32BITIO=NO
The following driver keywords are supported by the PRO/100 ISA adapter. All keywords are optional.
||Specifies which physical medium is attached to the adapter. The default is automatic configuration.|
|| AUTO -- auto-detect speed and duplex of the network |
HALF10 -- 10 Mbps half duplex connection is required
FULL10 -- 10 Mbps full duplex connection is required
HALF100 -- 100 Mbps half duplex connection is required
FULL100 -- 100 Mbps full duplex connection is required
||Any legal 12 digit hexadecimal ethernet value|
||Overrides the EtherExpress PRO/100 ISA adapter's unique Ethernet hardware address.|
|| xx-xx-xx-xx-xx-xx (an Ethernet hardware address, where x is a hexadecimal byte value)|
||Use the RXEARLY keyword to DISABLE RX EARLY interrupt
generation (pipelined processing of receive packets,
also called Early Receives). Using RXEARLY ON improves
performance by reducing receive latency, but increases
the CPU overhead incurred by the driver.|
||Prevents driver from performing 32-bit I/O operations
to the adapter. Some PCI/ISA motherboard chip sets
have problems with this 32-bit operation and the
results are data corruption.|
||Specifies the Plug and Play serial number of the
adapter; required only when multiple adapters are
present in the system. The default value #0 can be
used if there is only one adapter in the system.|
||#0 or #nnnnnn, where the nnnnnn is the last 6 digits
of the IEEE address that can be found on the adapter
on a bar-coded label with the legend "MAC=".|
The EtherExpress PRO/100 ISA adapter server driver maintains the following custom statistics, which can be viewed by loading the NetWare MONITOR program:
|Current Line Speed (Mbps):
Duplex Mode (0 = Half, 1 = Full):
Link State (0=Down, 1=Up, 2=Unknown):
Receive Symbol Errors (100 Mbps only):
Get RCB Attempts Reject Count:
Early Receive Interrupts Count:
Back-to-back Send Count:
No Transmit Resources Count:
|10 or 100|
0 or 1
0, 1, or 2
If the driver's MEDIATYPE setting for the EtherExpress PRO/100 ISA adapter is AUTO (or was not specified) the Current Line Speed, Duplex Mode, and Link State are updated any time that the driver detects changes in the EtherExpress PRO/100 ISA adapter and its physical network connection.
Receive Symbol Errors apply to 100 Mbps operation only. They are also counted in the General Statistics Checksum Errors counter.
If the Get RCB Attempts Reject Count is counting upward quickly, it probably means that some client station(s) on the network is not using the correct FRAME type to communicate to the server or that the server does not have the correct FRAME types bound to the IPX protocol stack.
The Early Receive Interrupts Count gives an indication of how much early receive packet processing is happening. This count will remain at 0 if RXEARLY=OFF has been used or if both RXBURSTCOUNT and RXBURSTTIMEOUT have been specified.
The Back-to-back Send Count is the number of packets that were queued to the driver for transmission while the driver was busy.
The No Transmit Resources Count is the number of transmit attempts that failed because the driver had run out of transmit descriptors.
This applies to: