============================ R E A D M E N O T E S ============================ Broadcom 440x 10/100 Integrated Controller Ethernet Driver for DOS NDIS2 driver Copyright (c) 2002-2005 Broadcom Corporation All rights reserved. CUSTOM KEYWORDS in driver in protocol.ini: BusNum DevNum FuncNum or PortNum LineSpeed Duplex NodeAddress RxBuffer BusNum: This decimal parameter, range from 0-255, specifies the PCI bus number on which the ethernet controller is located. DevNum: This decimal parameter, range from 0-31, specifies the PCI device number assigned to the ethernet controller. FuncNum or PortNum: This decimal parameter, range from 0-7, specifies the PCI function or port number assigned to the ethernet controller. LineSpeed: This decimal parameter, 10/100, specifies the speed of the network connection. Duplex: This string parameter, HALF/FULL, specifies duplex mode on the ethernet controller. The Linespeed parameter must be set when this keyword is used. If neither the Duplex nor the Linespeed paramaters are specified the ethernet controller will default to autonegotiate mode. NodeAddress: This string parameter specifies the network address used by the the ethernet controller. If Multicast Address or Broadcast Address was specified, the default MAC Address will be used. RxBuffer: This decimal parameter, range from 1-6, specifies the additional receive buffers to be use by the driver. This could enhance the driver's download performance in some cases, but would require more of system memory. An increase of approximately of 8KB when specified the maximum 6 receive buffers. Note: The first three keywords are used concurrently and have been included for manufacturing purposes. Do not use them unless you are familiar with PCI device configuration. These three keywords are needed if multiple NetXtreme boards are on a system and (a) specific NetXtreme adapter/s need to be loaded in specific order. Example of the use of these key words in the protocol.ini: [B44] DriverName = "B44$" BusNum = 3 DevNum = 14 PortNum = 2 LineSpeed = 100 Duplex = Full NodeAddress = "001020304050" To add more adapter(up to 4) repeat the below entry, where n can be from 2 to 4. [B44_n] DriverName = "B44n$" BusNum = DevNum = Example of using addition entries to load more than one adapter in the protocol.ini: [B44] DriverName = "B44$" BusNum = 3 DevNum = 10 [B44_2] DriverName = "B442$" BusNum = 3 DevNum = 11 [B44_3] DriverName = "B443$" BusNum = 3 DevNum = 12 [B44_4] DriverName = "B444$" BusNum = 3 DevNum = 13 NOTE: I) In some cases due to memory constraints the command NET START may not function properly. For these situations NET START BASIC is recommended. For some applications that utilize "autostart" by using NET LOGON or NET USE, there are two keywords in the \NET\SYSTEM.INI file under heading [network] that will dictate which NET Service to run when using "autostart": 1) preferredredir 2) autostart Make sure these two keywords are as follows: 1) preferredredir=basic 2) autostart=basic II) For some application that builds a Network Boot Disk such as MODBOOT, the bracketed module name,i.e, [B44], must be remove or commented out as ;[B44] in the supplied protocol.ini file before building the disk.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.