From: <jeebs@yango.us>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host.
Date: Sat, 26 Feb 2005 10:34:49 -0600 [thread overview]
Message-ID: <002d01c51c21$2105bd90$254d21d1@computername> (raw)
In-Reply-To: 20050226151144.GA24006@jbrown.mylinuxbox.org
From: "Jim C. Brown" <jma5@umd.edu>
> Evidently, we don't have enough qemu-win32 users or developers, if it takes us
> this long to hear that the build is broken. :/
That has crossed my mind, too...
However, it's still possible that:
1) It's a relatively recent break in the cvs windows builds.
2) Most of the windows users are trying to run Linux, rather than Windows. (I haven't tried linux on qemu lately.)
3) Maybe I'm using some run option they aren't. Or I'm not using one that they are. (Although admittedly I've kept my options pretty simple. localtime, dummy-net, and a few times the audio option.... So there aren't many for me to remove.)
>From what I've heard recently, the cdrom change problem has been around a long time and is fairly well known and hasn't been fixed.
It's possible the rest of the problems is more during the installation, and that already installed images work okay. Meaning qemu might be working okay on the disk images they already have, and they haven't bothered to try and install it because the don't need to.
> from source and they only run linux guests. (I am curious why someone would
> want to run Windows inside of Windows. Are you being a very thorough beta tester
> (which we need), or do you actually have use of such a configuration?)
I was beta testing, yes. (I'm also currently a beta tester of VMWare 5. Although I gotta admit I did more testing back when it was beta and rc1 than I have now with rc2.) That's why I've tried several versions of dos and windows etc.
But I was also going to keep Win98 and use it.
Yes, I do like to run the occasional Windows in Windows. As a way to safely test programs, or run a different version, or experiment with various ideas etc. without having to make changes to my existing setup. And a few other reasons occasionally.
To me, there are plenty of reasons to occasionally use another copy of Windows.
> Just curious, have you tried running a Linux guest on these builds? If so, what
> was the result?
Not lately.
In fact, this has been my first usage of qemu in months.
I've got linux installed under vmware, but I haven't bothered to do that with qemu.
At the time I was actually going to try to use a clean copy of Win98, and that has taken a lot longer than I thought. [grimace]
next prev parent reply other threads:[~2005-02-26 16:54 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
2005-02-26 9:56 ` Laurent Amon
2005-02-26 15:11 ` Jim C. Brown
2005-02-26 16:34 ` jeebs [this message]
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='002d01c51c21$2105bd90$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).