Workstation for DOS ODI Client
v1.00
NetWare* DOS ODI Client Driver installation notes for Intel's
EtherExpress(TM) PRO/100B LAN Adapter
=============================================================
Location of Driver: \DOS\E100BODI.COM
Quick Installation
------------------
Use the Automatic setup option in the SETUP utility on the Intel
Configuration and Drivers disk to quickly and easily install the ODI
driver. For workstations using VLM's, see the VLM client section below.
Sample Configuration Files
--------------------------
AUTOEXEC.BAT:
CD\NWCLIENT
LSL
E100BODI
IPXODI
NETX or VLM (VLM's for NetWare 4.1 or 3.12)
NET.CFG (for 802.3 clients - generally NetWare 2.x and 3.11 servers):
LINK DRIVER E100BODI
FRAME ETHERNET_802.3
NET.CFG (for 802.2 clients - generally NetWare 3.12 and 4.1 servers):
LINK DRIVER E100BODI
FRAME ETHERNET_802.2
NETWARE DOS REQUESTER
FIRST NETWORK DRIVE = F
General Installation for NetWare 2.2/3.11/3.12 clients
------------------------------------------------------
All the files necessary to connect to the NetWare servers are supplied on
the Intel Configuration and Drivers disk. Newer versions of the shell
files (LSL.COM, IPXODI.COM, NETX.EXE) may be available from Novell on
CompuServe in the NetWire forum. To access this forum, type GO NOVFILES
and download the files NET33X.EXE and VLMUP2.EXE.
1 From the \DOS directory on the Intel Configuration and Driver disk,
copy the following files onto your hard drive: LSL.COM, E100BODI.COM,
IPXODI.COM, NETX.EXE, and NET.CFG.
2 Add the commands to your AUTOEXEC.BAT file as shown above under the
Sample Configuration Files section. Make sure you change to the
subdirectory where the drivers are loaded before executing the files.
In the example above, the drivers are located in the NWCLIENT
subdirectory.
3 Edit the NET.CFG file per your requirements.
If you don't know which frame type to load, type CONFIG from your file
server console to see which frame type your file server is loading and
load one of these frame types on the workstation.
If you list two or more frame types in the NET.CFG, the IPX protocol
will bind to the first frame type.
The NET.CFG file should be in the same directory as the adapter
driver.
If you're running EMM386, make sure you are using v4.49 or later. It's
the version that ships with DOS 6.22.
4 Reboot the computer and the drivers will load and connect you to the
network.
General Instructions for NetWare 4.1/3.12 client with VLMs
----------------------------------------------------------
The installation of the NetWare 4.1 client software is much easier than
earlier versions. The installation procedure transfers files to a
specific directory on the workstation and creates or modifies existing
configuration files to fit your specific needs. The installation utility,
INSTALL.EXE, is located on NetWare's "Workstation for DOS" disk. The
install program is also located in \PUBLIC\CLIENT\DOSWIN on the server.
NetWare 3.12 does not automatically create this directory on the server
during installation.
Installation Procedure for NetWare 4.1/3.12 client with VLMs
-------------------------------------------------------------
1 Run INSTALL.EXE from the NetWare Workstation for DOS Disk.
2 The NetWare Client Install program screen appears. You must complete
each of the options as they are specific to your needs.
Step #1: Specifies the directory on the hard drive that you want to
install the client software. The default directory is C:\NWCLIENT. You
can specify another directory if you desire.
Step #2: Gives you the option to automatically update the CONFIG.SYS
and the AUTOEXEC.BAT files or modify them at a later time manually.
Step #3: Installs Windows software for your system if your
workstation supports Windows and asks you to specify the directory
where Windows is located.
Step #4: Asks you to select a network driver and provide
configuration options. It uses the specifications you select to create
the file NET.CFG. Insert the Intel Configuration and Drivers disk when
prompted for the driver disk. Intel EtherExpress PRO/100B is the name
of the driver. Once you choose the driver, verify the configuration
settings for the board if necessary.
Step #5: The install program copies the appropriate files to your
hard drive. This is the final step.
3 Be sure to add LASTDRIVE=Z to your CONFIG.SYS file and FIRST NETWORK
DRIVE=F in the NET.CFG file under the Netware DOS Requestor section.
Hints and tips
=====================================================================
NET.CFG optional parameters
---------------------------
FORCEDUPLEX: Specifies the duplex mode the driver uses.
Syntax: FORCEDUPLEX n
Where n=0 (auto-negotiate)
1 (half duplex)
2 (full duplex)
NOTE: If adapter is set to half or full duplex, the SPEED parameter
must be set 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.
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
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.
If you don't have a auto-negotiating hub and are configuring the
adapter for full-duplex support, you must specify the speed
using this parameter.
If you use this parameter, the driver operates at the specified
speed instead of automatically detecting network speed.
Syntax: SPEED n (n = 10 or 100)
Default: none, the adapter automatically senses speed
SLOT: Specifies the slot number. This is optional for single adapter
installations, but required for multiple adapter installations.
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.
However, you can run the SETUP.EXE utility from the Intel
Configuration and Drivers diskette and view the adapter's slot
number (and device location in hex). Another 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).
THRESHOLD: Represents the threshold for transmits from extender SRAM
FIFO. By default threshold is dynamically set based on driver
activity. This parameter only sets a starting value. It will
still dynamically change.
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).
NODE ADDRESS: Specifies a local node address unique to each adapter. The
first four digits of the address indicate who assigned the
address when the driver loads.
The node address is also printed on a sticker on the back edge
of adapter. See the Installation Guide for a picture of the
adapter showing the location of the sticker.
Syntax: NODE ADDRESS 00aa12345678
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.2
PROTOCOL: Indicates the standard protocol in use.
Syntax: Protocol IPX E0 Ethernet_802.2
Values: E0=Ethernet_802.2
0=Ethernet_802.3
8137=Ethernet_II
8137=Ethernet_SNAP
NetWare DOS Requester
=====================
PB BUFFERS: A hexadecimal number representing number of packets in a
single transmit burst sequence used by VLM. The default is 16
(10h).
FIRST NETWORK DRIVE: (Used only with the VLM.EXE). Indicates the first
network drive available in the client system.
Note: If you use FIRST NETWORK DRIVE, the last line in the CONFIG.SYS
file must read: LASTDRIVE=Z
Detailed example
----------------
LINK DRIVER E100ODI
SLOT 1
SPEED 100
THRESHOLD 16
BUS 2
NODE ADDRESS 00aa00xxxxxx <--Last six digits are unique for each
adapter)
FRAME ETHERNET_802.2
PROTOCOL IPX E0 ETHERNET_802.2
In addition, the NET.CFG file can contain the following optional
information:
NETWARE DOS REQUESTER
PB BUFFERS=10
FIRST NETWORK DRIVE=F
* 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.