Problem with boot cd

I need to create a boot cd that contains three different network cards.  I did the google search, I tried several options including PE builder but no success.  I finally found a solution that worked at http://help.ischool.washington.edu/faqs/12_29_en.html but for whatever reason, after the initial success, my boot disks aren't working any longer.  I know, it sounds odd but I am getting a Protocol.ini error.

Protocol.ini Pro0001E: Invalid option
Protocol manager not present

I'm not sure what the problem is (hence the posting here).  I've copied protmon.dos, protman.exe and protocol.ini from a couple of different places back to the floppy disk and tried to boot from it before I burn it to a disc.  Please let me know what to try next.  Thanks for the help.
LVL 9
samiam41Asked:
Who is Participating?
 
Irwin SantosConnect With a Mentor Computer Integration SpecialistCommented:
In case you need to make another bootdisk...visit this site
http://www.allbootdisks.com/
0
 
Irwin SantosComputer Integration SpecialistCommented:
do you have the proper paths setup to point to the exact location of your net driver?
0
 
samiam41Author Commented:
I have an e100b and 3c90x folder in the root of A:\.  Also in the root are the various dos files (autoexec.bat, command.com, config.sys, io.sys, mouse.com, mouse.ini, mscdex.exe, msdos.sys, netbind.com, oakcdrom.sys, protman.dos, protman.exe and protocol.ini)

--<Autoexec.bat>--
@echo off
SET TZ=GHO+08:00
mscdex /L:D /d:mscd001
MOUSE.COM
\net\netbind.com
echo Loading Ghost...
D:
cd \ghost
GHOST.EXE -nousb

--<Config.sys>--
 [menu]
MENUITEM=3C90X, 3Com - Various
MENUITEM=E100B, Compaq - Intel Pro 100

[FROMFLPY]

[FROMCD]

[COMMON]
DEVICE=OAKCDROM.SYS /D:mscd001
LASTDRIVE = Z

[3C90x]
DEVICE=\3c90x\protman.dos /i:\3c90x
DEVICE=\3c90x\dis_pkt.dos
DEVICE=\3c90x\EL90X.dos

[E100B]
DEVICE=\E100B\protman.dos /i:\B57
DEVICE=\E100B\dis_pkt.dos
DEVICE=\E100B\E100B.dos
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
samiam41Author Commented:
Correction on the E100B line.  It should read:

DEVICE=\E100B\protman.dos /i:\e100b
0
 
Irwin SantosComputer Integration SpecialistCommented:
what's in your protocol.ini?  (I suggest re-download the driver for this, maybe something got messed up). It says invalid parameter and it could be something was trying to start.... like that last line that you have for example..

DEVICE=\E100B\protman.dos /i:\e100b

could be the /i switch (arbitrary example)
0
 
nobusCommented:
did you try making a new bootdisk? the old floppy can be bad.
0
 
samiam41Author Commented:
This is the protocol.ini file from the b57 driver.

[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername=B57$


nobus->  I ended up using several different floppies.  As the frustration grew, the floppy I was using at the time meet it's demise.  So, I never used the same floppy more then a few times.
0
 
samiam41Author Commented:
**Thank you to all for your suggestions and time.  Late last night an engineer from another agency stopped by and we ended up using his boot discs.  I am closing this topic and rewarding all points to irwinpks.  

Sorry we didn't find a solution but I had to get the XP roll-out back on schedule.  Take care!
0
 
Irwin SantosComputer Integration SpecialistCommented:
cool.. thank you!
0
All Courses

From novice to tech pro — start learning today.