DOS Networking issue

[izzzy12k]

I am having an issue trying to back (via image) my new computer.

I have a DOS boot disk I have been using on my old computer and never had an issue.

Now with my new computer, I updated the dos drivers on the floppy to use the new computers Intel NIC, yet now I keep getting an error and am not sure what's causing it or how to fix.

Here's the error I get:
"pro0004e: A parameter does not belong to any logical module"

"Error loading device driver PROTMAN.DOS"


The error seems to happen when the "net initialize" command is executed.

Anyone know what's the cause?
Thanks,
-Iz

[izzzy12k]

Found the issue was tied to the protocol.ini file which was missing some info...

Now when the batch file executes netbind.com..
it errors out with "Error: 33 Unable to bind"

Almost there :)

[izzzy12k]

Got it fixed.. one of my [labels] had a typo in the protocol.ini

[james.barr]

I'm having this same problem...

What was the missing info from protocol.ini?

[izzzy12k]

Well initially my protocol.ini had:
; Protocol.Ini section for the Intel(R) PRO/1000 Adapters

DRIVERNAME = E1000$
SPEEDDUPLEX = 3

; NODE = "00D00C123456" ; override the burned in MAC address

; SPEEDDUPLEX = 0 ; 10Mbps half duplex
; = 1 ; 10Mbps full duplex
; = 2 ; 100Mbps half duplex
; = 3 ; 100Mbps full duplex

; SLOT = 7 ; set this for each NIC if using more than one

; CACHEFLUSH = 1 ; set this if doing an unattended installation of
; Windows NT 4.0 using this driver to make the initial
; connection


When it should have been:
[network.setup]
version=0x3110
netcard=e1000$_ini,1,e1000$_ini,1
transport=tcpip,TCPIP
lana0=e1000$_ini,1,tcpip

[e1000$_ini]
drivername=e1000$
speedduplex = 3


[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[TCPIP]
NBSessions=6
DisableDHCP= 0
drivername=TCPIP$
BINDINGS=e1000$_ini
LANABASE=0

[pktdrv]
drivername=pktdrv$
BINDINGS=e1000$_ini
intvec=0x60
chainvec=0x66
novell=no

It's possible that some of the above can be left out... but it worked and didn't wanna break what was now working :)

[james.barr]

Thanks... I'll give that a try substituting the drivername(s) and duplex settings with the relevant parameters for my card.

[izzzy12k]

Ensure you also fix the label [e1000$_ini] as that what caused my second issue. (i had left what was on the original copy of the file)

[james.barr]

Will-do. Thanks again.