1. IEE_10.ZIP Driver
2. NW311.TXT File Contents

NW311.TXT Driver File Contents (IEE_10.ZIP)

   Server Driver for NetWare 3.11
                                                                       v3.04


NetWare* 3.11 Server Driver Installation Notes for Intel's EtherExpress(TM)
PRO/10 ISA LAN Adapter
===========================================================================

Location of Driver: \NWSERVER\311LAN\EPROLAN.EXE (self-extracting archive
                    containing ODI 3.2 Assembly Specification drivers)


Sample Load Commands
--------------------
   
   LOAD C:\EPRO311 PORT=xxx FRAME=ETHERNET_802.3
   BIND IPX TO EPRO311 NET=xxxxxxxx


Overview
--------

NetWare 3.11 requires an ODI 3.2 Assembly Specification driver.  This driver
is in a self-extracting archive named EPROLAN.EXE contained on the
\NWSERVER\311LAN\ directory of the Configuration and Drivers disk.  To
unpack the archive copy it to a blank floppy disk or other disk that has at
least 100K bytes of free disk space and type EPROLAN on the DOS command
line.  The archive contains the following files:

    EPRO.LAN      (3.2 Specification server driver for NetWare 3.12/4.10)
    EPRO.LDI      (Installation file)
    EPRO311.LAN   (3.2 Specification server driver for NetWare 3.11 ONLY)
    NW311.TXT     (This file)


General Installations
---------------------

If you have a Plug and Play BIOS, make sure you DISABLE Plug and Play on
your adapter using SoftSet2 (Advanced Options menu). NetWare servers don't
support Plug and Play (they don't support a Configuration Manager). As a
result, NetWare servers may not be able to find your adapter if Plug and
Play is enabled.

1  Install NetWare 3.11 according to the NetWare 3.11 installation manual.

2  Copy the EPRO311.LAN server driver that you unpacked from the archive and
   any updated NLMs, to the NetWare server's hard drive.

   If you can't log in to the server, then before starting the server, copy
   the EPRO311.LAN driver to the root directory of the server's hard drive.

   If you can log into the server, copy the files 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.

3  Bring up the server, and at the server console issue the load and bind
   statement(s) as required.  See the example above and substitute "xxx"
   with valid parameters for that adapter.  PORT= refers to the I/O port
   address and NET= is the unique address for that LAN network segment.  If
   you have workstations using the 802.2 frame type, see below for using
   multiple frame types on one adapter.

4  Add the load and bind statements you require to the server's AUTOEXEC.NCF
   file so the EtherExpress(TM) PRO/10 ISA adapter driver will load
   automatically each time the server starts up.


Hints and Tips
--------------

1. Installing multiple EtherExpress PRO/10 ISA LAN adapters:

   If you have multiple LAN adapters in a single server, each adapter must
   have a different network number and a different port number. You may also
   want to name each adapter for ease of management. For example
   
   LOAD C:\EPRO PORT=300 NAME=LAN_A
   BIND IPX TO LAN_A NET=222
   LOAD C:\EPRO PORT=320 NAME=LAN_B
   BIND IPX TO LAN_B NET=333

2  Installing one EtherExpress PRO/10 ISA 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 will use the same
   port number but a different network number is required on the bind
   statement.  You need to supply a name on each load line in order to avoid
   being prompted for which board to bind IPX to.

   If you do not have the name option in the AUTOEXEC.NCF, it will not
   execute completely without user intervention.
   
   Example:
   
   LOAD C:\EPRO PORT=300 FRAME=ETHERNET_802.3 NAME=LAN8023
   BIND IPX TO LAN8023 NET=77777
   LOAD C:\EPRO PORT=300 FRAME=ETHERNET_802.2 NAME=LAN8022
   BIND IPX TO LAN8022 NET=88888



*  Third-party trademarks are the property of their respective owners.