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 DOS/ODI driver software involves the following steps:
![]() |
Note: To successfully install the controller driver for DOS, the controller must be installed in the computer before you install the driver. |
C:\LSL
C:\B57
C:\IPXODI
C:\VLM
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
F: <enter>
F:\login admin <enter>
![]() |
Note: The driver loads during system configuration, and the Broadcom banner, the controller name, the MAC address, the IRQ number, the detected line speed, and the BUSNUM and DEVNUM of the controller are displayed. If the driver fails to load, an initialization fail message appears. |
The following are optional custom keywords used in the Net.cfg file:
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 57XX Ethernet controllers are installed on a computer and each controller must be loaded in a specific order.
BUSNUM specifies the PCI bus number and DEVNUM specifies the device number that is assigned to the board 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 controller, the displayed values can be used in the Net.cfg file.
If a PCI scan utility displays card 1 at bus 4 and device 11 (hexadecimal), and card 3 at bus 3 and device 13 (hexadecimal), the following load instructions are written to the Net.cfg file (load card 3 first, and optionally load card 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) controller. Function number values are limited to 0 and 1, for the first and second function of the controller.
The SUBVID keyword is used to for load the driver only on the first network interface card found that has a subvendor ID (SVID) that matches the one set in Net.cfg. The driver ignores all other network interface cards that do not have a matching SVID. SIBVID 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 network interface card found that has a subvendor ID (SVID) that matches the one set in MODEL. The driver ignores all other NICs that do not have a matching SVID. MODEL expects a decimal number.
Example:
LINK DRIVER B44
MODEL 5348