Back to Contents

NDIS2 Driver Software: Broadcom 440x 10/100 Integrated Controller User Guide

Pre-Installation Requirements

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


Pre-Installation Requirements

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


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:

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

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

      [network.setup]

      version=0x3110

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

      transport=tcpip,TCPIP

      lana0=ms$ne2clone,1,tcpip

      [MS$NE2CLONE]

      DriverName=B44$

      [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 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=B44$

    [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 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=B44$

    [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=B44.dos.
    2. Check for references to C:\NET and change C:\NET to A:\NET if necessary.

      Example SYSTEM.INI

      [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=B44.dos

    transport=ndishlp.sys,*netbeui

    devdir=A:\NET

    LoadRMDrivers=yes

  3. Copy B44.dos to A:\Net.
  4. Create the appropriate Autoexec.bat file in drive A for the chosen protocol as shown below.

    For TCP/IP

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

  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.

Example: C:\LANMAN

  1. Copy the B44.dos file to this folder.
  2. Edit the Config.sys file by adding the following lines:

    DEVICE = C:\LANMAN\PROTMAN.DOS

    DEVICE = C:\LANMAN\B44.DOS

    DEVICE = C:\LANMAN\NETBEUI.DOS

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

  4. 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 = B44

[B44]

DriverName = "B44$"

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


Back to Top

Back to Contents