From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D55Cd-00062I-6c for qemu-devel@nongnu.org; Sat, 26 Feb 2005 11:54:03 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D55CQ-0005u7-5i for qemu-devel@nongnu.org; Sat, 26 Feb 2005 11:53:56 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D55CM-0005js-PI for qemu-devel@nongnu.org; Sat, 26 Feb 2005 11:53:46 -0500 Received: from [209.55.4.210] (helo=mxo1.broadbandsupport.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D54uK-0001m5-O2 for qemu-devel@nongnu.org; Sat, 26 Feb 2005 11:35:08 -0500 Received: from atmail2.ibbsonline.com (atmail2.ibbsonline.com [209.55.3.51]) by mxo1.broadbandsupport.net (Postfix) with ESMTP id 0AC9F39452 for ; Sat, 26 Feb 2005 11:34:57 -0500 (EST) Received: from [209.33.77.37] (helo=computername) by atmail2.ibbsonline.com with smtp (Exim 4.43) id 1D54tK-0006qg-29 for qemu-devel@nongnu.org; Sat, 26 Feb 2005 11:34:06 -0500 Message-ID: <002d01c51c21$2105bd90$254d21d1@computername> From: References: <421FEF22.3070301@tusker.org><000a01c51bcf$5a60ca00$254d21d1@computername> <20050226151144.GA24006@jbrown.mylinuxbox.org> Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host. Date: Sat, 26 Feb 2005 10:34:49 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 From: "Jim C. Brown" =20 > 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. =20 > 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]