# Intel Network Drivers for DOS

## DOS Driver

The NDIS2 (DOS) driver is provided solely for the purpose of loading other operating systems such as during RIS or unattended installations. It is not intended as a high-performance driver.

You can find adapter drivers, protocol.ini files, and net.cfg files in the DOS directory on the Intel CD. For additional unattended install information, see the readme files in the Windows\PUSH directory.

## DOS ODI Client Driver

This driver is provided solely for the purpose of loading an OS. It is not intended as a high-performance driver. Please limit use to 1-2 frame types.

Location of Drivers:
10/100 Mbit: \DOS\E100BODI.COM
Gigabit: \DOS\E1000ODI.COM (This directory also contains the protocol.ini file and net.cfg file for gigabit adapters.)

| NOTE: If connection fails, set the Spanning Tree Protocol (STP) option on the switch to "off".
| NOTE: Novell no longer supports NETX.EXE or the VLM client software. However, as a convenience to Intel customers, a copy of NETX.EXE is provided on the Intel Configuration and Drivers CD. Intel recommends that you use the latest Novell Client32 software.
| NOTE: With dual-port adapters, the first port must be used before the second port.

### NETX General Installation

1. Copy the following files from the \DOS directory of the Intel media to the hard drive (NWCLIENT):

   - LSL.COM

   - E100BODI.COM (10/100 Mbit) or E1000ODI.COM (gigabit)

   - IPXODI.COM

   - NETX.EXE

2. Configure AUTOEXEC.BAT and NET.CFG based on the sample files below. NET.CFG should be in the same directory as the driver.

3. Reboot, and the client should connect to the server.

### VLM General Installation

The driver requires VLM client version 1.21.

1. Run install.exe on the workstation you are configuring.
   For the client version of IntranetWare 4.11, you can find Install.exe on the IntranetWare CD at:

> - \PRODUCTS\VLM\IBM_6\INSTALL.EXE

> - \PRODUCTS\VLMIP\IBM_6\INSTALL.EXE (the TCP/IP client)

> For the server version of IntranetWare 4.11, you can find Install.exe on the IntranetWare CD at:

> - \PUBLIC\CLIENT\DOSWIN
>   This option is not available on NetWare 3.12

> For 4.1 / 3.12 clients, you can find Install.exe on the NetWare Workstation for DOS disk. It must be version 1.21 or greater (supplied with IntranetWare 4.11). To ensure you are using the correct version, right-click Install.exe and then click Properties. Version information appears on the NetWare Version tab.

2. Follow the screen prompts including the following options:

   Prompt | Action
   Locate the directory on the hard drive for the client software | Default: C:\NWCLIENT You can specify another directory.
   Automatically update CONFIG.SYS and AUTOEXEC.BAT files? | Type Y or N
   If you are loading Windows, specify the directory where you would like to load Windows. | User defined
   Configure workstation for back-up by a NetWare server. | User defined

3. Select a network driver and set configuration options. Do NOT select a Driver from the list Novell provides; rather, choose OTHER DRIVER and insert the Intel adapter disk.

4. Select the Intel Adapter.

5. Optionally set:

   - Frame Type

   - Adapter Node Address

   - Force Duplex Mode

   - Line Speed

6. Install copies of the appropriate files to your hard drive and set NET.CFG. This is the final step.

| NOTE: Because some switches link slower than others, you may have to allow more time before running VLM. If you run vlm and don't get a valid connection, run vlm -u and then try running vlm again.

### TIPS (DOS ODI)

#### NETX

- In CONFIG.SYS add LASTDRIVE=E.

- In NET.CFG add FIRST NETWORK DRIVE F (or some drive letter after the range of physical devices you've installed) under the NetWare DOS REQUESTER section (indented).

#### VLM

- In CONFIG.SYS add LASTDRIVE=Z.

- In NET.CFG, add FIRST NETWORK DRIVE F under the NetWare DOS REQUESTER section (indented). If F is already assigned, select a drive letter after the range of physical devices you have installed.

- Promiscuous mode support is not supported since ASM does not include a receive monitor stack. If needed, load RXMONSTK.COM (from the VLM client kit) after LSL.COM and before E100BODI.COM or E1000ODI.COM.

- This version of E100BODI.COM or E1000ODI.COM requires VLM client version 1.21 or higher. Attempting to use an older version of the VLM client may cause connection problems, slow response or computer system lock-ups.

### 10/100 Mbit Sample Files

AUTOEXEC.BAT:

>     CD\NWCLIENT
>     LSL
>     E100BODI
>     IPXODI
>     NETX (or VLM optional for NetWare 3.12 or higher)

NET.CFG:

>     LINK DRIVER E100BODI
>     FRAME ETHERNET_802.2 (generally NetWare 3.12 and later servers)
>     ;FRAME ETHERNET_802.3 (generally NetWare 3.11 and earlier)
>     SPEED=100
>     PROTOCOL IPX EO Ethernet_802.2

>     NETWARE DOS REQUESTER
>     FIRST NETWORK DRIVE = F (Used only with the VLM.EXE).
>     PB BUFFERS = 10

### Gigabit Sample Files

AUTOEXEC.BAT:

>     CD\NWCLIENT
>     LSL
>     E1000ODI
>     IPXODI
>     NETX (or VLM optional for NetWare 3.12 or higher)

NET.CFG:

>     LINK DRIVER E1000ODI
>     FRAME ETHERNET_802.2 (generally NetWare 3.12 and later servers)
>     ;FRAME ETHERNET_802.3 (generally NetWare 3.11 and earlier)
>     SPEEDUPLEX = 3
>     PROTOCOL IPX EO Ethernet_802.2

>     NETWARE DOS REQUESTER
>     FIRST NETWORK DRIVE = F (Used only with the VLM.EXE).
>     PB BUFFERS = 10

> NOTE: SPEEDUPLEX parameter: 0=10Mbps half-duplex; 1=10Mbps full-duplex; 2=100Mbps half-duplex; 3=100Mbps full-duplex. The SPEEDUPLEX keyword is only needed when you are forcing the card to a lower speed and duplex. The link partner must also be forced to the same setting.

`Last modified on 10/01/02 3:40p Revision 6`