Back to Contents Page

# DOS ODI Driver Software: Broadcom NetXtreme® 57XX User Guide

Installing the Driver Software

Configuring Parameters for the B57.com Driver (in the Net.cfg File)

The Open Data-Link Interface (ODI) application allows LAN drivers to work together irrespective of differences between the hardware and/or the protocol stacks of communicating computers. An intervening layer, called the link support layer (LSL), is responsible for routing different packet types between LAN drivers and protocol stacks.

## Installing the Driver Software

Installing the ODI driver software involves the following steps:

1. Verifying that the MS-DOS 6.22 operating system files are installed on your computer hard disk or are available on a removable storage medium.
2. Installing the ODI driver software in the MS-DOS environment.
3. If necessary, reconfiguring the driver software after installation.

### Preinstallation Requirements

1. Verify that the Broadcom NetXtreme Gigabit Ethernet adapter driver software has been installed on your computer and install it if it has not (see Installing the Driver Software). Otherwise, you cannot use a Broadcom NetXtreme Gigabit Ethernet adapter in the MS-DOS environment.

| NOTE: To successfully install the controller driver in the MS-DOS environment, the adapter must be installed in the computer before you install the adapter driver.

1. Install the MS-DOS 6.22 files on your computer hard disk or have them available on a removable storage medium.

### Installing the ODI Driver in the MS-DOS 6.22 Environment

1. Copy the ODI driver file (B57.com) to the root directory of the hard disk.
2. Copy the Lsl.com, Ipxodi.com, and Vlm.com files to the same directory (these files are provided by Novell).
3. Edit the Autoexec.bat file by adding the following lines:

C:\LSL
C:\B57
C:\IPXODI
C:\VLM

1. Edit the Net.cfg file and place the file in the same location as the Autoexec.bat file (located in drive C) to configure the driver to bind with different frame types.

Example:

LINK DRIVER B57
FRAME ETHERNET_802.2
FRAME ETHERNET_802.3
FRAME ETHERNET_II
FRAME ETHERNET_SNAP
NetWare DOS Requester
FIRST NETWORK DRIVE=F
NETWARE PROTOCOL=NDS BIND
PROTOCOL IPXODI

1. Restart the computer to complete the install.
2. As the files are being loaded, the computer attempts to attach to a Netware server using the frame types specified in Net.cfg. If the connection is successful, a dialog box appears.
3. Change to drive F and log on to the NetWare server.

| NOTE: The driver loads during system configuration, and the Broadcom banner, the adapter name, the MAC address, the IRQ number, the detected line speed, and the BUSNUM and DEVNUM of the adapter are displayed. If the driver fails to load, an initialization fail message appears.

## Configuring Parameters for the B57.com Driver (in the Net.cfg file)

The following are optional custom keywords used in the Net.cfg file:

BUSNUM

DEVNUM

FUNNUM

SUBVID

MODEL

The first two keywords (BUSNUM and DEVNUM) are used concurrently and have been included for manufacturing purposes. Do not use them unless you are familiar with PCI device configuration. These two keywords are needed if multiple Broadcom NetXtreme Gigabit Ethernet adapters are installed in a computer, and each adapter must be loaded in a specific order.

BUSNUM specifies the PCI bus number and DEVNUM specifies the device number that is assigned to the adapter when it is configured by the PCI BIOS.

The values for these adapter parameters are displayed in hexadecimal notation when the driver loads (the Net.cfg file expects hexadecimal values). A PCI device scan utility can also be used to find this information. If the driver loads on a single adapater, the displayed values can be used in the Net.cfg file.

If a PCI scan utility displays adapter 1 at bus 4 and device 11 (hexadecimal), and adapter 3 at bus 3 and device 13 (hexadecimal), the following load instructions are written to the Net.cfg file (load adapter 3 first, and optionally load adapter 1 second):

LINK DRIVER B57

BUSNUM 3

DEVNUM 13 (13 hex = 19 decimal)

LINK DRIVER B57

BUSNUM 4

DEVNUM 11 (11 hex = 17 decimal)

The FUNNUM keyword is used to determine which function/port the driver is to load on when using a multifunction (multiport) adapter. Function number values are limited to 0 and 1, for the first and second ports of the adapter.

The SUBVID keyword is used to for load the driver only on the first adapter found that has a subvendor ID (SVID) that matches the one set in Net.cfg. The driver ignores all other adapters that do not have a matching SVID. SUBVID expects a hexadecimal number.

Example:

LINK DRIVER B57

SUBVID 14E4

SUBVID cannot be used with BUSNUM, DEVNUM or FUNNUM.

The MODEL keyword is for loading the driver only on the first adapter found that has a subvendor ID (SVID) that matches the one set in MODEL. The driver ignores all other adapters that do not have a matching SVID. MODEL expects a decimal number.

Example:

LINK DRIVER B44

MODEL 5348

Back to Contents Page