DOS Boot from the USB CD-ROM
I would like to boot DOS from the USB CD-ROM to run a powerquest restore utility for restore the system on HDD. The system without FDD or internal CD-ROM.
I use nero 6 to make a bootable CD-ROM with FDD emulation (The usbaspi.sys, usbcd.sys and with correct config.sys and autoexec.bat included).
While the booting, the start up found the CD-ROM then unable to load the other files and command.com
I got a message like this one :
VID057B_PID0000 FS
VID04BB_PID0201 FS
ID:0 LUN:0 = DVD/CDRW RW9120 1.36
The following file is missing or corrupted: USBCD.SYS
There is an error in your CONFIG.SYS file on line 5
The following file is missing or corrupted: COMMAND.COM
Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
A>
I try many methods but unable to solve. Please help!!!
To search on google, and found some people have similar issue and post on web, but no one can answer..
I use nero 6 to make a bootable CD-ROM with FDD emulation (The usbaspi.sys, usbcd.sys and with correct config.sys and autoexec.bat included).
While the booting, the start up found the CD-ROM then unable to load the other files and command.com
I got a message like this one :
VID057B_PID0000 FS
VID04BB_PID0201 FS
ID:0 LUN:0 = DVD/CDRW RW9120 1.36
The following file is missing or corrupted: USBCD.SYS
There is an error in your CONFIG.SYS file on line 5
The following file is missing or corrupted: COMMAND.COM
Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
A>
I try many methods but unable to solve. Please help!!!
To search on google, and found some people have similar issue and post on web, but no one can answer..
ASKER
The boot image is a bootable floppy diskette, in Nero 6, you can choose the floppy disk as the boot image source.
I make the bootable CD many times, it always work well on normal IDE CD-ROM.
I make the bootable CD many times, it always work well on normal IDE CD-ROM.
Good and the files usbaspi.sys, usbcd.sys and command.com are inside the bootable floppy disk image?
I think that usbaspi is confliclting with the floppy emulation. That is, to boot dos from a cd you don't need usbaspi/usbcd at all. Just create a boot floppy(image) , put it on a cd and when you boot you will see those files as drive a: (and you won't see any other file on the cd, unless you load some cd driver). Probably the usbaspi is preventing dos to see the files in the floppy image. Try booting with a stepbystep confirmation and skip usbaspi.sys.
I think that usbaspi is confliclting with the floppy emulation. That is, to boot dos from a cd you don't need usbaspi/usbcd at all. Just create a boot floppy(image) , put it on a cd and when you boot you will see those files as drive a: (and you won't see any other file on the cd, unless you load some cd driver). Probably the usbaspi is preventing dos to see the files in the floppy image. Try booting with a stepbystep confirmation and skip usbaspi.sys.
Sorry to jump in here guys..
lbertacco,
I have tried making a .js url changer and logger, but have failed..if you get a second could you take a look.
https://www.experts-exchange.com/questions/20972869/URL-Change-and-try-then-log-results.html
Thanks,
Caiapfas
lbertacco,
I have tried making a .js url changer and logger, but have failed..if you get a second could you take a look.
https://www.experts-exchange.com/questions/20972869/URL-Change-and-try-then-log-results.html
Thanks,
Caiapfas
ASKER
I'm also thinking about the usbaspi.sys could cause the problem, but I need an alternative to solve my situation.
Below are the tests I have done
1. Bootable CD without any CD-ROM driver, the powerquest software support it on normal IDE CD-ROM, but cannot work on USB CD-ROM. -> Stop on booting.
2. Bootable CD with IDE CD-ROM driver -> Booting then cannot identify the CD-ROM - result as expect
3. Bootable CD with usbaspi.sys CD-ROM driver -> The problem I get now.
Below are the tests I have done
1. Bootable CD without any CD-ROM driver, the powerquest software support it on normal IDE CD-ROM, but cannot work on USB CD-ROM. -> Stop on booting.
2. Bootable CD with IDE CD-ROM driver -> Booting then cannot identify the CD-ROM - result as expect
3. Bootable CD with usbaspi.sys CD-ROM driver -> The problem I get now.
I have an idea which _might_ work, however are you sure that, provided that you can boot with usbaspi/usbcd loaded, then powerquest would be able to access the cd?
If you are not sure, I think you should verify this beforehand (e.g. make a small dos bootable partition on hd and copy usb/aspi/cd and powerquest there and see if it works).
If powerquest works with usbaspi than you could:
- make bootable floppy that contains the files usbaspi/cd but doesn't load them
- this floppy must create a ramdrive (say e:) in config.sys and copy everything from a: to e: in autoexec.bat
- after copying from a: to e:, autoexec changes current drive to e: (at this point you don't need to access the cd anymore) and then loads usbaspi/cd.
There is a program that lets you load .sys driver from autoexec however I'm not sure that this program is compatible with recent versions of msdos. I'll try to find out if it's downloadable from somewhere (I think it was from the MSDOS Bible) and will let you know asap. However I think this solution has just 40% probability to work.
If you are not sure, I think you should verify this beforehand (e.g. make a small dos bootable partition on hd and copy usb/aspi/cd and powerquest there and see if it works).
If powerquest works with usbaspi than you could:
- make bootable floppy that contains the files usbaspi/cd but doesn't load them
- this floppy must create a ramdrive (say e:) in config.sys and copy everything from a: to e: in autoexec.bat
- after copying from a: to e:, autoexec changes current drive to e: (at this point you don't need to access the cd anymore) and then loads usbaspi/cd.
There is a program that lets you load .sys driver from autoexec however I'm not sure that this program is compatible with recent versions of msdos. I'll try to find out if it's downloadable from somewhere (I think it was from the MSDOS Bible) and will let you know asap. However I think this solution has just 40% probability to work.
ASKER
That's a good idea and worth to try. Thanks! :-)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks !!!
The devload.exe can load device driver successful; previously I use IBM PC DOS synaload.com to load but failed.
Now I can access the usb cd-rom.
But the usbaspi.sys+usbcd.sys seems only support usb 1.1, so the speed is extreme slow while restoring data from CD-ROM to hard disk.
Do you know any other DOS usb driver can support usb 2.0?
The devload.exe can load device driver successful; previously I use IBM PC DOS synaload.com to load but failed.
Now I can access the usb cd-rom.
But the usbaspi.sys+usbcd.sys seems only support usb 1.1, so the speed is extreme slow while restoring data from CD-ROM to hard disk.
Do you know any other DOS usb driver can support usb 2.0?
This supports usb2 high-speed for sure. Be careful not to specify /o or /u options otherwise high-speed is disabled.
http://www.computing.net/dos/wwwboard/forum/13288.html
http://www.computing.net/dos/wwwboard/forum/13288.html
ASKER
Thanks,
I've found that's the Panasonic usbaspi.sys version issue
V2.06 will only usb 1.1 speed
V2.15 can speed to usb 2 download here
http://panasonic.co.jp/pcc/products/drive/combi/kxlcb35an/license.html
I've found that's the Panasonic usbaspi.sys version issue
V2.06 will only usb 1.1 speed
V2.15 can speed to usb 2 download here
http://panasonic.co.jp/pcc/products/drive/combi/kxlcb35an/license.html
Hi
I have a variation of this error. I'm building a boot CD-ROM for a SONY notebook that has an internal USB CD drive. I was successful in using the USBASPI.SYS driver to build a boot FLOPPY that works fine in the USB floppy drive.
I then used Nero to burn a boot CD using my boot floppy as the image. When I tested the CD it generated the error above. I investigated the devload method but don't see how it will work in this situation.
Referencing a post above by Ibertacco I believe the USBASPI.SYS is interferring somehow. I can, of course, remove the reference to USBASPI.SYS and use the floppy files for booting. I need a bit more space on the CD for more files than will fit on the 1.44 floppy.
It's really odd that the CONFIG.SYS and AUTOEXEC.BAT seem to load on booting the CD but then all goes south when it finds the CD during the USB drive "search"...then fails with the error.
The following file is missing or corrupted: USBCD.SYS
There is an error in your CONFIG.SYS file on line 5
The following file is missing or corrupted: COMMAND.COM
Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
Thanks for any thoughts.
Terry
I have a variation of this error. I'm building a boot CD-ROM for a SONY notebook that has an internal USB CD drive. I was successful in using the USBASPI.SYS driver to build a boot FLOPPY that works fine in the USB floppy drive.
I then used Nero to burn a boot CD using my boot floppy as the image. When I tested the CD it generated the error above. I investigated the devload method but don't see how it will work in this situation.
Referencing a post above by Ibertacco I believe the USBASPI.SYS is interferring somehow. I can, of course, remove the reference to USBASPI.SYS and use the floppy files for booting. I need a bit more space on the CD for more files than will fit on the 1.44 floppy.
It's really odd that the CONFIG.SYS and AUTOEXEC.BAT seem to load on booting the CD but then all goes south when it finds the CD during the USB drive "search"...then fails with the error.
The following file is missing or corrupted: USBCD.SYS
There is an error in your CONFIG.SYS file on line 5
The following file is missing or corrupted: COMMAND.COM
Type the name of the Command Interpreter (e.g., C:\WINDOWS\COMMAND.COM)
Thanks for any thoughts.
Terry
What did you use a boot image?