Installing the EISA PC Adapter NetWare Driver

These additional lines allow the server to take advantage of the FDDI larger packet size and increases the number of receive buffers, thus improving performance.

Step 3 Add the following load commands to the autoexec.ncf file:

load c:\netware\patchman
load c:\netware\lslenh
load c:\netware\msm31x
load c:\netware\fdditsm

Step 4 Proceed to the section "Editing the autoexec.ncf to Load a Driver with Different Frame Formats."

Editing the autoexec.ncf to Load a Driver
with Different Frame Formats

The autoexec.ncf file must be modified to load the following:

• adapter driver---Adapter driver is the same for all CDDI/FDDI EISA adapter: CRS320T.
  

• slot number---Adapter card physical slot.
  

• logical adapter name variable---Used with bind command.
  

• load frame format---Two different frame formats may be used, each with different network protocols supported:
  

  • FDDI_802.2 frame format used with IPX and OSI protocols
    

  • FDDI_SNAP frame format used with IPX, TCP/IP, AppleTalk protocols
    

The load command format follows:

load crs320T slot=[physical slot number] name=[variable] frame=[frame format]

See examples of load and bind commands for four different protocol types in the section "Binding Protocol to Frame Format Examples."

Binding Protocol to Frame Format Examples

The bind command is used to logically associate the driver to the protocol stack. In each protocol bind that follows, the adapter is assumed to be in slot 5:

• IPX Bind Example
  

load crs320T slot=5 name=cisco frame=FDDI_802.2
bind ipx to cisco net=12

• OSI Bind Example
  

load osill
load isis
load crs320T slot=5 name=cisco frame=FDDI_802.2
bind CLNP to cisco

• TCP/IP Bind Example
  

load tcpip
load crs320T slot=5 name=cisco frame=FDDI_SNAP
bind IP to cisco addr=[IP address of this server interface]

• AppleTalk Bind Example
  

load appletlk net=3 zone={"admin"}
load crs320T slot=5 name=cisco frame=FDDI_SNAP
bind appletlk to cisco net=12-12

Note Multiple frame formats may be bound to the same adapter, and multiple adapters may be configured in the same PC.

Reboot Server Steps

Before the changes made to the files can take effect you must restart the server using the NetWare down and exit commands, as follows:

Step 1 Remove the EISA PC Driver Disk from the floppy drive.

Step 2 Enter down and exit to restart the server.

Step 3 Verify the installation by logging into the server from a client station.

Installing Client Drivers

Each client PC attached to the NetWare network server using the workgroup CDDI/FDDI EISA PC adapter must have the client drivers installed.

Installing the client drivers involves the following tasks:

• Installing Files
  

• Editing Client autoexec.bat to Load the Drivers
  

• Editing Client net.cfg to Link a Driver to a Frame Format
  

• Rebooting Client
  

Installing Files

To install the client driver files on your EISA PC, use the DOS copy command to copy the following files to the server root directory from the \novell\client directory of the workgroup CDDI/FDDI EISA Driver disk.

CRS320T.COM
LSL.COM
IPXODI.COM
NETX.EXE

(For example: COPY A:\NOVELL\CLIENT\CRS320T.COM C:\)

Editing Client autoexec.bat to Load the Drivers

Modify the autoexec.bat to include the following lines to execute the Novell drivers and the CDDI/FDDI EISA adapter drivers when the client reboots:

C:\LSL.COM
C:\CRS320T.COM
C:\IPXODI.COM
C:\NETX.EXE

Note The previous lines assume the files are copied into the root directory.

Make sure there are no shared-memory conflicts with other boards or programs, such as TSR (terminate-stay-resident) programs.

When loading EMM386.EXE in the config.sys, add x=c800-c9ff if the EISA PC adapter was assigned address c800 by the EISA configuration utility.

The client driver can be loaded high by using the DOS loadhigh command. This allocates more space for application programs. You will need to use a memory manager, such as EMM386.EXE or QEMM.EXE, to use the upper memory.

Note Remember to exclude the adapter shared memory area (x=c800-c9ff) in these programs.

Editing Client net.cfg to Link a Driver to a Frame Format

Modify the net.cfg file to link Novell drivers and EISA NetWare driver and the proper frame format for the network protocol type supported.

The net.cfg file must be modified as follows:

• link---The CDDI/FDDI EISA adapter driver
  

• load frame format---Two different frame formats can be used, each with different network protocols supported:
  

  • FDDI_802.2 frame format used with IPX, OSI, and IP protocols
    

  • FDDI_SNAP frame format used with TCP/IP, AppleTalk, and IPX protocols
    

  Edit the net.cfg file to match the network protocol being supported.
  

FDDI_802.2 Used with IPX and OSI

If you are using the FDDI_802.2 frame format, add the following lines to the net.cfg:

link driver crs320T
frame FDDI_802.2

The space before the word frame in the second line of the previous example is required to properly format the command. The client driver default frame format is FDDI_802.2. A net.cfg file is not needed if the frame format is FDDI_802.2.

FDDI SNAP Used with TCP/IP and AppleTalk

If you are using the FDDI_SNAP frame format, add the following lines to the net.cfg:

link driver crs320T
frame FDDI_SNAP

The space before the word frame in the second line of the previous example is required to properly format the command.

Rebooting Client

Before the changes made to the autoexec.bat and net.cfg files can take effect, you must reboot the client workstation as follows:

Step 1 Remove the EISA PC Driver disk from the floppy drive.

Step 2 Reboot the PC to load the drivers.

Step 3 Verify the installation by logging into a server.

Copyright 1988-1996 © Cisco Systems Inc.