NDIS2 Driver Software: Broadcom NetXtreme II™ Network Adapter User Guide
Installing the NDIS2 Driver Software for Use on MS-DOS Platforms
Using Keywords for the BXND20X.dos Drivers
Preinstallation Requirements
Before you can successfully install the NDIS2 driver software, the Broadcom network controller must be physically installed on the server. Networking software that is appropriate to the operating system (such as Microsoft LAN Manager 2.2 for MS-DOS) must already be running on your server.
Installing the NDIS2 Driver Software for Use on MS-DOS Platforms
The NDIS2 driver software can be run from an MS-DOS startup disk using Microsoft Network Client 3.0 or from the hard disk using Microsoft LAN Manager 2.2.
Creating a Startup Disk to Run Microsoft Network Client
To perform this installation you must have the following items
- Windows NT Server 4.0 CD-ROM
- A blank MS-DOS system disk (3.5" high-density floppy disk)
- Access to the Broadcom NDIS2 driver file (BXND20X.dos). This file is located on the driver source media.
NOTES:
- Windows NT Server 4.0 users. When running Setup for Microsoft Network Client v3.0 for MS-DOS, click any network card from the list (NE2000 Compatible, for example) to create the startup disk.
- After creating the startup disk, follow the instructions in Modifying the Startup Disk.
To create a startup disk
- Create a folder called NCADMIN in the root of the C drive.
- Copy the NCADMIN.CN_, NCADMIN.EX_, and NCADMIN.HL_ files from the I386 folder on the Windows NT Server 4.0 CD-ROM.
- Open a command prompt window and change the directory to C:\NCADMIN.
- Type
expand -r ncadmin.*
and press ENTER.- Close the command prompt window by typing exit and then pressing ENTER.
- Start Windows Explorer.
- Open the NCADMIN folder and double-click ncadmin.exe.
- Follow the on-screen instructions to make the network startup disk (choose NE2000 Compatible from the list of adapters).
Modifying the Startup Disk
To modify the startup disk
- Edit A:\Net\Protocol.ini with Notepad or a similar text editor.
- Change
DriverName=$
toDriverName=BXND20X$
.- Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as IOBASE=0x300 or INTERRUPT=3, and so on.
Example Protocol.ini file for IP
[network.setup]version=0x3110netcard=ms$ne2clone,1,MS$NE2CLONE,1transport=tcpip,TCPIPlana0=ms$ne2clone,1,tcpip[MS$NE2CLONE]DriverName=BXND20X$[protman]DriverName=PROTMAN$PRIORITY=MS$NDISHLP[tcpip]NBSessions=6DefaultGateway=0SubNetMask=255 0 0 0IPAddress=192 168 0 1DisableDHCP=0DriverName=TCPIP$BINDINGS=MS$NE2CLONELANABASE=0Example Protocol.ini file for IPX
[network.setup]version=0x3110netcard=ms$ne2clone,1,MS$NE2CLONE,1transport=ms$ndishlp,MS$NDISHLPtransport=ms$nwlink,MS$NWLINKlana0=ms$ne2clone,1,ms$nwlinklana1=ms$ne2clone,1,ms$ndishlp[MS$NE2CLONE]DriverName=BXND20X$[protman]DriverName=PROTMAN$PRIORITY=MS$NDISHLP[MS$NDISHLP]DriverName=ndishlp$BINDINGS=ms$ne2clone[ms$nwlink]DriverName=nwlink$FRAME=Ethernet_802.2BINDINGS=MS$NE2CLONELANABASE=0Example Protocol.ini file for NetBEUI
[network.setup]version=0x3110netcard=ms$ne2clone,1,MS$NE2CLONE,1transport=ms$ndishlp,MS$NDISHLPtransport=ms$netbeui,MS$NETBEUIlana0=ms$ne2clone,1,ms$ndishlplana1=ms$ne2clone,1,ms$netbeui[MS$NE2CLONE]DriverName=BXND20X$[protman]DriverName=PROTMAN$PRIORITY=MS$NDISHLP[MS$NDISHLP]DriverName=ndishlp$BINDINGS=MS$NE2CLONE[MS$NETBEUI]DriverName=netbeui$SESSIONS=10NCBS=12BINDINGS=MS$NE2CLONELANABASE=0- Edit A:\Net\System.ini.
- Change
netcard=
tonetcard=BXND20X.dos
.- Check for references to C:\NET and change
C:\NET
toA:\NET
if necessary.Example System.ini file
[network]sizworkbuf=1498filesharing=noprintsharing=noautologon=yescomputername=MYPClanroot=A:\NETusername=USER1workgroup=WORKGROUPreconnect=yesdospophotkey=Nlmlogon=0logondomain=preferredredir=basicautostart=basicmaxconnections=8[network drivers]netcard=BXND20X.dostransport=ndishlp.sys,*netbeuidevdir=A:\NETLoadRMDrivers=yes- Copy BXND20X.dos to A:\Net.
- Create the appropriate Autoexec.bat file in drive A for the chosen protocol as shown below.
For TCP/IP
path=a:\neta:\net\net initializea:\net\netbind.coma:\net\umb.coma:\net\tcptsr.exea:\net\tinyrfc.exea:\net\nmtsr.exea:\net\emsbfr.exea:\net\net start basicnet use z: \\SERVERNAME\SHARENAMEFor IPX
SET PATH=A:\NETA:\NET\net initializeA:\NET\nwlinkA:\NET\NET START BASICnet use z: \\SERVERNAME\SHARENAMEFor NetBEUI
SET PATH=A:\NETA:\NET\NET START BASICnet use z: \\SERVERNAME\SHARENAME- Create a Config.sys file on the startup disk in drive A as shown below.
files=30device=a:\net\ifshlp.syslastdrive=zInstalling the DOS NDIS2 Driver Software on the Hard Disk
To install the DOS NDIS2 Driver Software on the hard disk
- Verify that the system has Microsoft LAN Manager 2.2 installed, with a protocol such as NetBEUI configured.
- Create a folder on your hard disk to store the NDIS 2.01 driver.
Example: C:\LANMAN
- Copy the BXND20X.dos file to this folder.
Edit the Config.sys file by adding the following lines:DEVICE = C:\LANMAN\PROTMAN.DOSDEVICE = C:\LANMAN\BXND20X.DOSDEVICE = C:\LANMAN\NETBEUI.DOS- Edit the Autoexec.bat file by adding the following lines:
C:\ LANMAN\NETBIND.EXEC:\LANMAN\NET START WORKSTATIONC:\LANMAN\NET USE drive letter: \\server name\resource name- Edit the Protocol.ini file (located in C:\LANMAN) to configure the driver to bind with NetBEUI or any other protocols.
Example:
[PROTOCOL MANAGER]DriverName = PROTMAN$[NETBEUI_XIF]DriverName = netbeui$BINDINGS = BXND20X[BXND20X]DriverName = "BXND20X$"- Restart the computer to complete the installation.
NOTE: The driver loads during system configuration and displays the Broadcom banner, controller name, MAC address, IRQ number, detected line speed, and the controller BusNum and DevNum. If the driver fails to load, an initialization fail message is displayed.
Using Keywords for the BXND20X.dos Drivers
The Protocol.ini file contains certain keywords that are used by the BXND20X.dos drivers. These keywords are listed below:
BusNum. Specifies the number of the PCI bus on which the network adapter is located. Requires a decimal number having a value ranging from 0 to 255.
DevNum. Specifies the device number assigned to the network adapter when it is configured by the PCI BIOS. Requires a decimal number having a value ranging from 0 to 255.
FuncNum or PortNum. Specifies the PCI function or port number assigned to the network controller. Requires a decimal number having a value ranging from 0 to 7.
NOTE: These keywords, BusNum, DevNum, and FuncNum (or PortNum) are needed when multiple adapters are installed in the server and when a specific controller must be loaded in a certain order. These keywords are used concurrently and are included for manufacturing purposes. Do not use them unless you are familiar with how to configure PCI devices. A PCI device scan utility is needed to find this information.
LineSpeed. Specifies the speed of the network connection in Mbit/s. Requires the decimal number 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and is achievable only through auto-negotiation. For the sake of simplicity, the driver performs auto-negotiation when the line speed is set to a value of 1000.
Duplex. Specifies the duplex mode of the network adapter. Requires a setting of either Half or Full. When this keyword is used, the LineSpeed keyword must also be used. If neither keyword is used, the network adapter defaults to auto-negotiation mode.
NodeAddress. Specifies the network address used by the network adapter. If a multicast address or a broadcast address is specified, the adapter uses the default MAC address.
Example:
[BXND20X]DriverName = "BXND20X$"BusNum = 3DevNum = 14PortNum = 2LineSpeed = 1000Duplex = FullNodeAddress = 001020304050