From: Mark IJbema <mark@ijbema.xs4all.nl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] windows?
Date: Wed, 25 Feb 2004 17:49:39 +0100 [thread overview]
Message-ID: <20040225164939.GD2113@ijbema.xs4all.nl> (raw)
In-Reply-To: <20040225092120.GA21701@cs.unibo.it>
On Wed, Feb 25, 2004 at 10:21:20AM +0100, Renzo Davoli wrote:
> On Wed, Feb 25, 2004 at 10:09:41AM +0100, Mark IJbema wrote:
> > Well, the application i had in mind was using it for reactos, in the
> > same way bochs is used now. Because on linux, qemu runs much faster than
> > bochs, and when it's bugfree (or at least not notably bugged), it would
> > be a viable alternative to vmware (even though it's still a lot slower
> > than vmware).
> >
> Even a lot safer (runs at user level, no kernel modules)
> Even a lot general (runs already on four hardware architectures and this
> number is the low boundary of what is going to be implemented in the
> future).
While this is true, i personally don't care, i only have x86 hardware
(though i should get some other hardware ;) )
> It is not only an alternative to vmware, but also to VirtualPC and many
> other virtual machine solution.
> But it is also a general framework for running single executables for
> the wrong architecture.
Yup, this could indeed be interesting for OS-es intended to run on
various hardware platforms, but for which most apps are released x86
only (WinNT / ReactOS).
> P.S. the real solution would be to convince everybody to leave
> proprietary sw and formats, including flash. It needs time, though....
Isn't flash open? I thought they released some sort of open Flash-XML
format...
Mark
next prev parent reply other threads:[~2004-02-25 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 23:26 [Qemu-devel] windows? Mark IJbema
2004-02-24 23:44 ` John R. Hogerhuis
2004-02-25 9:09 ` Mark IJbema
2004-02-25 9:21 ` Renzo Davoli
2004-02-25 16:49 ` Mark IJbema [this message]
2004-02-24 23:50 ` dguinan
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=20040225164939.GD2113@ijbema.xs4all.nl \
--to=mark@ijbema.xs4all.nl \
--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).