Ref: 08720031
Title: Configuring Two EtherLink16 Adapters in One LAN Manager Machine
Date: 3/11/91

Copyright 3Com Corporation, 1991.  All rights reserved.

Two EtherLink16 adapters can be installed into one LAN Manager
machine.  However, current versions of the NDIS drivers for the EtherLink16
(at the time of this writing, the current version was 1.1(c), dated 1/08/91
10:58am) do not follow the standard conventions for the value of the
DRIVERNAME= statement in the PROTOCOL.INI file.

The standard convention for the second and any subsequent instances of an
NDIS driver is to use the base part of the filename, with an x (where x is
2 if this is the second instance of the driver, 3 if this is the third
instance of this driver, etc.) appended to the end of the base name,
followed by a $ symbol.

For example, the first instance of the NBP protocol driver would use the
drivername NBP$ (the file name of the driver is NBP.OS2, the base name is
NBP) and the second instance of the NBP driver would use a drivername of
NBP2$.  The third instance would be NBP3$.

The EtherLink16 adapter driver did not follow this convention.  The second
instance of this adapter driver will take the name ELNK16X$.  Because of
this, you may not install a third or fourth EtherLink16 in the same PC with
the current NDIS drivers for this adapter.

Future releases of the NDIS adapter drivers for this adapter will correct
this mistake; the second instance will correctly use the drivername ELNK162$,
the third instance will correctly use the drivername ELNK163$, etc.

The procedure for physically installing and configuring two EtherLink16
adapters in one machine is fairly straightforward.

Install one EtherLink16 at a time into the target machine and run the
Diagnostic/Configuration program 3C507.EXE on each.  Remember to boot the
machine with a "vanilla" DOS diskette with no network drivers or memory
managers present.  The interrupt, I/O base address, and shared memory RAM
base address must be unique to each EtherLink16, and must not conflict with
other devices or software such as memory managers.  If remote boot PROMs are
used, the ROM base address for each adapter must also be unique to that
adapter and must not conflict with other devices or software.

The adapter with the lowest I/O base address will be the "first" EtherLink16.

After each adapter has been configured seperately, reinstall both of them in
the target machine, and install the network operating system software.

If you are using 3Com's 3+Open 1.1 LAN Manager, the NETSETUP program will
only install one network adapter.  Select the 3Com EtherLink16 (3C507)
adapter.  Select the transport protocol(s) of your choice.

Once NETSETUP is complete, you must manually edit some files:

1.  Edit CONFIG.SYS to create a duplicate statement immediately following
the statement defining the EtherLink16 device driver.

In a server, this is the DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\ELNK16.OS2
statement.  In an OS/2 workstation, this is the
DEVICE=C:\3OPEN\OS2WKSTA\LANMAN\DRIVERS\ELNK16.OS2 statement.  If
the target machine is a LAN Manager server, this area of CONFIG.SYS
should now look like:

  DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\PROTMAN.OS2  (continued below)
     /I:C:\3OPEN\SERVER\LANMAN\DRIVERS
  DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\ELNK16.OS2
  DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\ELNK16.OS2
  DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\XNSNB.OS2
  DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\LGL.OS2 -m50


2.  Edit PROTOCOL.INI to duplicate the section identified by [ETHERLINK16].
Then edit the section name for the newly created copy, making it unique.
(Note:  if you use a numeric character as the first character of this
section name, you will have to enclose it in quotes when referring to it
within a BINDINGS= statement later on.)   Also, edit the DRIVERNAME=
statement at this time, making the name ELNK16X$.  The two sections should
now look something like this:

   [ETHERLINK16]
     DRIVERNAME=ELNK16$

   [ETHERLINK16_2]
     DRIVERNAME=ELNK16X$


3.  Bind the two adapters to the protocol(s).

If you are using a single transport protocol that supports internal routing
(such as 3Com's XNS and TCP/IP), you can bind both adapters to one instance
of this protocol.  Some protocols, such as 3Com's NBP and Microsoft's NETBEUI,
do not support internal routing.  If you want both adapters to be bound to
the same protocol, you must load two instances of that protocol.

Please review Appendix C of the 3+Open Technical Reference Manual or
your network operating system documentation for information regarding
binding protocols to adapters and using multiple protocols.


