User guide

C:\VLM
4. 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 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
5. Restart the computer to complete the installation. 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 is displayed.
6. Change to drive F and log on to the Netware server.
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
is displayed.
Configuring Parameters for the B44.com Driver (in
the Net.cfg file)
The following are optional custom keywords used in the Net.cfg file:
BUSNUM
DEVNUM
The 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 440X 10/100 Integrated 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