Public bug reported:
How to reproduce:
Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be
messages about "missing" files and OS2.INI not found. Chkdsk C: complains about
FS corruption. Nothing changes even after fixing errors and next reboot. If you
install OS/2 onto FAT partition instead, everything will be OK. I also tried
booting images with OS/2 pre-installed through VBOX with same results. Is that
HPFS driver or QEMU fault?
** Affects: qemu
Importance: Undecided
Status: New
** Tags: corruption hpfs i386 os2 warp4
** Description changed:
How to reproduce:
- Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be
messages about "missing" files and OS2.INI not found. Chkdsk C: complains about
FS corruption. Nothing changes evwn after fixing errors and next reboot. If you
install OS/2 onto FAT partition instead, everything will be OK. I also tried
booting images with OS/2 pre-installed through VBOX with same results. Is that
HPFS driver or QEMU fault?
+ Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be
messages about "missing" files and OS2.INI not found. Chkdsk C: complains about
FS corruption. Nothing changes even after fixing errors and next reboot. If you
install OS/2 onto FAT partition instead, everything will be OK. I also tried
booting images with OS/2 pre-installed through VBOX with same results. Is that
HPFS driver or QEMU fault?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1743337
Title:
OS/2 Warp 4 HPFS corruption
Status in QEMU:
New
Bug description:
How to reproduce:
Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be
messages about "missing" files and OS2.INI not found. Chkdsk C: complains about
FS corruption. Nothing changes even after fixing errors and next reboot. If you
install OS/2 onto FAT partition instead, everything will be OK. I also tried
booting images with OS/2 pre-installed through VBOX with same results. Is that
HPFS driver or QEMU fault?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1743337/+subscriptions
