My suggestion: dd if=/dev/fd0 bs=512 of=win95.img when fd0 contains a Win95 boot floppy with some diagnostics. Then qemu -boot a -fda win95.img -hda win95 & and run the diagnostics.
That should tell you if there's an error in the image itself, perhaps in the MBR. If it's not in the image, then it's a bug somewhere in qemu. But that should get you started. Wesley Parish Quoting Leah Cunningham <[EMAIL PROTECTED]>: > This probably isn't exactly the right question for a development > mailing > list, but the user-forumns did not seem to exist, so I hope you will > forgive me or tell me where to ask a question like this. > > I have an image of a Window's 95 hard disk, dd'd directly off the disk > itself. I can mount the image loopback: > > /tmp/win95 on /mnt type vfat (rw,loop=/dev/loop5) > > I do not seem to be able to boot the image with qemu, trying with > various versions, but I have no idea how to proceed with finding out > what is wrong. How can I debug what is happening? Would there be a > boot loader error? > > If anyone can help, I would appreciate it. When I try to boot the image > we hang right after the BIOS says "Booting from hard disk". > > Cheers, > Leah > -- > Leah Cunningham : d416-585-9971x692 : d416-703-5977 : m416-559-6511 > Frauerpower! Co. : www.frauerpower.com : Toronto, ON Canada > > > > _______________________________________________ > Qemu-deve l mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > "Sharpened hands are happy hands. "Brim the tinfall with mirthful bands" - A Deepness in the Sky, Vernor Vinge "I me. Shape middled me. I would come out into hot!" I from the spicy that day was overcasked mockingly - it's a symbol of the other horizon. - emacs : meta x dissociated-press _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
