China DOS Union

After booting with the USB flash drive, I loaded
device=USBASPI.SYS /e /v /w
device=aspidisk.sys
to identify my USB hard drive. But after the usbaspi, the problem came up. After USBaspi ran (the original U was the C drive), I couldn't find the contents on the USB flash drive. The things on the USB flash drive became garbled in DOS, and then I couldn't find the aspidisk.sys file or the command.com!
I think it was because Usbaspi.sys re - identified the USB flash drive, making the USB flash drive recognized normally by the original motherboard abnormally. So I used the memory disk of Grub to call the IMG file on the USB flash drive to load USBASPI and ASPIDisk, and it was normal then. But after loading, the C drive, which was the USB flash drive, still couldn't be used. The USB flash drive was assigned another drive letter. I wonder if there are other solutions?

Also, why can't ISOEMU 1.09 call ISO files on my external hard drive? My external hard drive is FAT32!

I have encountered the problem mentioned by the post owner. I think a feasible solution is: if the motherboard supports USB boot, then do not load new USB drivers.

Agree with the statement above. ISOEMU currently does not support USB hard drives, so it naturally cannot recognize the FAT32 partitions on USB hard drives!

But my motherboard doesn't support USB HDD, so I can't see my external hard drive, only the USB flash drive.

Just a thought: transfer the command interpretation command of COMMAND.com from the USB - located drive letter to the RAM - DISK - located drive letter, and the RAM - DISK stores the required USB drivers and tools, then manually load the USB drivers. The premise is that the content of the RAM - DISK is not lost.

The author of USBoot said in its PDF document: The key is the BIOS. The USB-FDD, USB-HDD, USB-ZIP in most motherboard BIOSes are all in name only, and simply do not detect the USB flash drive. I have 3 computers and 3 USB flash drives. Only 1 computer supports USB-ZIP and only recognizes 32M.