China DOS Union

Hehe, thanks a lot.
If it's placed on a hard drive, it's much simpler, but it's just not convenient.
If it's placed on a CD, using EASYBOOT can be realized very well.
I think it would be even better if GRUB can be freely applied in the IMG.

The CD does not support 3M floppy disk boot images. The CD can only support three types of floppy disk formats for boot images: 1.2M, 1.44M, and 2.88M. If the boot image you create is not one of these three formats, then you cannot use it for CD booting. Although the CD standard stipulates that the above three formats must be supported, not all BIOSes may fully implement them. Making a 1.44M floppy disk boot image is the safest, and it can boot smoothly under all BIOSes.

On the other hand, even if VMware cannot run a 2.88M floppy disk image, it doesn't matter. When you use it to make a CD boot image, the BIOS may boot it smoothly. The reason VMware cannot run it is that its BIOS does not support floppy disks larger than 1.44M. This does not mean that when this image is made into a CD, the BIOS of the CD still has this problem. That is to say, the BIOS of the CD may perfectly support the 2.88M boot image. You can try. Similarly, with VMware, it may not be able to boot a 2.88M floppy disk image (or although it can barely boot but there are problems in further operations), but the bootable CD made from this floppy disk image may be correctly and perfectly booted by VMware.

That makes sense. For CD - boot, there's no need to create an image larger than 1.44M (just make several images, that's fine ^0^). The file - booting in floppy images isn't as easy to implement as with EASYBOOT (I mean, booting different image files in IMG through GRUB, which is nesting IMG within IMG, so the IMG can be large. But it doesn't seem very practical, heh.). Also, multi - boot CDs made with EASYBOOT can boot IMG files of any size.

VM only supports formal IMG images!