From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D53qx-00081k-1A for qemu-devel@nongnu.org; Sat, 26 Feb 2005 10:27:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D53qu-00080h-Td for qemu-devel@nongnu.org; Sat, 26 Feb 2005 10:27:33 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D53qu-00080D-N7 for qemu-devel@nongnu.org; Sat, 26 Feb 2005 10:27:32 -0500 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D53be-0004pf-2U for qemu-devel@nongnu.org; Sat, 26 Feb 2005 10:11:46 -0500 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j1QFBikL009663 for ; Sat, 26 Feb 2005 10:11:44 -0500 (EST) Date: Sat, 26 Feb 2005 10:11:44 -0500 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host. Message-ID: <20050226151144.GA24006@jbrown.mylinuxbox.org> References: <421FEF22.3070301@tusker.org> <000a01c51bcf$5a60ca00$254d21d1@computername> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000a01c51bcf$5a60ca00$254d21d1@computername> 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 On Sat, Feb 26, 2005 at 12:49:36AM -0600, jeebs@yango.us wrote: > > > 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 have to agree here. The one major windows developer who I have spoken to keeps his own qemu source tree, independent of the CVS. (I don't think his tree is an option for you to test out however, as it is in source only and I believe you'd need a copy of Visual Studio to compile it.) Evidently, we don't have enough qemu-win32 users or developers, if it takes us this long to hear that the build is broken. :/ I do know of a few others who use qemu on windows host, but they all compile 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?) > > It's pretty clear that the Windows builds are significantly broken. Or else qemu just flat out doesn't like anything but Linux guests. On a linux host, windows 2000, windows 98se, freedos, and msdos 6.22 all work fine, so this is most likely a windows-host specific problem. Just curious, have you tried running a Linux guest on these builds? If so, what was the result? -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.