USBOOT is a very famous and widely used USB flash drive boot disk making tool. Its feature is good compatibility. Many software is only effective for certain brands of USB flash drives. For example, HPUSBFW.EXE is also used by many people, but it cannot recognize certain brands. For example, it cannot recognize Kingston which is commonly used in the market. And I have not found any USB flash drive that USBOOT cannot recognize so far, and it also has a very good function, which is to design the format of the USB flash drive. This is very good.
In the时空 Forum, people often report that grub4dos has poor support for certain brands of USB flash drives in USB-ZIP format, but I have never encountered this situation because I always format the USB flash drive to FDD format. The FDD format has many advantages. Because after booting, it is drive A, which will not affect the drive letter of the hard disk partition, so it will not affect the operation of the original hard disk program. More importantly, it can avoid serious consequences caused by disk operations due to misidentifying the drive letter due to negligence.
USBOOT can format USB flash drives below 2G into FDD format, that is, can all be booted into drive A. Generally, 2G is enough for making boot and maintenance disks. For those above 2G, format into HDD and boot into drive C. If formatted into ZIP, the drive letter after booting on computers of different brands can be different. My Intel machine boots into A:, and the Asus boots into C:.
Now the problem is:
After USBOOT makes the boot disk, the partitions of the USB flash drive are all messed up, and other partition software cannot recognize them, looking like a mess. Windows or Linux partition tools all see them as messy. There are four primary partitions, and the disk capacity is all wrong. But strangely, it does not affect its normal use!!!
If the partitions are corrected, it cannot be used normally. Please experts analyze the principle.
In the时空 Forum, people often report that grub4dos has poor support for certain brands of USB flash drives in USB-ZIP format, but I have never encountered this situation because I always format the USB flash drive to FDD format. The FDD format has many advantages. Because after booting, it is drive A, which will not affect the drive letter of the hard disk partition, so it will not affect the operation of the original hard disk program. More importantly, it can avoid serious consequences caused by disk operations due to misidentifying the drive letter due to negligence.
USBOOT can format USB flash drives below 2G into FDD format, that is, can all be booted into drive A. Generally, 2G is enough for making boot and maintenance disks. For those above 2G, format into HDD and boot into drive C. If formatted into ZIP, the drive letter after booting on computers of different brands can be different. My Intel machine boots into A:, and the Asus boots into C:.
Now the problem is:
After USBOOT makes the boot disk, the partitions of the USB flash drive are all messed up, and other partition software cannot recognize them, looking like a mess. Windows or Linux partition tools all see them as messy. There are four primary partitions, and the disk capacity is all wrong. But strangely, it does not affect its normal use!!!
If the partitions are corrected, it cannot be used normally. Please experts analyze the principle.