We are not forcing line speed or duplex -- those values are definitely auto-negotiated in Windows, and should be in DOS also (I know the values are correct, because the switch it plugs into is 100Mbps / full-duplex).
The actual INI files are below.
------
Broadcom disk's protocol.ini:
; Protocol.ini section for the Broadcom Ethernet NDIS2
[B57]
DriverName = "B57$"
; (Bunch more comments)
------
E1000B disk's protocol.ini:
[network.setup]
version=0x3110
netcard=E1000$,1,MS$ELNK16,1
transport=tcpip,TCPIP
lana0=ms$elnk16,1,tcpip
[ms$elnk16]
drivername=E1000$
; iobase=0x300
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ms$elnk16
LANABASE=0
------
And now that I think about it, I may have found the problem. With the E1000B disk, we lifted protocol.ini from a *REALLY OLD* (but working) NT4-Server-created bootdisk, and just changed a few fields to match each successive driver. (That's why the E1000B disk's protocol.ini still has references to MS$ELNK16 in it. The original disk used an EtherLink16 driver, for a really old network card.)
When I made the Broadcom disk, I just copied protocol.ini from the Broadcom driver ZIP file, basically because it existed and I forgot about the edits we used to do. I bet I need to copy protocol.ini from the old disk and change the same field names, rather than completely replace it.
I'll have to try that tomorrow. I'll let everybody know how it goes, of course. Thanks for the idea! |
