From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org, katakombi@web.de
Subject: Re: [Qemu-devel] qemu vs. win4lin pro
Date: Thu, 01 Sep 2005 01:10:23 -0700 [thread overview]
Message-ID: <1125562223.5781.11.camel@aragorn> (raw)
In-Reply-To: <200509010840.52069.katakombi@web.de>
On Thu, 2005-09-01 at 08:40 +0200, Stefan Kombrink wrote:
> Hi there,
>
> I tried win4lin pro and found it very similar to running win2k using qemu.
> Speed (of graphics) is not higher and it uses the same hardware.
> Does it contain less bugs than qemu or what's the advantage that makes user
> pay 89$ for it?
>
Never used it, but here's their answer to this question:
http://www.win4lin.com/content/view/131/155/
So you're not imagining that it behaves similar to QEMU. As to whether
$X for support, smoothing rough edges and whatnot is worth it to party
Y, only Y can say.
For myself, I like my computers to need me. If everything just worked,
aside from being bored, I'd be superfluous! So I get my QEMU from source
control.
-- John.
prev parent reply other threads:[~2005-09-01 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 6:40 [Qemu-devel] qemu vs. win4lin pro Stefan Kombrink
2005-09-01 8:10 ` John R. Hogerhuis [this message]
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=1125562223.5781.11.camel@aragorn \
--to=jhoger@pobox.com \
--cc=katakombi@web.de \
--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).