Back to Contents Page

NDIS2 Driver Software: Broadcom NetXtreme II™ Network Adapter User Guide

Overview

Preinstallation Requirements

Installing the NDIS2 Driver Software for Use on MS-DOS Platforms

Using Keywords for the Drivers

Overview

Two drivers are discussed in this section:

The examples used in this section refer to the BXND20X driver, but also apply to the BNX2EV driver.

Preinstallation Requirements

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

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. Close the command prompt window by typing exit and then pressing ENTER.
  6. Start 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=BXND20X$.
    2. Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as IOBASE=0x300 or INTERRUPT=3, and so on.
    3. 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=BXND20X$
      
      [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=BXND20X$ 
      
      [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=BXND20X$ 
      
      [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=BXND20X.dos.
    2. Check for references to C:\NET and change C:\NET to A:\NET if necessary.
    3. 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=BXND20X.dos
      
      transport=ndishlp.sys,*netbeui
      
      devdir=A:\NET
      
      LoadRMDrivers=yes
      
  3. Copy BXND20X.dos to A:\Net.
  4. Create the appropriate Autoexec.bat file in drive A for the chosen protocol as shown below.
  5. 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
    
  6. Create a Config.sys file on the startup disk in drive A as shown below.
  7. files=30
    
    device=a:\net\ifshlp.sys
    
    lastdrive=z
    

Installing the DOS NDIS2 Driver Software on the Hard Disk

To install the DOS 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 hard disk to store the NDIS 2.01 driver.
  3. Example: C:\LANMAN

  4. Copy the BXND20X.dos file to this folder.
  5. Edit the Config.sys file by adding the following lines: 
    
    DEVICE = C:\LANMAN\PROTMAN.DOS 
    
    DEVICE = C:\LANMAN\BXND20X.DOS
    
    DEVICE = C:\LANMAN\NETBEUI.DOS
    
  6. Edit the Autoexec.bat file by adding the following lines:
  7. C:\ LANMAN\NETBIND.EXE
    
    C:\LANMAN\NET START WORKSTATION 
    
    C:\LANMAN\NET USE drive letter: \\server name\resource name
    
    
    
     
  8. Edit the Protocol.ini file (located in C:\LANMAN) to configure the driver to bind with NetBEUI or any other protocols.
  9. Example:

    [PROTOCOL MANAGER]
    
    DriverName = PROTMAN$ 
    
    [NETBEUI_XIF]
    
    DriverName = netbeui$
    
    BINDINGS = BXND20X
    
    [BXND20X]
    
    DriverName = "BXND20X$" 
    
  10. Restart the computer to complete the installation.
  11. 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 Drivers

The Protocol.ini file contains certain keywords that are used by the BXND20X.dos AND 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.

NOTE: LineSpeed is not available with the Broadcom NetXtreme II 10 Gigabit Ethernet driver.

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.

NOTE: LineSpeed is not available with the Broadcom NetXtreme II 10 Gigabit Ethernet driver.

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 = 3
DevNum = 14
PortNum = 2
LineSpeed = 1000
Duplex = Full
NodeAddress = 001020304050

FixCheckSumOff. Turns off the driver's workaround for the TCP/IP stack to recognize the 1s complemented version of the checksum.

AcceptAllMC. Informs the driver to deliver all multicast packets to the upper protocol.


Back to Contents Page