I'm using the latest version of GRUB4DOS v0.4.6a (rev 2017-10-05) and I found that I can neither boot OS/2 Warp nor Windows 95 when I map drives.
When I select OS/2 Warp 4 when booting from the second hard disk image mapped as the first hard disk image, this is the error message that I get:
And when I try to boot Windows 95 from the third hard disk image mapped as (hd0), this is the error message that I get:
On a side note, when trying to boot with the Windows 95 boot disk, to try to access the third hard disk, I end up getting massive data corruption (almost 600 MB worth). I'm really lucky that I have backed up hard disk images incase something terrible goes wrong.
Now, here's are the current parameters that are used to boot OS/2 and Windows 95 under GRUB4DOS:
title IBM PC-DOS 6.30 / IBM OS/2 Warp 4\n\n
map (hd0) (hd1)
map (hd1) (hd0)
title Microsoft Windows 95\n\n
map (hd0) (hd2)
map (hd2) (hd0)
find --set-root /IO.SYS
I have used the map --hook feature to hook INT13 after mapping hard disks, but it doesn't seem to work anymore in this latest release of GRUB4DOS. If I remove the first and third hard disk images, I can boot OS/2 and if I remove the first and second hard disk images, I can boot Windows 95.
Looking in the latest code change located here: https://github.com/c...325630e41692e64
I see that there are two new parameters, "--in-situ" and "--swap-drive=DRIVE1=DRIVE2". I never used these features before.
Has anything changed in GRUB4DOS? If so, what parameters should I use to correct this error?
Edited by ppgrainbow, 2 weeks ago.