This document applies to the EtherExpress 16, 16TP, 16C, FLASH,
FLASH TP, FLASHC, MCA, and MCA/TP adapters. This information is based
on a customer report.
You can use either the LANSUP (NDIS based) or ODINSUP (ODI based) to
connect the EtherExpress 16 simultaneously to an IBM AS400 and Novell
server. Some customers have reported that LANSUP is slower. ODINSUP is
included in the DOSUPx.ZIP (where x is the number of the latest
offering) file on NetWire/Compuserve.
Here are the configuration files when using LANSUP (NDIS based)
CONFIG.SYS should include:
DEVICE = \LANMAN\PROTMAN.DOS
DEVICE = EXP16.DOS <--- NDIS driver
DEVICE = \AS400\DXMA0MOD.SYS <--- 1.35 or later
DEVICE = \AS400\DXME0MOD.SYS <--- 1.35 or later
DEVICE = C:\PCS\EIMPCS.SYS
DEVICE = C:\PCS\ECYDDX.SYS
AUTOEXEC.BAT should include:
\AS400\NETBIND
LSL
LANSUP <-- Must be 4/10/91 or newer, located on wsgen disk
IPXODI
NETX
C:\PCS\STARTPCS
PROTOCOL.INI should include:
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[ETHERNET]
DRIVERNAME = DXME0$
BINDINGS = EXP16
[EXP16]
DRIVERNAME = EXP16$
IOADDRESS = 0x300
Here are the configuration files using ODINSUP (ODI based)
CONFIG.SYS should include:
DEVICE = \LANMAN\PROTMAN.DOS
DEVICE = \AS400\DXMA0MOD.SYS
DEVICE = \AS400\DXME0MOD.SYS
DEVICE = C:\PCS\EIMPCS.SYS
DEVICE = C:\PCS\ECYDDX.SYS
AUTOEXEC.BAT should include:
LSL
EXP16ODI
ODINSUP <-- Must get this from Novell
NETBIND
IPXODI
NETX
L:
LOGIN
C:\PCS\STARTPCS
PROTOCOL.INI should include:
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[ETHERNET]
DRIVERNAME = DXME0$
BINDINGS = EXP16ODI
[EXP16ODI]
DRIVERNAME = EXP16ODI$
IOADDRESS = 0x300
NET.CFG should include:
Protocol ODINSUP
Bind EXP16ODI <-- Bind 1, if using IPXODI v2.x or later
Link Driver EXP16ODI
Port 300
FRAME ETHERNET_802.3
FRAME ETHERNET_II
FRAME ETHERNET_802.2
FRAME ETHERNET_snap