ENVascension
asked on
PROTOCOL.INI Issue
I'm trying to wipe and reinstall Windows XP Tablet Edition 2005 on a tablet PC which has no onboard drives other than a hard drive. I used the instructions I found at http://www.lockstockmods.net/2008/04/26/easy-way-to-pxe-boot-windows/ for booting to the network. As part of the process, I had to add a custom driver to the image (which is an image of Bart's Network Boot Disk). The NIC driver loads ok and I'm accepting all the defaults on the first boot like the instructions say, but when it tries to do a net init and load PROTMAN.DOS, I get the following error:
PRO0008E: Invalid decimal digit in PROTOCOL.INI file
Error loading device driver PROTMAN.DOS.
Error 7306: The driver failed to initialize.
When I examine the PROTOCOL.INI file, it appears that it is being dynamically generated by the MSNET.BAT file included with Bart's Network Boot Disk, so I'm not sure what I can do to avoid this problem. I'm including what's in the PROTOCOL.INI file. I had to retype by hand since there's no way to copy and paste the file.
PRO0008E: Invalid decimal digit in PROTOCOL.INI file
Error loading device driver PROTMAN.DOS.
Error 7306: The driver failed to initialize.
When I examine the PROTOCOL.INI file, it appears that it is being dynamically generated by the MSNET.BAT file included with Bart's Network Boot Disk, so I'm not sure what I can do to avoid this problem. I'm including what's in the PROTOCOL.INI file. I had to retype by hand since there's no way to copy and paste the file.
; Protocol.ini generated by msnet.bat
[network.setup]
version=0x3110
netcard=nu2$nic,1,NU2$NIC,1
transport=tcpip,TCPIP
lana0=nu2$nic,1,tcpip
[tcpip]
NBSessions=6
DriverName=TCPIP$
BINDINGS=NU2$NIC
LANABASE=0
DisableDHCP=0
[pktdrv]
DriverName=PKTDRV$
BINDINGS=NU2$NIC
intvec=0x60
chainvec=0x66
[NU2$NIC]
; OEMSETUP.INF for Broadcom Ethernet Adapter
[netcard]
B57$="Broadcom Ethernet", 0, NDIS, Ethernet, REAL, B57$_ini, B57$_ini
[B57$_ini]
DriverName=B57$
device=B57$.dos, @INST\B57.dos
NETDIR=5:B57.dos
ASKER
I have already built a new cab file for my NIC and the driver appears to load without any problems. The issue I'm encountering ocurrs ater the NIC driver loads.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That seems to have solved the problem. The default version of the B57.ini file that came with the driver from the manufacturer had additional lines in it. When I commented out everything except for the DriverName line (as illustrated in your .ini file), everything loaded properly. Thanks for the help.
Looks like it's moaning about TCP/IP addresses
http://support.microsoft.com/kb/123357
Also see http://service1.symantec.com/SUPPORT/on-technology.nsf/0437f27e11eaa7ef88256ebb0049cfe6/aef37d51a77dcf2e8825734e0059c2f1?OpenDocument
http://www.computing.net/answers/dos/invalid-decimal-in-protocolini/11653.html
http://support.microsoft.com/kb/123357
Also see http://service1.symantec.com/SUPPORT/on-technology.nsf/0437f27e11eaa7ef88256ebb0049cfe6/aef37d51a77dcf2e8825734e0059c2f1?OpenDocument
http://www.computing.net/answers/dos/invalid-decimal-in-protocolini/11653.html
I think I ran into the same problem with barts network boot disk. What you have to do is download cabarc from Barts Network Boot Disk website, and also download the latest drivers for the laptop that you're building. Then build your own cab file for the network card.