BC 4035, Appendix B - Novell ODI Driver Installation

BC 4035
Appendix B - Novell ODI Driver Installation

The BC uses AMD’s ODI Pcnet family of drivers for the Novell environment. Cubix has included the latest version of these drivers on the BC Series 10 Base-T Driver Diskette. The latest updates for these drivers are available on the Cubix BBS (refer to the rear of this manual for BBS information)

The files on the BC Series 10 Base-T Driver Diskette are compressed in the form of self extracting ZIP files. Before installation of any drivers, the appropriate ZIP file must be decompressed. To decompress the NetWare DOS, OS/2, 3.x and 4.x drivers, insert the driver diskette into the system, change to that drive and type:

novell-d

The decompressed drivers will be placed on the same diskette. After the files are decompressed, the diskette is ready for installation.

NetWare DOS ODI Client Driver

NetWare PCnet DOS ODI driver is located in the NOVELL\WKSTN\DOSODI subdirectory on the driver diskette. This driver can be loaded directly from the DOS command line or from a batch file (such as AUTOEXEC.BAT). The example below is for a NETX configuration using default settings.

Copy the following files from the BC Series 10 Base-T Driver Diskette to the root or subdirectory:

LSL.COM
PCNTNW.COM
IPXODI.COM
NETX.EXE
NET.CFG

Load these files in the following order:

LSL
PCNTNW.COM
IPXODI
NETX

NET.CFG for BC 4035 Board

The following illustrates the proper format for the NET.CFG file:

# NET.CFG File for the Cubix BC 4035
#

Link Driver PCNTNW

PORT 300

DMA 5

INT 5

Frame Ethernet_802.3

Protocol IPX 0 Ethernet_802.3

If this information is not provided in the NET.CFG file, the PCNTNW driver will default to IRQ 3 and frame type 802.2. Make sure all lines following "Link Driver PCNTNW" are indented. If these lines are not indented, the PCNTNW driver will ignore the commands.

To change parameters such as IRQ, frame type, etc., edit the NET.CFG file. When editing the NET.CFG file, be aware that either IRQ 3 or 5 are supported. The DMA channel is fixed at 5 and the I/0 port address is fixed at 300H.

NetWare OS/2 ODI Client Driver

The NetWare OS/2 ODI driver is located in the NOVELL\WKSTN\OS20DI subdirectory of the driver diskette. This driver should be loaded from the OS/2 CONFIG.SYS file. For more information on installing and configuring the OS/2 ODI driver, please refer to the NetWare Requester for OS12 Installation documentation.

Example Configuration:

Copy the OS/2 ODI driver PCNTNW.OS2 from the BC Series 10 Base-T Driver Diskette to the C:\NETWARE directory of the boot drive.

Edit the CONFIG.SYS file to load the driver as follows: DEVICE=C:\NETWARE\PCNTNW.OS2

Following is an example CONFIG.SYS load sequence for the OS/2 ODI driver configured for the IPX protocol stack.

REM --- NetWare Requestor Statements Begin ---

DEVICE = C:\NETWARE\LSL.SYS
RUN = C:\NETWARE\DDAEMON.EXE
DEVICE = C:\NETWARE\PCNTNW.OS2
DEVICE = C:\NETWARE\IPX.SYS
DEVICE = C:\NETWARE\NWREQ.SYS
IFS = DEVICE = C:\NETWARE\NWIFS.IFS
RUN = DEVICE = C:\NETWARE\NWDAEMON. EXE

REM --- NetWare Requestor Statements End ---

To change parameters such as IRQ, frame type, etc., edit the NET.CFG file.

Both IRQ 3 and 5 are supported. The DMA channel is fixed at 5 and the I/0 port address is fixed at 300H.

NetWare ODI Server Driver

The NetWare v3.11, v3.12, and v4.x server drivers are located under the \NOVELL\SERVER\3.1 X and \NOVELL\SERVER\4.X subdirectories. The NetWare server drivers for the BC are loaded and configured using the LOAD and BIND statements from the server's console. Please refer to the NetWare installation documentation for further information on loading and configuring network card drivers.

Example for IPX driver under NetWare 3.11

1. Copy the files from \NOVELL\SERVER\3.lX directory on the driver diskette to the \SYSTEM directory on the file server.

PCNTNW.LAN v3.1x/v4.x Server Driver

MSM31X.NLM Media Support Module for 3.1x

PATCHMAN.NLM Patch file called by LSLENH

ETHERTSM.NLM Ethernet TSM for v3.1x

LSLENH.NLM Enhanced LSL for v3.11

MONITOR.NLM new Monitor program required for v3.11

****IMPORTANT****

2. In NetWare 3.11 installations only, LSLENH.NLM must be loaded before any other LAN driver is loaded. (LSLENH is not used with NetWare v3.12 or v4.x.)

3. Load and bind the PCNTNW driver to IPX. Following is an example sequence for the file server's AUTOEXEC.NCF file.

LOAD LSLENH (autoloads PATCHMAN.NLM)

LOAD MSM31 X

LOAD PCNTNW

Frame = Ethernet 802.3 ( autoloads ETHERTSM.NLM)

BIND IPX to PCNTNW net= 25

Be sure to replace the MONITOR.NLM which was shipped with v3.1 1 with the newer version included.

For BC 4035 processor, the LOAD PCNTNW command line should specify the Base I/0 Port Address, DMA Channel, and Interrupt level as well as the Frame type. For example:

LOAD PCNTNW IOP=300 DRQ=5 IRQ=5

Frame = Ethernet 802.3

Do not use PORT, DMA, and INT keywords. Use IOP, DRQ, and IRQ instead.

PORT must remain set to 300H and DMA must be 5. The IRQ may be 3 or 5.

Diskless Boot ROM

The Diskless Boot ROM is enabled in the AMI BIOS Setup program in the Advanced Chipset Options. When it is enabled, the BC will execute Novell's RPL code during system boot to allow the BC to be configured for diskless boot. The Diskless Boot ROM is mapped into the 32KByte section of system memory at C8000-CBFFF. Please refer to Novell's installation documentation for details on how to configure a workstation for diskless boot.

To enable the diskless boot option, set the "ON BOARD LAN BIOS BOOT" to "enabled". The C and D drives must be configured as "Not Installed" in the Standard CMOS Setup section.

When the Diskless Boot ROM is enabled the port address, DMA channel, IRQ, and Boot ROM Memory address are fixed at the following locations.

I/0 Address =300

DMA Channel = 5

IRQ = 5

Memory Address = C8000-CBFFF

The following configuration changes are required:

1. Change the NET.CFG file from Ethernet - 802.3 to Ethernet-802.2. This requires modifying the Frame and Protocol lines as follows:

Frame Ethernet 802.2

Protocol IPX EO Ethernet 802.2

NOTE: The Protocol ID must be changed from 0 (for 802.3) to EO (for 802.2).

2. Add the following lines to the file server's AUTOEXEC.NCF file:

LOAD PCNTNW IOP=300 DRQ=5 IRQ=5

FRAME=ETHERNET_802.2

BIND IPX TO PCNTNW [FRAME= ETHERNET-802.21 NET= 26

LOAD RPL

BIND RPL TO PCNTNW [FRAME= ETHERNET-802.21

3. Copy the RBOOT.RPL file to the SYS:LOGIN directory of the file server.

This document, and all Web contents, Copyright © 1997 by Cubix Corp., Carson City, NV, USA.