LAN Manager* Workstation/Server v3.05

LAN Manager 2.2 Workstation/Server Installation Notes for Intel's EtherExpress™ PRO/10 LAN Adapter

Location of Driver: \NDIS\MSLANMAN.BAT

MSLANMAN.BAT will create the following directory structure on local hard drive:

\MSLANMAN.DOS\DRIVERS\ETHERNET\EPRO\EPRO.DOS (DOS NDIS driver) \MSLANMAN.DOS\DRIVERS\ETHERNET\EPRO\PROTOCOL.INI \MSLANMAN.DOS\DRIVERS\NIF\EPRODOS.NIF \MSLANMAN.OS2\DRIVERS\ETHERNET\EPRO\EPRO.OS2 (OS/2 NDIS driver) \MSLANMAN.OS2\DRIVERS\ETHERNET\EPRO\PROTOCOL.INI \MSLANMAN.OS2\DRIVERS\NIF\EPROOS2.NIF

DEVICE=C:\LANMAN\PROTMAN.DOS /I:C:\LANMAN DEVICE=C:\LANMAN\EPRO.DOS

DEVICE=C:\LANMAN\PROTMAN.OS2 /I:C:\LANMAN DEVICE=C:\LANMAN\EPRO.OS2

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™ PRO/10 adapter driver isn't included on the LAN Manager disk) and insert the disk you created with the PRO/10 drivers, select the EtherExpress™ PRO/10 adapter driver and follow the directions.
   
   
2. When completed, reboot your computer for changes to take effect.

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=EPROx$, 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.
   
   If you want information on advanced PROTOCOL.INI parameters, refer to the NDIS Driver Notes document or obtain document 6341 on Intel's automated services.
   
   
2. If you are having problems authenticating to a LAN Manager server, use SoftSet2 to check if the PRO/10 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 = EPRO_NIF
   LANABASE = 0
   
   
   [EPRO_NIF]
   ; PROTOCOL.INI section for the Intel® EtherExpress™ PRO/10
   ; Adapter
   
   
   IOADDRESS = 0x300
   DRIVERNAME = EPRO$
   

This applies to:

EtherExpress™ PRO/10 and PRO/10+ ISA adapters