2 Server: NetWare 4.x server
                                                                    v1.03
      
      
      NetWare 4.x server driver installation notes for Intel's
      EtherExpress(TM) PRO/10 PCI LAN adapters
      =========================================================
      
      Location of driver:   \NWSERVER\E10P.LAN
      
      Location of NLMs:   Novell's automated services.
         
         MSM.NLM        (11-23-94 v2.50, or later)
         ETHERTSM.NLM   (11-29-94 v2.50, or later)
      
      
      Sample load commands
      --------------------
         
         LOAD C:<PATH>\E10P SLOT=n FRAME=ETHERNET_802.2
         BIND IPX TO E10P NET=xxxxxxxx
      
      
      General instructions
      --------------------
      
      1  If you are performing a new installation of NetWare 4.x, follow
         NetWare's instructions.  During the installation of 4.x, you
         will be prompted for the LAN driver.  At that time insert the
         LAN adapter driver disk and complete the information NetWare 4.x
         requires. The NetWare 4.x installation program will
         automatically add these statements to your AUTOEXEC.NCF file.
      
      2  We recommend you update the version of the following two NLMs to
         version 2.50 or later. Earlier versions may not work properly.
         These files can be obtained from Novell's online services.
              
              MSM.NLM       (11-23-94 v2.50)
              ETHERTSM.NLM  (11-29-94 v2.50)
      
         If you can log into the server, rename the existing copy of
         these files in the SYSTEM subdirectory, and copy the updates
         into the SYSTEM subdirectory.  If the adapter is the only one in
         the server, manually load these NLMs in the order listed above,
         specifying the c:\<path> to where they are located.
      
      3  Before starting the server, copy the E10P.LAN driver from the
         \NWSERVER directory on the Intel EtherExpress PRO/10 PCI disk to
         the root directory of the hard drive of the server.
      
         If you can log in to 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.
      
      4  Start the server. At the server console, issue the load and bind
         statement(s) in this order:
              
              LOAD C:<PATH>\E10P SLOT=n FRAME=ETHERNET_802.2
              BIND IPX TO E10P NET=xxxxxxxx
         
         Note: If MSM and ETHERTSM NLM's aren't loaded, they'll
               automatically load before the driver.
      
         Where:
      
         SLOT=n specifies the PCI device number.  Substitute n with the
         valid value for the adapter.
      
         NET=xxxxxxxx is the unique network address for that LAN segment.
      
         If you have workstations using the 802.3 frame type, see the
         section later in this document about using multiple frame types
         on one adapter.
      
      5  Add the load and bind statements you need to the server's
         AUTOEXEC.NCF file so the EtherExpress(TM) PRO/10 PCI LAN adapter
         driver loads automatically each time the server starts.
      
      
      Hints and tips
      --------------
      
      1  Installing multiple adapters
      
         If you have multiple adapters in a single server, each adapter
         must have a different network number and SLOT number. Also, you
         may want to name each adapter. For example:
              
              LOAD C:\E10P SLOT=3 NAME=LAN_A
              BIND IPX TO LAN_A NET=222
              LOAD C:\E10P SLOT=4 NAME=LAN_B
              BIND IPX TO LAN_B NET=333
      
         In an IPX internal router configuration (a server with two
         adapters, each connected to a different network), the data
         transfer rate across the router can be low.  This happens if
         client workstations have CPU speeds equal to or higher than the
         server. You may be able to increase the data transfer rate by
         adding the following to STARTUP.NCF:
              
              SET MAXIMUM INTERRUPT EVENTS = 100000
      
         The default setting is 10.
      
         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/10 PCI 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.
      
      2  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.
         For example:
         
         LOAD C:\E10P SLOT=3 FRAME=ETHERNET_802.3 NAME=LAN8023
         BIND IPX TO LAN8023 NET=77777
         LOAD C:\E10P SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
         BIND IPX TO LAN8022 NET=88888
      
      3  Specifying the connector type when using Novell's SFTIII
      
         If you're using Novell's SFTIII on an EtherExpress PRO/10 PCI
         LAN adapter that has three connectors, you must specify the
         connector type either on the command line or in your IOAUTO.NCF
         file.
      
         By default, CONNECTOR=AUTO.  Change the value to AUI, BNC or
         TPE.  For example:
         
         LOAD C:\E10P.LAN SLOT=3 CONNECTOR=TPE
      
      4  Optional LOAD line parameters
      
      SLOT:       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. One 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)
      
      NODE:       Specifies a local administered address (LAA) unique to
                  each adapter. Use this option to provide your own
                  unique node address for the adapter.  Setting this
                  parameter overrides the default factory setting. 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=02aa12345678
      
      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
      
      FIFO:       Defines the FIFO threshold for requesting bus access.
                  For computers with high bus latency, you can increase
                  this setting. For computers with very low latency, you
                  can reduce this setting.
      
                  For best performance, set as low as possible without
                  causing DMA over/underruns.
      
                  Syntax: FIFO=n  (n = 2,3,4,...).
      
                  Default: FIFO=8
      
      CONNECTOR:  If the Connector parameter is set to Auto Detect, the
                  adapter attempts to detect which connector type is
                  active. If it doesn't find activity on any of the
                  connectors, it defaults to AUI.
      
                  If Connector is set to anything other than Auto Detect,
                  it forces the adapter to use the specified connector
                  type.
      
                  Syntax:  CONNECTOR=n  (n = AUTO, AUI, BNC, TPE)
      
                  Default: CONNECTOR=AUTO
      
      
      *  Third-party trademarks are the property of their respective
         owners