1. es199.exe Driver
2. MSLANMGR.TXT File Contents

MSLANMGR.TXT Driver File Contents (es199.exe)

   5 LAN Manager Workstation/Server
                                                                    v1.05


LAN Manager* 2.2 Workstation/Server installation notes for Intel's
EtherExpress(TM) PRO/10+ PCI LAN Adapter
==================================================================

Location of Driver: \NDIS\MSLANMAN.BAT

MSLANMAN.BAT will create the following directory structure on a local
hard drive:
   
   \MSLANMAN.DOS\DRIVERS\ETHERNET\E100B\E100B.DOS (DOS NDIS driver)
   \MSLANMAN.DOS\DRIVERS\ETHERNET\E100B\PROTOCOL.INI
   \MSLANMAN.DOS\DRIVERS\NIF\E100B.NIF
   
   \MSLANMAN.OS2\DRIVERS\ETHERNET\E100B\E100B.OS2 (OS/2 NDIS driver)
   \MSLANMAN.OS2\DRIVERS\ETHERNET\E100B\PROTOCOL.INI
   \MSLANMAN.OS2\DRIVERS\NIF\E100B.NIF


Sample Configuration Files
--------------------------

CONFIG.SYS (for DOS) will include these lines:
   
   DEVICE=C:\LANMAN\PROTMAN.DOS /I:C:\LANMAN
   DEVICE=C:\LANMAN\E100B.DOS

CONFIG.SYS (for OS/2) will include these lines:
   
   DEVICE=C:\LANMAN\PROTMAN /I:C:\LANMAN
   DEVICE=C:\LANMAN\E100B.OS2

PROTOCOL.INI will contain these lines:
   
   [E100B_NIF]
   ; PROTOCOL.INI section for Intel EtherExpress PRO/10+ PCI adapter
   
   DRIVERNAME = E100B$


General Installation
--------------------

1  Create the directory structure needed for the LAN Manager installation
   by running the batch file MSLANMAN.BAT.  It will create the
   directories at the root of the specified drive and copy the necessary
   files.

2  Run the appropriate Microsoft LAN Manager setup for the computer you
   are setting up (DOS, OS/2 or OS/2 Server). When prompted for the LAN
   adapter driver, select "Other Driver" (the EtherExpress PRO/10+ PCI
   adapter driver isn't included on the LAN Manager disk) and specify the
   drive from step 1. Select the EtherExpress PRO/10+ PCI adapter driver
   and follow the directions.

3  When completed, reboot your computer in order for changes to take
   effect.


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

1  Parameters for the PROTOCOL.INI file:
   
   DRIVERNAME: (required) If you have a single adapter, use the syntax in
      the Sample Configuration file section.  If you are installing
      multiple adapters, each adapter must have a unique driver name.
      Additional instances of the driver would be referenced by
      DRIVERNAME=E100Bx$, where "x" would be a unique number 2 through 9.
   
   FORCEDUPLEX: (required if connecting to full duplex hub) This
      parameter enables the adapter to work with a full duplex hub.
      Options are 1 (for half), 2 (for full). If not specified, the
      adapter will operate at half duplex. [Example: FORCEDUPLEX = 2]
   
   SLOT: (required for multiple adapters) This parameter is optional if
      only one adapter is present.  If it is specified but is incorrect,
      a message indicates that the value doesn't match the configuration
      but the driver will find the adapter and load anyway.
   
      This parameter becomes required if more than one adapter is present
      in either one bus or multiple PCI buses of a system. The value of
      this parameter makes it possible for the driver to uniquely
      identify which of the adapters is to be controlled by this driver.
      The SLOT number is the encoded value of the PCI adapter's device
      location. To determine the slot number, load the driver with only
      the DRIVERNAME parameter specified.  The driver will report all the
      slots which have PCI adapter(s) installed. You can determine which
      card is in which slot by using SETUP.EXE and matching the Ethernet
      addresses of the adapter to the device number specified in View
      Configuration. [Example: SLOT=0x1C]
   
   NODE: (optional) This value sets the adapter's Individual Address,
      overriding the value read from the adapter EEprom. The address must
      consist of 12 hexadecimal digits, enclosed in double quotes.  The
      value can not be all zeros. The value can not have the Multicast
      bit set. So, use only the hexadecimal digits 2, 6, A, or E as the
      second digit of the twelve required in the NODE ADDRESS parameter.
      Use any other numbers you prefer in all other positions.
      [Example: NODE = "02AA00123456"]

2  Sample PROTOCOL.INI for LAN Manager:
   
   [PROTMAN]
   DRIVERNAME = PROTMAN$
   DYNAMIC = YES
   PRIORITY = NETBEUI
   
   [NETBEUI_XIF]
   Drivername = netbeui$
   SESSIONS = 6
   NCBS = 12
   BINDINGS = "E100B_NIF"
   LANABASE = 0
   
   [E100B_NIF]
   ; PROTOCOL.INI section for the Intel EtherExpress PRO/10+ PCI adapter
   DRIVERNAME = E100B$



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