Location of Driver: \DOS\EPROODI.COM
Use the Auto Installation option in the SoftSet2 program. For
workstations that will use VLMs, see VLM Client section below.
Sample Configuration Files
NET.CFG (for 802.3 clients-generally NetWare 2.x and 3.11 servers)
NETX or VLM (VLM's for NetWare* 4.x or 3.12)
LINK DRIVER EPROODI
NET.CFG (for 802.2 clients - generally NetWare 3.12 and 4.x servers)
LINK DRIVER EPROODI
NETWARE DOS REQUESTER
FIRST NETWORK DRIVE = F
CONFIG.SYS (for NETX clients)
LASTDRIVE=E (For clients using NETX)
CONFIG.SYS (for VLM clients)
LASTDRIVE=Z (For clients using VLMs)
General Installation for NetWare* 2.2/3.11/3.12 client
General Installation for NetWare* 4.x/3.12 client with VLMs
- All the files necessary to connect to the NetWare* servers, are
supplied on Intel's driver 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 VLMUPx.EXE.
From the \DOS directory on the driver disk, copy LSL.COM, EPROODI.COM,
IPXODI.COM, NETX.EXE, NET.CFG.
If you are also running Windows for Workgroups, please see the Hints and
Tips section below for other important information.
- Add the commands to your AUTOEXEC.BAT file as shown above in 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
- Edit the NET.CFG file that you copied over. If you do not know which
frame type to load, type CONFIG from your file server console to see
which frame type your files server is using, 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. You may
also need to change the port number to the one your card is using.
See above for examples.
The NET.CFG file must be in the same directory as the EPROODI.COM file.
- Reboot the computer and the drivers will load and connect you to the
The installation of the NetWare 4.x client software is much easier than
earlier versions. The installation procedure will transfer files to a
specific directory on the workstation and create or modify existing
configuration files to fit your specific needs. The installation
utility INSTALL.EXE is located on NetWare's "Workstation for DOS" disk.
The INSTALL.EXE program is also installed on the 4.x server, so you
could run the SoftSet2 quick installation and connect with NETX to run
the install. The install program is located in \PUBLIC\CLIENT\DOSWIN
directory on the server. NetWare 3.12 does not automatically create
this directory on the server during installation.
6 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 Requester section.
Hints and Tips
- Run INSTALL.EXE from the Workstation for DOS Disk.
- The NetWare* Client Install program screen will appear. You must
complete each of the questions. These options are specific to your
- 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 will install Windows* software for your system if your
workstation supports Windows, and will ask you to specify the directory
in which Windows is located.
- d 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 EtherExpress PRO/10 adapter disk when prompted
for the driver disk. Intel® EtherExpress PRO/10 is the name of the
driver. Once you have chosen the driver, verify the configuration
settings for the board if necessary.
- Step #5 is the final step and the install program will copy the
appropriate files to your hard drive.
Start Windows for Workgroups and set up the driver for the
EtherExpress PRO/10 adapter by following the instructions shown in the
Windows for Workgroups installation document. When the driver is
chosen, Windows for Workgroups will detect the ODI driver is already
loaded and automatically install the appropriate support.
- NET.CFG Options:
PORT - This is the base I/O address of the adapter. Verify setting in
INT - <optional> The system IRQ for the adapter to use. This option is
only used as a reminder for which IRQ the board is set for. It does not
cause the driver to override the EEprom contents.
Node Address - <optional> This is the Ethernet node address for the
NODE ADDRESS 00AA00123456
00AA00123456 is the adapter's ethernet address . This is optional. If
it is not present, the driver will use the value in the EEprom on the
adapter. If it is present, the driver will use this value even if it
differs from the EEprom contents. This is Novell's node address
override feature. To comply with Novell's multicast
specification, the second digit of the overriding address should be a 2,
6, A or E.
- Windows for Workgroups
To install proper driver support for Windows for Workgroups and Novell
NetWare* on the same workstation, follow these steps:
- Set up the workstation with the DOS ODI client driver as shown above.
- Load the ODI driver and login to your NetWare server.
Plug and Play (PnP) error message when loading the driver
The PRO/10 adapter is a Plug and Play adapter, and if the adapter
detects a Plug and Play BIOS in your computer, it will rely on that BIOS
to configure it. Various BIOS setup configurations can cause the
adapter not to be configured. Follow the suggestions listed in the
message to fix the problem. Since BIOS differ in options, some BIOS may
not allow you to adjust all the listed selections.
Your computer's Plug and Play BIOS couldn't configure your EtherExpress
PRO/10 LAN Adapter. The probable cause is that your computer's BIOS
isn't properly configured for this Plug and Play adapter. To keep the
Plug and Play feature on the adapter, check the following:
- Make sure your computer's BIOS has enough Interrupts (IRQs)
designated for Plug and Play devices.
- Check your computer's BIOS for a Plug and Play Activation level.
Make sure it is set to configure Plug and Play devices.
- Your computer may require a Plug and Play Configuration Manager.
Check with your computer vendor for details.
- * Disable Plug and Play on this adapter by running SoftSet2.
This applies to: