
    Microsoft OS/2 LAN Manager Driver Installation
==========================================================

The drivers contained in the directory MSLANMAN.DOS,
MSLANMAN.OS2 are for NE2000 Compatible Ethernet adapters.

They are used with 3Com 3+Open, Microsoft OS/2 LAN
Manager OEM distribution, Release 1.x or 2.x, and
other compatible OEM versions of LAN Manager. The
drivers named ETHNE conform to the Network Driver
Interface Specification (NDIS) defined by Microsoft.

Included in MSLANMAN.DOS and MSLANMAN.OS2 subdirectories
are the following files:

\MSLANMAN.DOS\DRIVERS\ETHNE\ACCNE\
  ETHNE.DOS		The DOS NDIS MAC driver
  PROTOCOL.INI		A sample section of PROTOCOL.INI file

 \MSLANMAN.DOS\DRIVERS\NIF\
  ACCNE.NIF		Network Information File

\MSLANMAN.OS2\DRIVERS\ETHNE\ACCTNE\
  ETHNE.OS2		The First OS/2 NDIS MAC driver
  PROTOCOL.INI		A sample section of PROTOCOL.INI file

\MSLANMAN.OS2\DRIVERS\NIF\
 ACCNE.NIF		Network Information File

\NDIS
 EN1657O.NIF		Network Information File for LAN Server (OS/2)
 EN1657D.NIF		Network Information File for LAN Server (DOS)
 README.TXT		This file
 OEMSETUP.INF		Network Information File for Windows for Workgroup

Initial Installation
====================
1. Install the adapter into the host PC.
2. Run diagnostics to test for proper installation. Run SETUP.EXE
   and choose the TEST THE ADAPTER option to run diagnostics.

Note
----
The SETUP program will not run proper from the OS/2 compatibility
box.

Driver Installation on Microsoft LAN Manager v2.1
=================================================

1. Use SETUP utility provided by LAN Manager to install
   the NDIS driver. Choose  the "Configuration," "Network drivers...",
   <Add New Config>, <Other Driver> options sequentially
   and insert this diskette into your floppy drive.and
   Then configure your system using the driver ETHNE.DOS
   (or ETHNE.OS2).

2. Modify the PROTOCOL.INI file if you are not using
   the default adapter settings.

3. After completing the setup operation, the CONFIG.SYS file
   should contain the NDIS driver.

4. Reboot your computer and follow the NDIS binding
   procedure to use the NDIS driver.


Driver Installation on Microsoft LAN Manager v2.0
=================================================

1. Use SETUP utility provided by LAN Manager to install
   the NDIS driver. Choose  the "Import Network drivers"
   option and insert this diskette into your floppy drive.
   Then configure your system using the driver ETHNE.DOS
   (or ETHNE.OS2).

2. Modify PROTOCOL.INI file if you are not using the
   default adapter settings.

3. After completing the setup operation, the CONFIG.SYS
   file should contain the NDIS driver.

4. Reboot your computer and follow the NDIS binding
   procedure to use the NDIS driver.


Sample PROTOCOL.INI File and Parameters
=======================================

[ACCNE_NIF]
;  Default section of protocol.ini file for the NE2000 compatible Adapter
    drivername = ETHNE$
    irq = 3
    iobase = 0x300
; End of this sample file

Several parameters are included in the ACCNE_NIF section of the
PROTOCOL.INI file.  However, the only parameter that must
be specified is the "drivername."  The other parameters use the
values detected by the driver.

irq	     Specifies the interrupt channel used by the adapter.
	     Acceptable values for this parameter are 2, 3, 4, 5, 10,
	     11, 12, and 15.



iobase	     Specifies the iobase address used by the adapter.
	     This parameter is given in hexadecimal values.
	     Acceptable value for this parameter are 0x200,0x220,
	     0x240, 0x260, 0x300, 0x320, 0x340, 0x360.


Additional Parameters in the PROTOCOL.INI File
for in the NDIS Driver Configuration
===============================================

--------------------------------------------------------------
Keyword 	Parameter
---------------------------------------------------------------
MaxMultiCast	1 .. 1000  Default 10
		Maximum number of MultiCast Addresses.
		This configures the size of the MultiCast
		Address Table.

MaxRequests	6 .. 64  Default 8
		Maximum number of outstanding GeneralRequests.
		This configures the size of the GeneralRequest
		Queue.

MaxTransmits	6 .. 64  Default 12
		Maximum number of outstanding TransmitChain commands.
		This configures the size of the TransmitChain Request
		Queue.

ReceiveChains	6 .. 96  Default 12
		Maximum number of outstanding ReceiveChain commands.
		This configures the size of the ReceiveChain Request
		Queue.

ReceiveBuffers	6 .. 96  Default 12
		Configures the number of the Receive buffers in the
		Receive Buffer Pool.

TransmitBufSize 128 .. 1514  Default 1514
		Configures the size (in bytes) of buffers in the
		Transmit Buffer Pool.

ReceiveBufSize	128 .. 1536  Default 256
		Configures the size (in bytes) of buffers in the
		Receive Buffer Pool.
------------------------------------------------------------------
Note
----
Values for the preceding parameters are seldom changed by
the user.  Most of the time, the default values are used.


Troubleshooting and Error Messages
==================================

Run SETUP's AUTO CONFIGURE option to immediately detect
adapter setting conflicts.


Error Message:
ERROR: Adapter card not found or IO port error.

Possible Causes:
1. The adapter is not properly installed in the computer's slot,
   or there is no adapter installed.
2. I/O port failure causing the adapter to fail.
3. The IO Base setting in the PROTOCOL.INI file does not
   match that adapter's hardware setting.

Solution:
1. Run SETUP's TEST THE ADAPTER option to find out the reason
   for the problem.


TRADEMARKS
==========
All trademarks or brand names mentioned are properties of
their respective companies.

===End===

