Adapter drivers (software) enable the ETHERNET2 adapter (hardware) to interface with the PC/TCP kernel. Drivers are intermediate pieces of software that manage access to the adapter.
Choose one of these stacks commonly used with the ETHERNET2 adapter:
NDIS (Network Driver Interface Specification)
ODI (Open DataLink Interface)
Packet Driver
Barr Systems recommends the following configurations:
If you use LAN Support, MS LAN Manager, or any other NDIS-based network on the ETHERNET2 adapter, use an NDIS stack (see section 3.2).
If you use Novell software on the Barr PC, use the ODI stack (see section 3.3).
If you use only the Barr software on the ETHERNET2 adapter, the Packet Driver should meet your needs. The Packet Driver is the simplest to install (see section 3.4).
Your BARR/PRINT for TCP/IP package includes most of the files required for these configurations as shown in Table 3-1.
Table 3-1. Driver File Locations
|
Driver |
Included with Barr Software |
Included with 3Com Software |
Included with FTP Software |
Other Files |
|
NDIS |
NETBIND.EXE |
ELNK3.DOS |
DIS_PKT.GUP |
|
|
ODI |
|
3C5X9.COM |
ODIPKT.COM |
LSL.COM2 |
|
Packet |
|
|
ETHDRV.EXE |
|
1Rename
the Barr PROTOCOL.ISA file to PROTOCOL.INI.
2Novell software usually includes LSL.COM. You must build your own
NET.CFG file.
The Testing Driver Configuration section of your PC/TCP Kernel User’s Guide might be helpful during this process. For information about other configurations than those listed, consult your PC/TCP Kernel User’s Guide or contact Barr Technical Support.
Microsoft and 3Com codeveloped NDIS. You must use the following files for this configuration.
Table 3-2. NDIS Configuration Files
|
File |
Description |
|
NETBIND.EXE |
Resolves references set up by PROTMAN.SYS |
|
PROTMAN.SYS |
Protocol manager for NDIS |
|
PROTOCOL.INI |
Configuration file used by NDIS |
|
ELNK3.DOS |
Media Access Control (MAC) driver |
|
DIS_PKT.GUP |
PC/TCP conversion module to communicate with the NDIS driver |
|
ETHDRV.EXE |
PC/TCP kernel |
If you do not find these files in your PC/TCP directory (the default directory is C:\PCTCP), copy them from the sources listed in Table 3-1.
Make the necessary configuration changes to the PROTOCOL.INI, CONFIG.SYS, and AUTOEXEC.BAT files discussed in this section.
If you already have a PROTOCOL.INI file, modify it with a program editor to include the following statements for the PC/TCP kernel and the ETHERNET2 adapter.
If you do not have a PROTOCOL.INI file, create one based on the sample file (PROTOCOL.ISA) provided in C:\BARR.
NDIS uses the internal label ELNK3 for the ETHERNET2 adapter.
The INTVEC parameter specifies the software interrupt for communications between the packet driver and the kernel. The default interrupt used by the PC/TCP kernel is 0x60. See your PC/TCP Kernel User’s Guide for valid values.
Make a backup copy of your CONFIG.SYS file and name it CONFIG.BAR. Then you can modify the CONFIG.SYS file with a program editor.
Add these statements to the end of the CONFIG.SYS file:
The Device statement for DIS_PKT.GUP loads the PC/TCP packet conversion module. This statement enables the PC/TCP kernel to work with NDIS.
Make a backup copy of your AUTOEXEC.BAT file and name it AUTOEXEC.BAR. Then you can modify the AUTOEXEC.BAT file with a program editor.
Add the NETBIND.EXE statement to the beginning of the AUTOEXEC.BAT file.
Add the ETHDRV.EXE statement, which loads the PC/TCP kernel, to the end of the AUTOEXEC.BAT file.
After you modify the CONFIG.SYS and AUTOEXEC.BAT files and install the Barr software, restart your PC.
Apple Computers, Inc. and Novell codeveloped ODI. You must use the following files for this configuration.
Table 3-3. ODI Configuration Files
|
File |
Description |
|
3C5X9.COM |
Multiple-link interface driver (MLID) |
|
ODIPKT.COM |
PC/TCP conversion module used to communicate with the ODI driver |
|
ETHDRV.EXE |
PC/TCP kernel |
|
LSL.COM |
Link support layer (LSL) |
|
NET.CFG |
Configuration file used by ODI.COM |
Copy these files to your PC/TCP directory. If you do not find these files in your PC/TCP directory (the default directory is C:\PCTCP), copy them from the sources listed in Table 3-1.
Make the necessary configuration changes to the NET.CFG and AUTOEXEC.BAT files as described in the rest of this section.
Make a backup copy of your NET.CFG file and name it NET.BAR. Then you can modify the NET.CFG file with a program editor.
Add a Frame entry for the PC/TCP frame type of ETHERNET_II. The Barr ETHERNET2 adapter uses this frame type.
Make a backup copy of your AUTOEXEC.BAT file and name it AUTOEXEC.BAR. Then you can modify the AUTOEXEC.BAT file with a program editor.
The ODI driver for the ETHERNET2 adapter is 3C5X9.COM. You must load the packet converter ODIPKT.COM after the ODI driver. Then add the ETHDRV.EXE statement, which loads the PC/TCP kernel, to the end of the AUTOEXEC.BAT file.
After you modify the NET.CFG and AUTOEXEC.BAT files and install the Barr software, restart your PC.
For the packet driver, you only need to modify AUTOEXEC.BAT and copy 3C5X9PD.COM from the Supported Packet Driver Disk in the FTP software package. Copy 3C5X9PD.COM to your PC/TCP directory (the default directory is C:\PCTCP).
Make a backup copy of the original AUTOEXEC.BAT file and name it AUTOEXEC.BAR. Then you can modify the AUTOEXEC.BAT file with a program editor.
Add these statements to the end of the file:
The 3C5X9PD.COM statement loads the adapter driver.
The ETHDRV.EXE statement loads the PC/TCP kernel.