China DOS Union

Originally posted by xiaoyunwang at 2008-11-18 07:29 PM:
I found a BUG inside, which is caused by modifying IO.SYS to be immune to logical locks, resulting in inaccurate or even non-recognition of FAT32 partitions under DOS. After adding ifs, it can be recognized, but when exiting...

Just...............

Thanks! No problem found when loading with the image!
Looking forward to the new version of qboot...

Bump it.
I have no problem loading the image on the USB flash drive.
Releasing directly to the USB flash drive and booting is slow.
It is suggested that the new qboot change the edit, add pc.exe or vc.exe, and add a general CD-ROM driver.
As a bridge between DOS and XP (such as being able to enter XP through qboot after changing and backing up your own files under DOS), qboot is very good, so looking forward to it!

[ Last edited by julon on 2008-11-21 at 07:35 ]

Originally posted by julon at 2008-11-21 07:33 AM:
Give it a thumbs up.
I have no problem loading the image on the USB flash drive.
Releasing directly to the USB flash drive for booting is slow.
It is suggested that the new qboot should change edit, add pc.exe or vc.exe, and add a universal CD-ROM driver.
As a bridge between DOS and XP...

This is not planned to be changed for the time being. If we change to using PSI to analyze and convert the path, it means that all the original batch processing code will be invalidated and needs to be rewritten from scratch. I'm too lazy to do it. In Qboot, using usecd can drive the universal IDE/ATAPI/SATA CD-ROM. Using useusb (or adding the /r parameter can identify multiple partitions of the USB flash drive. The reason is that the default Di1000dd.SYS can only assign one drive letter, and after adding /r, using Aspidisk.sys to assign drive letters can assign multiple drive letters, but the compatibility is not as good as Di1000dd.sys). You may need to update USBASPI.SYS to version 2.27. This version 2.24 has some compatibility issues (some USB2.0 cannot be driven with version 2.24, but can be driven with version 2.20 or the latest version 2.27). As for that edit, heh, that's the smallest editor in the world, which once won an award in PC Magazine. "Edit file path" to load for editing, and after editing, just press Alt+X to exit, and the modification takes effect immediately (you can press F1 in the editor to get help). As for VC, PC and other GUI management tools, that's an extra matter. If everything is required, it will become a "toolbox". Please add it yourself. Also, don't forget that there is a BUG in that IO.SYS (caused by modifying IO to be不怕logical lock), which needs to be replaced with others (such as the webmaster's IO.SYS or the original one). Also, the update of Grub.exe is done.

[ Last edited by xiaoyunwang on 2008-11-21 at 09:16 ]

Thanks! Then I'll DIY it myself, and maybe recommend this tool on the Wuyou Forum.

Yesterday, I converted the partition file system of USB flash drive partition 2 to FAT32. In DOS, this partition cannot be recognized indeed, and IFS didn't work. This might be due to poor compatibility of PQ partition. There are also examples on the Internet where USB flash drives became unusable after being converted by PQ. For other tool - partitioned hard drives as FAT32, QBOOT is well recognized, including my old computer partitioned by DM.

Today, when setting up the BIOS boot, I set the USB drive to HDD mode. After inserting the USB drive, the computer boots from the hard disk. (If set to Floppy + ZIP mode, it boots from the USB drive.) When entering Qboot, it can read the two partitions of the USB drive (FAT, FAT32), and the drive number is after the C drive. Does this mean that the recognition of the FAT32 partition is related to the motherboard rather than the software (Qboot)?

Originally posted by julon at 2008-11-25 06:32 PM:
Today, I set up the BIOS boot and set the USB drive to HDD mode. I inserted the USB drive, but the computer booted from the hard drive. (If set to Floppy + ZIP mode, it boots from the USB drive) Entering qboot, it can read the two partitions of the USB drive (FAT, FAT...

This, I don't know very well. If qboot can recognize the two partitions of the USB drive, it is using usbaspi + aspidisk for driver. In very few motherboards, this driver will cause a system crash. These days, my motherboard is broken, and I have replaced it with a new one. The BIOS seems to support USB boot. I have never made a USB drive bootable, and I don't dare to use usboot or flashboot, for fear of damaging the USB drive.

Original tools can be used to create USB-ZIP bootable disks. USboot version 1.7 should be used (it can only add the boot). Flashboot is ineffective on my USB flash drive. It has very good security. If the USB flash drive needs a boot tool disk, PE, etc., it is best to write the GRUB boot.