|So far the following DOS boot disk has worked on every system I have tried it on (3 homebrew desktops, a Dell desktop, and a Sony notebook). I found this site 2 weeks ago while trying to get DOS to recognize a Sony Q120 CD-R/DVD-R drive mounted in a Gallaxy external case. The disk works to write and read to CDs with Ghost 2003 but not yet with DVDs.|
I quickly found that none of the packages that reportedly work with CDs, HDs, floppies, and memory sticks would work with any of my systems. Since I only wanted CD support (and hopefully DVD), I finally built a floppy with just 10 files that (so far) is a universal DOS USB boot disk. In the process I learned the following:
There are 3 basic requirements for a USB CD drive to work in DOS.
1. The config.sys file must contain a valid name for the USB CD drive.
USBCD001 works with a Sony Q120 CD-R/DVD-R drive in a Galaxy
external case. UBCD001 is not a file name and it is not on the boot
disk except in other files. However, if an unacceptable drive name
is used, DOS will report "File not found".
MSCD001 is not an acceptable name for the USB drive. It only
works for an internal IDE drive. Using a cute name like "tomato"
might work if you are clever enough to rewrite the device driver.
I do not have the time.
2. Next, the config.sys file must contain the necessary commands and
switches to mount/map the drive. You can see when the drive is mounted/mapped because the firmware name (SONY Q120, not USBCD001) prints on the screen.
3. After the drive is mounted/mapped, MSCDEX, which runs from the
autoexec.bat file, assigns a DOS drive letter to the mounted/mapped
If the drive gets mounted/mapped but no DOS drive letter has been
assigned, GHOST 2003 can still find the drive and write to it.
However, neither GHOST nor DOS will be able to find the files
unless the disk is placed into a fully operational drive
(e.g. internal IDE).
The boot disk started as a Win'98 emergency boot disk (created with EBD on the
The disk must have the following ten files:
drvspace.bin hidden system file
io.sys hidden system file
msdos.sys hidden system file
usbcd.sys 5,509 bytes (may be named usbcd1.sys on sites with multiple versions) usbaspi.sys 39,093 bytes (from version 2.15, may be named usbaspi1.sys)
At boot, DOS first runs the config.sys
My config.sys has the following 20 lines ending with "last drive=z":
menuitem=USB1, Start with USB CD-ROM support. (Pause allows plugging in drive)
menuitem=CD, Start with IDE CD-ROM support. (Files deleted. See REM below.)
rem device=usbcd.sys /D:mscd001
rem Temporarily unREM the line above if you want to test the effect of using
rem the wrong drive name. Then temporarily REM the the line below.
REM all REMed out because the files were deleted to make room for GHOST
The autoexec.bat file has the following lines 6 lines ending with "mouse6":
LH mscdex.exe /d:usbcd001
SET DIRCMD=/a /og /p
REM mouse6 doesn't work with a USB mouse
(Ghost is rather difficult to use without a mouse)
After the disk worked, I added 4 other optional files:
TED (a very small text editor), DR (dirmagic), and FINDIT are useful DOS
utilities that came on a freeware disk from PC Magazine at least 15
years ago. MOUSE6 is a mouse driver. Note that to open a file with TED,
the full file name and extension must be entered and TED creates a backup
(.bak) file each time a file is edited.
Comment: There was nothing useful on Motto Hairu that I had not already found here.
Good luck. I hope this speeds up the process for someone else.