All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Michel POURE <jm@poure.com>
To: qemu-devel@nongnu.org
Cc: Mike Nordell <tamlin@algonet.se>
Subject: Re: [Qemu-devel] Win2k mouse
Date: Thu, 15 Apr 2004 10:52:54 +0200	[thread overview]
Message-ID: <200404151052.55500.jm@poure.com> (raw)
In-Reply-To: <002801c42260$67c56110$0401a8c0@putte2k>

> While NT as guest behaves like this, just booting it
> is a test of patience why it might take some days before I get any real
> numbers.

Dear Mike,

Actually, under my Pentium4 1.8 Ghz desktop, QEMU is able to boot Win2k in 90 
seconds (until password prompt) and needs another 30 seconds to display the 
desk. This is fairly fast compared to other emulation softwares.

When using Bochs, I can remember installations lasting 48 hours and a one hour 
startup. Using Qemu, I was able to install Win2k in one hour and a half. 

In the case of Win2k, appying the ne2000 patch and solving the mouse issue 
would be perfect. Then people can start using Win2k and sending bug reports, 
patches and improvements. 

Cheers,
Jean-Michel

  reply	other threads:[~2004-04-15  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 20:36 [Qemu-devel] Win2k mouse Mike Nordell
2004-04-15  8:52 ` Jean-Michel POURE [this message]
2004-04-15  9:37   ` Lionel Ulmer
2004-04-15 11:28     ` Brad Campbell
2004-04-15 11:51     ` Jean-Michel POURE
2004-04-15 13:48       ` Mike Nordell
2004-04-15 13:44     ` Mike Nordell
2004-04-15 18:31       ` Lionel Ulmer
2004-04-15 20:21         ` Lionel Ulmer
2004-04-16  3:54           ` Mike Nordell
2004-04-16 16:33             ` malc
2004-04-16 17:30               ` [Qemu-devel] sound issue Hetz Ben Hamo
  -- strict thread matches above, loose matches on Subject: below --
2004-04-14  8:49 [Qemu-devel] Win2k mouse Jean-Michel POURE
2004-04-14 11:11 ` Hetz Ben Hamo
2004-04-14 20:17 ` Fabrice Bellard

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=200404151052.55500.jm@poure.com \
    --to=jm@poure.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tamlin@algonet.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.