qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <jeebs@yango.us>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host.
Date: Sat, 26 Feb 2005 00:49:36 -0600	[thread overview]
Message-ID: <000a01c51bcf$5a60ca00$254d21d1@computername> (raw)
In-Reply-To: 421FEF22.3070301@tusker.org

From: "Damien Mascord" <tusker@tusker.org>
> 
> Give it a go with 
> http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-0.6.1-windows-2.zip and 
> see how you fare...

A little better, but only a little.

At the point where Win98 asks me to point it to my old windows files (to verify for Win98 being an 'upgrade') and I change the cd:

1) Twice the guest appeared to lock up.  I'd switch to the cd drive and the hour glass would show up, and nothing further would happen.  I couldn't even move the mouse cursor.

2) Once I was able to actually switch to the new cd iso image.  (Although I didn't go any further because I did #3 next.)

3) After I managed to switch it to the right ISO image, I decided to try and switch to another ISO image.  That change failed.  It showed the previous directory structure on the cd.  When I clicked on an invalid directory, nothing else happened.  Qemu didn't crash (like before), but nothing happened and I couldn't get Win98 to quit, so I could point it to the right directory or try changing the cd again.

4) In one test, when I tried changing the cd, it wouldn't recognise any cd image I tried.

In the final test, I used my cd image that has Win98 and Win 3 (for upgrade check) on it.  That way I didn't have to do the cd change.

In that test, it behaved like the ones from FreeOSZoo.  Namely, it blue screened after the first reboot.

I forgot to check to see if it accepts spaces in the pathnames, but I have no reason to believe it does.


(And for the record, these are the same images I've used under vmware.  So they are correct and working.)

> As a last resort, perhaps try to build the latest CVS source using the 
> following instructions:

I'd rather not build my own.  I don't have any compilers even installed.  Been a while since I've done any programming at all and I just don't bother to keep the stuff around.  So I'd have to download it all first.  Too much trouble when cvs builds are already built and made available.

If it's a build problem, then those builds need to get fixed.  That'd help everybody, not just me.

But with two different build sources having the same problems, I doubt it's a build problem.


I didn't try Win98se or WinME, or even XP.

This version is behaving enough like the ones from FreeOSZoo that I see no reason to.

It's pretty clear that the Windows builds are significantly broken.  Or else qemu just flat out doesn't like anything but Linux guests.

  reply	other threads:[~2005-02-26  7:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 22:53 [Qemu-devel] Experiences installing Win98 on WinXP host jeebs
2005-02-25 23:32 ` Darryl Dixon
2005-02-25 23:58   ` jeebs
2005-02-26  0:08   ` Mike Swanson
2005-02-26  0:37     ` jeebs
2005-02-26  3:38       ` Damien Mascord
2005-02-26  6:49         ` jeebs [this message]
2005-02-26  9:56           ` Laurent Amon
2005-02-26 15:11           ` Jim C. Brown
2005-02-26 16:34             ` jeebs
2005-02-27  2:51             ` Elefterios Stamatogiannakis
2005-02-27  5:43               ` jeebs

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='000a01c51bcf$5a60ca00$254d21d1@computername' \
    --to=jeebs@yango.us \
    --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).