DOS Boot with Network Support

Hi,

I have recently managed to create a Ghost Boot disk which allows multiple network card choices when booting from a CD to use ghost.
The problem is, we have a number of Toshiba Tecra M3 Notebooks with Marvell Yukon NIC's in them. This presents a problem as the driver supplied by Toshiba and Marvell do not help a great deal.

The boot disk contents can be downloaded at: http://www.computeonline.com/ghost.zip
You need to create a Windows 98 Boot Disk and then copy the contents of the zip onto the root of the floppy. You can then use the floppy as a boot disk for Nero to use to create a boot CD.

I get the following error messages (They appear in this order, but do have text between them):

PRO0003E: Protocol.ini file open failure

Protocol Manager not present

LTE0002E: Protocol Manager has not been loaded

Any ideas?


Thanks
Chris
LVL 1
unitedmpAsked:
Who is Participating?
 
jsugiCommented:
I am assuming that  the other nics work when you use your boot disk.  Because although I have not tried making a boot disk from the file you provided everything looks very similar to the boot disk that I have for work.  Looking at the config.sys and and autoexec.bat everything looks correct.  The only thing that I can think of is that it does not like your drivers for that nic or one of those files are corrupt.
The only thing that I would try would be to try different versions of nic drivers that you can find.  Not sure if you already tried that already.

Well good luck
0
 
unitedmpAuthor Commented:
Only 1 version of the driver exists.

Toshiba tell me they successfully use it for production lines.

I have downloaded the driver 2 times, and had it sent to me from Toshiba.

I have replaced the netbind, protman and dis_pkt files aswell just to be sure and also the protocol.ini file.

The error points towards a problem with opening the protocol.ini file. Not sure why tough. Am trying to find a USB floppy so I can do some tests and be sure of the problem.
0
 
unitedmpAuthor Commented:
I figured it out.

I don't know how or why this just jumped into my head and voila .. instant answer.

This is the contents of the Config.sys file with the problem:

[menu]
MENUITEM=VEi8, HP Vectra VEi8
MENUITEM=VL400, HP Vectra VL400
MENUITEM=D510, HP/Compaq D51x Series
MENUITEM=D530, HP D530 Series
MENUITEM=DC7100, HP Evo DC7100 Series
MENUITEM=TECRAM2, Toshiba Tecra M2 Notebook
MENUITEM=TECRAM3, Toshiba Tecra M3 Notebook

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


[VL400]
DEVICE=\3c90x\protman.dos /I:\3c90x
DEVICE=\3c90x\dis_pkt.dos
DEVICE=\3c90x\EL90X.dos

[DC7100]
DEVICE=\b57\protman.dos /I:\B57
DEVICE=\b57\dis_pkt.dos
DEVICE=\b57\B57.dos

[VEi8]
DEVICE=\E100B\protman.dos /I:\E100B
DEVICE=\E100B\dis_pkt.dos
DEVICE=\E100B\E100B.dos

[D530]
DEVICE=\b57\protman.dos /I:\B57
DEVICE=\b57\dis_pkt.dos
DEVICE=\b57\B57.dos

[D510]
DEVICE=\E100B\protman.dos /I:\E100B
DEVICE=\E100B\dis_pkt.dos
DEVICE=\E100B\E100B.dos

[TECRAM2]
DEVICE=\E1000\protman.dos /I:\E1000
DEVICE=\E1000\dis_pkt.dos
DEVICE=\E1000\E1000.dos

[TECRAM3]
DEVICE=\yukon\protman.dos /I:\yuknd
DEVICE=\yukon\dis_pkt.dos
DEVICE=\yukon\yuknd.dos

--- END OF FILE ---

The problem is with this line:
DEVICE=\yukon\protman.dos /I:\yuknd

It appears"/I:\yuknd" should be pointing to the directory name not the driver name.

Resolution to my problem, was changing this line to:
DEVICE=\yukon\protman.dos /I:\yukon


Amazing how something so small and simple can cause such an irritating problem.
Hope this helps anyone else who may experience the same problem.


Cheers
Chris
0
 
jsugiCommented:
hey congrats on finding the answer to your problem.  I was looking at the file to see if something was off, but I didn't see anything wrong with it.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.