From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EQDKI-00076T-EI for qemu-devel@nongnu.org; Thu, 13 Oct 2005 20:21:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EQDKG-00076H-O0 for qemu-devel@nongnu.org; Thu, 13 Oct 2005 20:21:34 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EQDKG-00076E-IW for qemu-devel@nongnu.org; Thu, 13 Oct 2005 20:21:32 -0400 Received: from [192.139.81.57] (helo=oogabooga.heinous.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EQDKG-0007kK-GV for qemu-devel@nongnu.org; Thu, 13 Oct 2005 20:21:32 -0400 Received: from tchitow.int.iplink.net (fw.iplink.net [192.139.81.98]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by oogabooga.heinous.org (Postfix) with ESMTP id 377B526AD for ; Thu, 13 Oct 2005 20:21:29 -0400 (EDT) Subject: Re: [Qemu-devel] Win95 Image does not boot, how can I debug where I am getting stuck From: Leah Cunningham In-Reply-To: <1129162089.5142.58.camel@tchitow.int.iplink.net> References: <1129069829.5142.16.camel@tchitow.int.iplink.net> <1129095295.434ca07f825ab@webmail.alinto.com> <1129162089.5142.58.camel@tchitow.int.iplink.net> Content-Type: text/plain Date: Thu, 13 Oct 2005 20:24:33 -0400 Message-Id: <1129249473.5142.76.camel@tchitow.int.iplink.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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