Novell DOS ODI WorkstationNovell DOS ODI Workstation

Contents

I.    Special Considerations 
II.   Files Needed for Installation 
III.  Installing the AT-2400 DOS ODI driver using the Novell DOS Requester 
IV.   Installing the AT-2400 DOS ODI driver manually 
V.    Removing an Existing Driver
VI.   Finding the MAC Address

I.  Special Considerations
Configuration of the AT-2400 resources is under PCI control. For most 
applications, no setup other than normal installation of the network software is 
necessary. To change port settings, view the speed and duplex settings, or to 
run Diagnostics, use SETUP.EXE. 

II. Files Needed for Installation
The following drivers and installation scripts are located on CardAssistant Disk.
16-bit Driver files:
AT24ODI.COM    DOS ODI client driver 
AT24ODI.INS    Installation script
32-bit Driver files:
AT24ODIv3.LAN  32-bit ODI driver
AT24ODIv3.LDI   Installation script

III.  DOS Client32 Installation
Start the Novell Client32 installation program, following Novell’s 
documentation for client setup options, and proceed to the driver installation 
portion of the setup. 

Select the type of driver you wish to use, i.e. 16-bit or 32-bit, and supply 
the appropriate path on the CardAssistant diskette to the driver. The 16-bit 
driver is located in the root directory, and the 32-bit driver is located 
under the Netware directory. You should see Allied Telesyn AT-2400 PCI 
Ethernet Adapter appear if the proper path has been supplied. Press Enter to 
select the driver and proceed with installation. 

IV. Manual Installation
Note: If you have a PCI-1 bus in your system, add the line BUSTYPE PCI1 to the 
NET.CFG file. Otherwise the driver may not find the card. If you don't know 
which bus you have, try loading without the option. If it loads, you don't need 
it.

Copy the contents of the DOS directory of the CardAssistant diskette to a 
directory you specify, i.e. C:\NET. 
Check the NET.CFG file to make sure the first frame type listed under the LINK 
DRIVER section matches the frame type the server is using. If you don't know, 
go to the file server console and type CONFIG. This will should the driver 
information for the server, including which frame types are available. 
Modify your AUTOEXEC.BAT (or batch file that loads the Novell drivers) to 
contain the following lines in this order:
LSL
A24ODI
IPXODI
NETX (or VLM) 

When using NETX.EXE, Check the CONFIG.SYS file in the root directory of drive 
C: for a LASTDRIVE statement. If there is none, the first network drive will 
be F:. Otherwise the first network drive will be the next letter after the one 
specified by LASTDRIVE. Otherwise, make sure that LASTDRIVE is set to Z when 
using VLMs, and that the NET.CFG specifies the first network driver under the 
Novell DOS Requester section.

Example:
LINK DRIVER AT24ODI
BUSTYPE PCI1

Reboot your computer by pressing the reset button, or by turning the power 
switch off and on. Do NOT use <Ctrl>+<Alt>+<Delete>. Some PCI systems do not 
reset bus-mastering cards with a warm boot. 
SAMPLE CONFIGURATION FILES - ODI
CONFIG.SYS
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
BUFFERS=30,0
FILES=45
DOS=HIGH,UMB
LASTDRIVE=Z 

Note: Set LASTDRIVE=Z only when using VLMs. The Novell DOS workstation 
installation will automatically set it for you. When using NETX, the first 
network drive is the next letter after the LASTDRIVE setting in the CONFIG.SYS.

AUTOEXEC.BAT
PATH C:\DOS
PROMPT $P$G
CD \NET
LH LSL
LH A24ODI
LH IPXODI
LH NETX
F:
LOGIN SERVER/USERNAME
STARTNET.BAT (DOS Requester - VLMs)
@ECHO OFF
CD \NWCLIENT
SET NWLANGUAGE=ENGLISH
LH LSL
LH A24ODI
LH IPXODI
VLM
CD \
NOTE: VLMs automatically load into high memory. 
NET.CFG (VLMs)
LINK DRIVER A24ODI
      FRAME ETHERNET_802.2
NETWARE DOS REQUESTER
      FIRST NETWORK DRIVE = F      
NET.CFG (NETX)
LINK DRIVER A24ODI
      FRAME ETHERNET_802.2

V. Removing an existing driver 
To de-install the driver, remove the driver from the STARTNET.BAT or 
AUTOEXEC.BAT file, or comment it out, and reboot.

VI. Finding the MAC Address
The MAC address appears when the driver loads. If necessary, add a pause 
statement in the batch file which loads the driver to pause the system after the 
driver loads.