NDIS2 Driver Software: Broadcom NetLink®/NetXtreme® 57XX User Guide

Before you can successfully install the NDIS2 driver software, the Broadcom NetXtreme Gigabit Ethernet adapter must be physically installed in the system. 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 system.

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

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 (B57.dos).

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.

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

Edit A:\Net\Protocol.ini with Notepad or a similar text editor.

Change DriverName=$ to DriverName=B57$.

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=0x3110

netcard=ms$ne2clone,1,MS$NE2CLONE,1

transport=tcpip,TCPIP

lana0=ms$ne2clone,1,tcpip

[MS$NE2CLONE]

DriverName=B57$

[protman]

DriverName=PROTMAN$

PRIORITY=MS$NDISHLP

[tcpip]

NBSessions=6

DefaultGateway=0

SubNetMask=255 0 0 0

IPAddress=192 168 0 1

DisableDHCP=0

DriverName=TCPIP$

BINDINGS=MS$NE2CLONE

LANABASE=0

Example: Protocol.ini file for IPX

[network.setup]

version=0x3110

netcard=ms$ne2clone,1,MS$NE2CLONE,1

transport=ms$ndishlp,MS$NDISHLP

transport=ms$nwlink,MS$NWLINK

lana0=ms$ne2clone,1,ms$nwlink

lana1=ms$ne2clone,1,ms$ndishlp

[MS$NE2CLONE]

DriverName=B57$

[protman]

DriverName=PROTMAN$

PRIORITY=MS$NDISHLP

[MS$NDISHLP]

DriverName=ndishlp$

BINDINGS=ms$ne2clone

[ms$nwlink]

DriverName=nwlink$

FRAME=Ethernet_802.2

BINDINGS=MS$NE2CLONE

LANABASE=0

Example: Protocol.ini file for NetBEUI

[network.setup]

version=0x3110

netcard=ms$ne2clone,1,MS$NE2CLONE,1

transport=ms$ndishlp,MS$NDISHLP

transport=ms$netbeui,MS$NETBEUI

lana0=ms$ne2clone,1,ms$ndishlp

lana1=ms$ne2clone,1,ms$netbeui

[MS$NE2CLONE]

DriverName=B57$

[protman]

DriverName=PROTMAN$

PRIORITY=MS$NDISHLP

[MS$NDISHLP]

DriverName=ndishlp$

BINDINGS=MS$NE2CLONE

[MS$NETBEUI]

DriverName=netbeui$

SESSIONS=10

NCBS=12

BINDINGS=MS$NE2CLONE

LANABASE=0

Edit A:\Net\System.ini.

Change netcard= to netcard=b57.dos.

Check for references to C:\NET and change C:\NET to A:\NET if necessary.

Example: System.ini file

[network]

sizworkbuf=1498

filesharing=no

printsharing=no

autologon=yes

computername=MYPC

lanroot=A:\NET

username=USER1

workgroup=WORKGROUP

reconnect=yes

dospophotkey=N

lmlogon=0

logondomain=

preferredredir=basic

autostart=basic

maxconnections=8

[network drivers]

netcard=B57.dos

transport=ndishlp.sys,*netbeui

devdir=A:\NET

LoadRMDrivers=yes

Copy B57.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:\net

a:\net\net initialize

a:\net\netbind.com

a:\net\umb.com

a:\net\tcptsr.exe

a:\net\tinyrfc.exe

a:\net\nmtsr.exe

a:\net\emsbfr.exe

a:\net\net start basic

net use z: \\SERVERNAME\SHARENAME

For IPX

SET PATH=A:\NET

A:\NET\net initialize

A:\NET\nwlink

A:\NET\NET START BASIC

net use z: \\SERVERNAME\SHARENAME

For NetBEUI

SET PATH=A:\NET

A:\NET\NET START BASIC

net use z: \\SERVERNAME\SHARENAME

Create a Config.sys file on the startup disk in drive A as shown below.

files=30

device=a:\net\ifshlp.sys

lastdrive=z

Installing 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 B57.dos file to this folder.

Edit the Config.sys file by adding the following lines:

DEVICE = C:\LANMAN\PROTMAN.DOS

DEVICE = C:\LANMAN\B57.DOS

DEVICE = C:\LANMAN\NETBEUI.DOS

Edit the Autoexec.bat file by adding the following lines:

C:\LANMAN\NETBIND.EXE

C:\LANMAN\NET START WORKSTATION

C:\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 = B57

B57]

DriverName = "B57$"

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.

Configuring the NDIS2 Driver Software

The NDIS2 driver software can be configured by adding specific optional keywords to the Protocol.ini file. If multiple (or multiport) Broadcom NetXtreme Gigabit Ethernet adapters are installed in a system, the NDIS2 driver software loads by default on the adapter/port that has a good link. If 2 or more adapters have a good link, the NDIS2 driver software loads on the adapter having the latest Device ID. If 2 or more adapters that have a good link have the same Device ID, the NDIS2 driver software loads on the adapter that is located in the slot having the lowest bus number.

NOTE: On MS-DOS platforms, it is not recommended to load the NDIS2 driver software on more than 1 adapter; the required NDIS2 protocol manager that supports multiple binds is not available in the MS-DOS environment.

If it is necessary to have the NDIS2 driver load on certain adapters in a certain order, the BusNum, DevNum, and FuncNum keywords can be used. Do not use these keywords unless you know how to configure PCI devices.

The BusNum keyword value, which represents the PCI bus number in which the adapter is located, is a decimal number ranging from 0 to 255.

The FuncNum keyword value, which represents the function (port) number of a multiport adapter, is a decimal number, with 0 representing the first port, and 1 representing the second port.

The DevNum keyword value, which represents the assigned device number, is a decimal number ranging from 0 to 31.

NOTE: At the end of the NDIS2 driver software installation process, note the BusNum and DevNum values that are displayed. Alternatively, use Broadcom Advanced Control Suite 3 to view the bus number, function (port) number, and device number assigned to each adapter (Windows users only).

Example BusNum, DevNum, and FuncNum keyword entries for loading the NDIS2 driver on multiple adapters in a certain order are shown below:

The LineSpeed keyword is used to force the speed of the network connection. The LineSpeed keyword requires a decimal number and of either 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and can be achieved 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. Forced 1000 Mbit/s speed is not needed for copper links; auto-negotiation is the proper supported configuration under the IEEE Ethernet specification.

The Duplex keyword is used to force the duplex mode of the adapter. The Duplex keyword requires a text string of either HALF or FULL. When the Duplex keyword is used, the LineSpeed keyword must also be used. If neither keyword is used, the network adapter defaults to auto-negotiation mode.

The NodeAddress keyword specifies the network address used by the adapter. If a multicast address or a broadcast address is specified, the adapter uses the default MAC address.

The FixCheckSumOff keyword turns off the driver workaround for the TCP/IP stack to recognize the ones complement version of the checksum.

Example entries for the LineSpeed, Duplex, and NodeAddress keywords are shown below: