Installing the Driver Software
Configuring Parameters for the b44.com Driver
(in the Net.cfg File)
Open Data-Link Interface (ODI) 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. |
Example:
c:\
copy b44.com c:\
C:\LSL
C:\B44
C:\IPXODI
C:\VLM
Example:
LINK DRIVER B44
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:
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.
These keywords 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 440X 10/100 Integrated Controllers are installed on a computer and each controller must be loaded in a specific order.
The values for these adapter parameters are displayed on the screen in hexadecimal notation when the driver loads. A PCI device scan utility can also be used to find this information.
The values are displayed in hexadecimal notation (the Net.cfg file expects hexadecimal values).
Example:
If the driver loads on a single controller, the values displayed on screen 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), then the following load instructions are written to the Net.cfg file (load card 3 first, and optionally load card 1 second):