From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EPitw-0002ju-3G for qemu-devel@nongnu.org; Wed, 12 Oct 2005 11:52:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EPitt-0002iy-UA for qemu-devel@nongnu.org; Wed, 12 Oct 2005 11:52:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EPitt-0002it-LG for qemu-devel@nongnu.org; Wed, 12 Oct 2005 11:52:17 -0400 Received: from [64.233.162.198] (helo=zproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EPitt-00011m-TW for qemu-devel@nongnu.org; Wed, 12 Oct 2005 11:52:18 -0400 Received: by zproxy.gmail.com with SMTP id i11so146298nzh for ; Wed, 12 Oct 2005 08:52:16 -0700 (PDT) Message-ID: <79bf98480510120852q3cd9f548h2973131af8bc6434@mail.gmail.com> Date: Wed, 12 Oct 2005 08:52:15 -0700 From: Mike Swanson Subject: Re: [Qemu-devel] Win95 Image does not boot, how can I debug where I am getting stuck In-Reply-To: <1129095295.434ca07f825ab@webmail.alinto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1129069829.5142.16.camel@tchitow.int.iplink.net> <1129095295.434ca07f825ab@webmail.alinto.com> 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 Windows 95 (along with all the NTs, 98 and Me) is also very picky about the hardware it's being booted from. If it's not similar to the hardware it was installed on, it may either not boot at all or have very strange effects during operation. Try to set up a new blank Hardware Profile (in System Properties), then booting it into QEMU. On 10/11/05, 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=3D/dev/loop5) > > > did you dd the complete disk, or juste the partition? > > > 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. > HTH > > --------------------------------------------- > Etes vous un consom'Acteur ? Toutes les saveurs =E9quitables sont sur htt= p://www.epicerie-equitable.com > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Mike