From: Leah Cunningham <leah@frauerpower.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Win95 Image does not boot, how can I debug where I am getting stuck
Date: Thu, 13 Oct 2005 20:24:33 -0400 [thread overview]
Message-ID: <1129249473.5142.76.camel@tchitow.int.iplink.net> (raw)
In-Reply-To: <1129162089.5142.58.camel@tchitow.int.iplink.net>
Final update on this. I was able to pull another disk image that is
working fine. The main difference was that I used 512k bs for the dd as
opposed to 1024k (what I had done the first time). I just thought I'd
throw that out in case anyone else ever runs into something like this.
Thanks again,
Leah
On Wed, 2005-10-12 at 20:08 -0400, Leah Cunningham wrote:
> On Wed, 2005-10-12 at 07:34 +0200, octane indice wrote:
> > > 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)
> > >
> > did you dd the complete disk, or juste the partition?
>
> I did dd the entire disk, but the partition table on it looks pretty
> goofy, so I wonder if I didn't get the boot sector and partition table
> in the image correctly.
>
> > > 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?
> > >
> > Use tomsrtbt (www.toms.net/rb, and find the tomsrtbt.raw
> > floppy image).
> >
> > Boot with
> > qemu -fda tomsrtbt.raw -hda win95.img -boot a
> > then try to do a
> > fdisk -l /dev/hda
> > if you see your partition, mount it. If everything is in place (the
> > boot flag, and so on) this is a win95 boot issue. (go to
> > www.bootdisk.com to join a boot floppy for win95)
> > If fdisk complains, the win95.img is not a harddisk image.
>
> That's a clever way to look at it, and it's clearly not a normal
> partition table, so I think that's a good clue for what I need to do to
> look into this. I'm sorry I didn't look at that more closely before
> sending this message, now I feel foolish, I was just so sure that the
> image was correct.
>
> I'll try to recreate the image with a dos boot sector and such and see
> how it goes from there. Thanks again to everyone for all the help.
>
> Leah
>
--
Leah Cunningham : d416-585-9971x692 : d416-703-5977 : m416-559-6511
Frauerpower! Co. : www.frauerpower.com : Toronto, ON Canada
next prev parent reply other threads:[~2005-10-14 0:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 22:30 [Qemu-devel] Win95 Image does not boot, how can I debug where I am getting stuck Leah Cunningham
2005-10-11 23:14 ` Wesley Parish
2005-10-12 5:34 ` octane indice
2005-10-12 15:52 ` Mike Swanson
2005-10-13 0:08 ` Leah Cunningham
2005-10-14 0:24 ` Leah Cunningham [this message]
2005-10-12 21:13 ` Henrik Nordstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1129249473.5142.76.camel@tchitow.int.iplink.net \
--to=leah@frauerpower.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).