Installing the NDIS2 Driver Software for Use on MS-DOS Platforms
Installing the NDIS2 Driver Software for Use on IBM OS/2 Platforms
Using Keywords for the B57.dos and B57.OS2 Drivers
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 or Warp Version 4 for IBM OS/2) must already be running on your computer.
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.
To perform this installation you must have the following items:
![]() |
Notes:
|
To create a startup disk
To modify the startup disk
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=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 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 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
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=B57.dos
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes
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
files=30
device=a:\net\ifshlp.sys
lastdrive=z
To install the DOS NDIS2 Driver Software on the hard disk
Example: C:\LANMAN
DEVICE = C:\LANMAN\PROTMAN.DOS
DEVICE = C:\LANMAN\B57.DOS
DEVICE = C:\LANMAN\NETBEUI.DOS
C:\ LANMAN\NETBIND.EXE
C:\LANMAN\NET START WORKSTATION
C:\LANMAN\NET USE <drive letter>: \\<server name>\<resource name>
Example
[PROTOCOL MANAGER]
DriverName = PROTMAN$
[NETBEUI_XIF]
DriverName = netbeui$
BINDINGS = B57
[B57]
DriverName = "B57$"
![]() |
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. |
To perform this installation you must have a floppy disk that contains the Broadcom NDIS2 driver files (B57.NIF and B57.OS2). Obtain these files from the support website.
To install the NDIS2 driver software
The Protocol.ini file contains certain keywords that are used by the B57.dos and B57.OS2 drivers. These keywords are listed below:
BusNum. Specifies the PCI bus number on which the network controller is located. Requires a decimal number having a value ranging from 0 to 255.
DevNum. Specifies the device number assigned to the network controller 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 controllers are installed in the computer 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 a decimal number having a value of either 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and is achievable only via auto-negotiation. For the sake of simplicity, however, the driver performs auto-negotiation when the line speed is set to a value of 1000.
Duplex. Specifies the duplex mode of the network controller. 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 controller defaults to Auto-negotiatiate mode.
NodeAddress. Specifies the network address used by the network controller. If a multicast address or a broadcast address is specified, the controller uses the default MAC address.
Example
[B57]
DriverName = "B57$"
BusNum = 3
DevNum = 14
PortNum = 2
LineSpeed = 1000
Duplex = Full
NodeAddress = 001020304050