From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Experiences installing Win98 on WinXP host.
Date: Sat, 26 Feb 2005 10:11:44 -0500 [thread overview]
Message-ID: <20050226151144.GA24006@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <000a01c51bcf$5a60ca00$254d21d1@computername>
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.
next prev parent reply other threads:[~2005-02-26 15:27 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 [this message]
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=20050226151144.GA24006@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).