4 Server: NetWare 3.11 server v1.03 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. 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 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. 4 If you can't log in (before starting the server) copy 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. 5 Modify the server's STARTUP.NCF to include: SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 1536 (or larger) This preallocates server buffers. 6 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.2. If your workstations needs to use the 802.3 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 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 - 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. 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: Note: The PRO/100B T4 adapter does not support full duplex at 100 Mbps. It does at 10 Mbps. The PRO/100B TX adapter supports full duplex at 10 and 100 Mbps. Syntax: FORCEDUPLEX=n 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) Duplex modes: 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. Note: The PRO/100B T4 adapter does not support auto-negotiate. 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 duplex. Half duplex: the adapter performs one operation at a time. It either sends or receives. Default: auto-negotiation (PRO/100B TX adapter) half duplex (PRO/100B T4 adapter) The PRO/100B TX 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 an auto- negotiating hub (an Nway switch) to get full duplex support with the FORCEDUPLEX parameter set to 0 (auto-negotiation). Examples: PRO/100B TX (100 Mbps full duplex): FORCEDUPLEX=2 (Sets adapter to full duplex) SPEED=100 (See SPEED parameter below) PRO/100B TX (10 Mbps full duplex): FORCEDUPLEX=2 (Sets adapter to full duplex) SPEED=10 PRO/100B T4 (100 Mbps full duplex): Not Supported PRO/100B T4 (10 Mbps full duplex): FORCEDUPLEX=2 (Sets adapter to full duplex) SPEED=10 Note: Use auto-negotiate for full duplex support only when the adapter is connected to a switch that fully supports Nway auto negotiation specification. SLOT: Specifies the slot number. For PCI adapters, SLOT is derived from the bus number and device location as defined by the PCI spec. 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. Select one of them. Syntax: SLOT=n (n = 1,2,3,4,...) Note: Future versions of NetWare will use NBI (NetWare Bus Interface) to determine the slot number. NBI will map the slot number to a different slot number than SETUP.EXE on the Intel Installation and Driver disk reports. SPEED: Specifies the speed the driver uses. If you don't use this parameter, the driver automatically detects the network speed. If unable to autosense, 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 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: The adapter automatically senses speed NODE: 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, A, E. Syntax: NODE=02a012345678 02 => LLA, 02 is set by the driver if not specified. 00 => 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.2 TXTHRESHOLD: Represents the threshold for transmits from extender SRAM FIFO (output buffer). 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 host memory. Default: dynamically set The maximum number that 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.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.