> Back to Contents Page

> ## NDIS2 Driver Software: Broadcom NetXtreme® 57XX User Guide

> Preinstallation Requirements

> Installing the NDIS2 Driver Software for Use in MS-DOS Environments

> Installing the NDIS2 Driver Software for Use in IBM-OS/2 Environments

> Configuring the NDIS2 Driver Software

> Using Keywords for the B57.dos Drivers

> ### Preinstallation Requirements

> 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 in MS-DOS Environments

> 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 disk)
> - Access to the Broadcom NDIS2 driver file (B57.dos). This file is located on the installation CD.

> 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

> 1. Create a folder called NCADMIN in the root of the C drive.
> 2. Copy the NCADMIN.CN_, NCADMIN.EX_, and NCADMIN.HL_ files from the I386 folder on the Windows NT Server 4.0 CD-ROM.
> 3. Open a command prompt window and change the directory to C:\NCADMIN.
> 4. Type expand -r ncadmin.* and press ENTER.
> 5. Type exit and then press ENTER.
> 6. Open Windows Explorer.
> 7. Open the NCADMIN folder and double-click ncadmin.exe.
> 8. 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

> 1. Edit A:\Net\Protocol.ini with Notepad or a similar text editor.
> 1. Change DriverName=$ to DriverName=B57$.
> 2. 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

> 2. Edit A:\Net\System.ini.
> 1. Change netcard= to netcard=b57.dos.
> 2. 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

> 3. Copy B57.dos to A:\Net.
> 4. 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

> 5. 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 NDIS2 Driver Software on the Hard Disk

> To install the NDIS2 driver software on the hard disk

> 1. Verify that the system has Microsoft LAN Manager 2.2 installed, with a protocol such as NetBEUI configured.
> 2. Create a folder on your disk to store the NDIS 2.01 driver.

> Example: C:\LANMAN

> 3. Copy the B57.dos file to this folder.
> 4. 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

> 5. 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

> 6. 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$"

> 7. 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.

> ### Installing the NDIS2 Driver Software for Use in IBM-OS/2 Environments

> To perform this installation you must have a disk that contains the Broadcom NDIS2 driver files (B57.NIF and B57.OS2). These files are located on the installation CD.

> To install the NDIS2 driver software

> 1. At the OS/2 desktop, double-click System Setup.
> 2. Select MPTS Network Adapter and Protocol Services, and then click OK.
> 3. In Multi-Protocol Transport Services, click Configure.
> 4. In Configure, verify that LAN Adapters and Protocol is selected, and then click Configure.
> 5. In Adapter and Protocol Configuration under Network Adapters, click Other Adapters.
> 6. Insert the disk that contains the B57.NIF and B57.OS2 files, and then click OK.
> 7. In Adapter and Protocol Configuration under Network Adapters, search for and select Broadcom NetXtreme Gigabit Ethernet, and then click Add.
> 8. In Protocols, select IBM OS/2 NETBIOS, and then click Add.
> 9. Click OK.
> 10. In Multi-Protocol Transport Services, click Close, and then click Exit.
> 11. Restart the system.

> ### 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 2 (see Broadcom Advanced Control Suite 2) 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:

>     [B57]

>     DRIVERNAME = B57$

>     BUSNUM = 3

>     DEVNUM = 10

>     [B57_2]

>     DRIVERNAME = B572$

>     BUSNUM 3

>     DEVNUM 11

>     [B57_3]

>     DRIVERNAME = B573$

>     BUSNUM 3

>     DEVNUM 12

>     [B57_4]

>     DRIVERNAME = B574$

>     BUSNUM 3

>     DEVNUM 13

> 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:

>     [B57]

>     DRIVERNAME = B57$

>     BUSNUM = 3

>     DEVNUM = 10

>     PORTNUM = 0

>     LINESPEED = 100

>     DUPLEX = FULL

>     NODEADDRESS = "001020304050"

> ### Using Keywords for the B57.dos Drivers

> The Protocol.ini file contains certain keywords that are used by the B57.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 system 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:

>     [B57]

>     DriverName = "B57$"

>     BusNum = 3

>     DevNum = 14

>     PortNum = 2

>     LineSpeed = 1000

>     Duplex = Full

>     NodeAddress = 001020304050

> Back to Contents Page