Contents:
EtherExpress 16 Family: Driver Installation With FTP PC/TCP
FTP PC/TCP 3.0 for DOS installation with the EtherExpress(TM) 16 adapter
FTP PC/TCP 3.0 software can be installed with the EtherExpress 16
adapter using a Packet Driver, an NDIS driver or an ODI driver. See the
appropriate section below for the driver you choose to install.
Packet Driver:
- Run SoftSet to find the I/O address setting of your EtherExpress
board and write it down.
- Run INSTALL from Disk 1 of the FTP PC/TCP installation disks.
- When prompted to install the network card, choose the "Intel
EtherExpress 16" from the list of adapters shown.
- Select the correct I/O address of the EtherExpress board.
- Continue with the FTP PC/TCP installation until complete.
Sample Configuration Files
Your configuration files will most likely contain other information.
These examples show requirements for PC/TCP only.
AUTOEXEC.BAT
c:\pctcp\exp16.com 0x60 0x310
set pctcp=c:\pctcp\pctcp.ini
c:\pctcp\ethdrv
c:\pctcp\idrive
NDIS Driver
- Run INSTALL from Disk 1 of the FTP PC/TCP installation disks.
- When prompted to install the network card, choose the "Other NDIS
Driver or Updated Packet Driver" from the list of adapters shown.
- When prompted to insert the vendor-provided driver, put the Intel
driver diskette into the A drive and press ENTER.
- Choose the "Intel EtherExpress 16 Ethernet Adapter" from the list of
choices.
- Continue with the FTP PC/TCP installation until complete.
Note: If the I/O address of your EtherExpress board is not set to 300,
you will need to edit your PROTOCOL.INI file in your PCTCP directory and
change the IOADDRESS to match the setting of your board.
Sample Configuration Files
Your configuration files will most likely contain other information.
These examples show requirements for PC/TCP only.
AUTOEXEC.BAT
c:\pctcp\netbind.com
set pctcp=c:\pctcp\pctcp.ini
c:\pctcp\ethdrv
c:\pctcp\idrive
CONFIG.SYS
device=c:\pctcp\protman.dos /I:c:\pctcp
device=c:\pctcp\EXP16.DOS
device=c:\pctcp\dis_pkt.gup
PROTOCOL.INI
[protman]
DriverName=PROTMAN$
[EXP16]
IOADDRESS = 0x310
DRIVERNAME = EXP16$
[PKTDRV]
DriverName=PKTDRV$
intvec=0x60
chainvec=0x62
BINDINGS=EXP16
ODI Driver
- Copy LSL.COM and EXP16ODI.COM from the DOS directory on the Intel
driver disk to a subdirectory on your hard drive.
- 2. Execute LSL
- 3. Execute EXP16ODI
- 4. Run INSTALL from Disk 1 of the FTP PC/TCP installation disks.
- 5. When prompted to install the network card, you will notice the
install program detected that the ODI driver is loaded in memory, choose
"ODI, EXP16ODI" from the list shown.
- 6. Continue with the FTP PC/TCP installation until complete.
Sample Configuration Files
Your configuration files will most likely contain other information.
These examples show requirements for PC/TCP only.
AUTOEXEC.BAT
C:\EE16DRVR\LSL
C:\EE16DRVR\EXP16ODI
c:\pctcp\odipkt.com
set pctcp=c:\pctcp\pctcp.ini
c:\pctcp\ethdrv
c:\pctcp\idrive
NET.CFG
LINK DRIVER EXP16ODI
PORT 310
FRAME ETHERNET_II
PROTOCOL TCPIP 8137 ETHERNET_II
FTP PC/TCP - 2.05 Configuration
This document applies to the EtherExpress(TM) 16, 16TP, 16C, FLASH,
FLASH TP, FLASHC, MCA, and MCA/TP adapters. This is an example only.
Your configuration may vary.
Notes for FTP PC/TCP installations:
Make sure the customer is running PC/TCP for DOS v2.05 and that the
kernel is PC-210.
Make sure that the protocol.ini, pro.msg, proh.msg are located in
the c:\lanman subdirectory.
Copy the EtherExpress 16 NDIS adapter driver from the LAN Adapter
diskette. (\NDIS\EXP16.DOS).
Example configuration files.
CONFIG.SYS:
files=40
buffers=40
device=c:\ftp\protman.dos
device=c:\ftp\exp16.dos
device=c:\ftp\dis_pkt.gup
device=c:\ftp\ipcust.sys
device=c:\ftp\ifcust.sys
AUTOEXEC.BAT:
path=c:\dos;c:\ftp
prompt $p$g
c:\ftp\netbind
c:\ftp\ethdrv
PROTOCOL.INI:
[PROTOCOL MANAGER]
drivername=PROTMAN$
;MACS
[EXP16]
drivername=EXP16$
ioaddress=0x300
;PROTOCOLS
[PKTDRV]
drivername=PKTDRV
bindings=EXP16
intvec=0X65
Note: The important part here is that what the bindings statement
refers to must be the name of the statement for the EtherExpress
statement. (i.e. if bindings=INTEL16, then you must have [INTEL16]).
Also EXP16$ should be in caps.
5. If you have problems, add a pause to the top line of the
AUTOEXEC.BAT file to see that the CONFIG.SYS loads with no errors.
FTP PC/TCP AND ODI
Notes for FTP PC/TCP and ODI installations:
- Make sure the customer is running PC/TCP for DOS version 2.05,
Patch level 4 (PL4) and that the kernel is PC-210.
- Check the NET.CFG file. It should look similar to the following:
Link Support
buffers 8 1514
mempool 4096
Protocol TCPIP
Bind EXP16ODI <-- delete if using IPXODI v2.x or later
Protocol IPX
Bind EXP16ODI <-- Bind 1, if using IPXODI v2.x or later
Link Driver EXP16ODI
port 300
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3
Frame Ethernet_II
Protocol TCPIP 8137 Ethernet_II