LAN Manager Workstation/Server
                                                                    v1.00


LAN Manager* 2.2 Workstation/Server Installation Notes for Intel's
EtherExpress(TM) 10 ISA LAN Adapter
==================================================================

Location of Driver: \NDIS\MSLANMAN.BAT


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


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

CONFIG.SYS (for DOS will contain):
   DEVICE=C:\LANMAN\PROTMAN.DOS /I:C:\LANMAN
   DEVICE=C:\LANMAN\EX10.DOS

CONFIG.SYS (for OS/2* will contain):
   DEVICE=C:\LANMAN\PROTMAN.OS2 /I:C:\LANMAN
   DEVICE=C:\LANMAN\EX10.OS2


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

1  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(TM) 10 ISA
   adapter driver isn't included on the LAN Manager disk) and insert the
   disk you created with the 10 ISA drivers, select the EtherExpress 10
   ISA adapter driver and follow the directions.

2  When completed, reboot your computer 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 example below.  If you are installing multiple adapters, each
   adapter must have a unique driver name.  Additional instances of the
   driver would be referenced by DRIVERNAME=EX10x$, where "x" would be a
   unique number 2 through 9.
   
   IOADDRESS: (optional for single adapter systems - except when set to
   certain addresses noted below) This value must match the adapter's I/O
   address.  If the driver does not find the adapter at the specified I/O
   address, it will scan most of the I/O addresses that the adapter could
   be at and will load if it finds the adapter.  The only addresses the
   driver doesn't scan are 2E0, 2F0 or 370. If you have used one of these
   address, this parameter isn't optional. If you use multiple adapters
   in one machine, make sure you specify the correct IOADDRESS for each
   board.  Otherwise, the driver will fail when loading on the second
   card.
   
   NODE: (optional) (Syntax: NODE="12 Hexadecimal digits") This value
   sets the adapter's Individual Address, overriding the value read from
   the adapter's EEprom.  The value must be exactly 12 hexadecimal
   digits, enclosed in double quotes.  The value can't be all zeros, nor
   can it be a multicast address.

2  If you are having problems authenticating to a LAN Manager server, use
   EX10Set to check if the 10 ISA is set to 8-bit mode. If it is, go to
   Change Adapter Configuration, Advanced Options Menu and disable
   Concurrent Processing.

3  Sample PROTOCOL.INI for LAN Manager
   
   [PROTMAN]
   DRIVERNAME = PROTMAN$
   DYNAMIC = YES
   PRIORITY = NETBEUI
   
   [NETBEUI_XIF]
   Drivername = netbeui$
   SESSIONS = 6
   NCBS = 12
   BINDINGS = EX10_NIF
   LANABASE = 0
   
   [EX10_NIF]
   ; PROTOCOL.INI section for the Intel EtherExpress(TM) 10 ISA
   ; Adapter
   
   IOADDRESS = 0x300
   DRIVERNAME = EX10$



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