China DOS Union

1. This win98.img can be normally booted with memdisk.
2. GRUB version 0.4.3 2007-10-08
3. Symptom: Freezes when starting Windows 98
4. Command line sequence
map (hd0,0)/boot/sources/win98.img (hd0)
map (hd0) (hd2)
chainloader (hd0)+1
boot

Try a version before August 12.

grub4dos-0.4.3pre2 also doesn't work. But both versions can work with the --mem parameter.

In addition, does it support compressed IMG or ISO files?

Supports compressed IMG, but when my win98.img is compressed, it looks like it didn't shut down properly last time, while it's okay without compression.

What's the matter when the file adjusted with winimage shows that the size calculated according to the partition table is inconsistent with the actual size when booting?

[ Last edited by zmq on 2007-10-9 at 10:41 AM ]

--mem does not require the continuity of file storage, while without --mem, the continuity of file storage is required. If the file is not stored continuously, it cannot start, so an error occurs

--mem is equivalent to memdisk, both are disk emulation in memory.

If you don't use --mem, you need --in-situ to emulate the disk to enter win98.

The image file used by --in-situ should be an "image of a certain partition", not an image of "the entire hard disk" with a partition table.

--in-situ also requires that the image file must be stored continuously on the disk. If the image file is not continuous, you must use a file defragmentation tool such as contig to sort it out, and then you can enter grub4dos to start win98 with disk emulation.