中国DOS联盟

Generally, I use the following methods to load in the command line or batch processing. Both the floppy disk boot method and the virtual boot floppy disk boot method of the hard disk can drive successfully. However, the U disk boot method does not work.

ADDEV VIDE-CDD.SYS /D:IDE-CD
SHSUCDX /D:?IDE-CD

Or use CTLOAD

In the U disk boot environment, such as after booting, it shows A:\>, and after loading the CD-ROM driver in the command line or batch processing, it is not successful, and the original A drive mapped by the U disk in DOS disappears, so it is impossible to enter the U disk again.

It is possible in CONFIG.SYS, but I need to do it in the command line (prompt), because sometimes I need to add the ISO virtual CD-ROM file. If the CD-ROM driver is loaded in CONFIG.SYS, then the ISO driver can be loaded in the command prompt or batch processing, and then my difficulty is solved.

This doesn't seem to be anything special, is it that the program's path is not there?

Under the DOS environment (at the command line) after booting with a USB flash drive, when the CD-ROM driver is loaded, the original A drive mapped from the USB flash drive in DOS disappears, but it is okay under the virtual boot floppy disk startup method from a floppy disk or hard disk.

Because the boot disk (XUSBOOT) I made also has an ISO loading program, and I solved it by loading with CONFIG, but the user raised that after loading the CD-ROM driver, the ISO cannot be loaded anymore.