From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1Kiq-0006jM-Pq for qemu-devel@nongnu.org; Wed, 16 Feb 2005 03:39:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1Kim-0006hj-VP for qemu-devel@nongnu.org; Wed, 16 Feb 2005 03:39:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1Kim-0006h6-NK for qemu-devel@nongnu.org; Wed, 16 Feb 2005 03:39:44 -0500 Received: from [65.19.178.186] (helo=pythonhacker.is-a-geek.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D1KTG-0004K8-5V for qemu-devel@nongnu.org; Wed, 16 Feb 2005 03:23:42 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id EABAF403D4 for ; Wed, 16 Feb 2005 03:23:40 -0500 (EST) Received: from pythonhacker.is-a-geek.net ([127.0.0.1]) by localhost (pythonhacker.is-a-geek.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04626-09 for ; Wed, 16 Feb 2005 03:23:07 -0500 (EST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by pythonhacker.is-a-geek.net (Postfix) with ESMTP id E88A0403CF for ; Wed, 16 Feb 2005 03:22:59 -0500 (EST) From: Darryl Dixon Content-Type: multipart/alternative; boundary="=-EWLOSlBVz3TkWm0MN+ev" Date: Wed, 16 Feb 2005 21:22:57 +1300 Message-Id: <1108542177.16634.13.camel@localhost.localdomain> Mime-Version: 1.0 Subject: [Qemu-devel] Qemu and Longhorn Reply-To: esrever_otua@pythonhacker.is-a-geek.net, 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 --=-EWLOSlBVz3TkWm0MN+ev Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi All, Just for giggles I ran an install of Longhorn build 4074 on CVS Qemu today with kqemu. The install seemed to go well; the first stage didn't recognise any mouse (probably more a Windows error than a Qemu one), but was otherwise perfectly rendered (with what appeared to be a vesa video mode) and usable with the keyboard. It proceeded reasonably quickly. After the first reboot, the mouse was detected and worked, and it once again proceed reasonably quickly (vesa video mode again), up until it started detecting the hardware, at which point it stuck for around an hour (it was actually doing work and processing the whole time). During this all seemed well, and I even watched it detect the video OK and flip from 640x480 to 800x600. Once it made it past the hardware detect and booted into the actual Windows GUI, things got painful. Apparently even though the installer knows how to use vesa video, Windows itself and the standard VGA display driver it installed *don't* and so I was left with a 640x480 16 colour display that ran *agonisingly* slowly, presumably as all of the video calls were being emulated through calls to the Bochs BIOS. It was glacial. Anyhow, I managed to soldier through a few windows to the Device Manager, and from what I could see everything except the network card had been detected OK (except of course that the video was 'Standard VGA'). Presumably the network card just needs the Win2000 RTL8029 driver like Server 2003 did. I tried to fix the video so I'd be able to give Qemu + Longhorn a proper test, but after (literally) hours to get through the driver update wizard and find that my only choice was the standard VGA or something called a 'BARCO', I gave up and wrote this short summary instead :) Presumably a more patient man would be able to install the Cirrus Win2000 driver and Longhorn on Qemu would be usable... Many regards, -- Darryl Dixon --=-EWLOSlBVz3TkWm0MN+ev Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi All,

    Just for giggles I ran an install of Longhorn build 4074= on CVS Qemu today with kqemu.  The install seemed to go well; the fir= st stage didn't recognise any mouse (probably more a Windows error than a Q= emu one), but was otherwise perfectly rendered (with what appeared to be a = vesa video mode) and usable with the keyboard.  It proceeded reasonabl= y quickly.  After the first reboot, the mouse was detected and worked,= and it once again proceed reasonably quickly (vesa video mode again), up u= ntil it started detecting the hardware, at which point it stuck for around = an hour (it was actually doing work and processing the whole time).  D= uring this all seemed well, and I even watched it detect the video OK and f= lip from 640x480 to 800x600.  Once it made it past the hardware detect= and booted into the actual Windows GUI, things got painful.  Apparent= ly even though the installer knows how to use vesa video, Windows itself an= d the standard VGA display driver it installed *don't* and so I was left wi= th a 640x480 16 colour display that ran *agonisingly* slowly, presumably as= all of the video calls were being emulated through calls to the Bochs BIOS= .  It was glacial.  Anyhow, I managed to soldier through a few wi= ndows to the Device Manager, and from what I could see everything except th= e network card had been detected OK (except of course that the video was 'S= tandard VGA').  Presumably the network card just needs the Win2000 RTL= 8029 driver like Server 2003 did.  I tried to fix the video so I'd be = able to give Qemu + Longhorn a proper test, but after (literally) hours to = get through the driver update wizard and find that my only choice was the s= tandard VGA or something called a 'BARCO', I gave up and wrote this short s= ummary instead :)   Presumably a more patient man would be able t= o install the Cirrus Win2000 driver and Longhorn on Qemu would be usable...=

Many regards,
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
--=-EWLOSlBVz3TkWm0MN+ev--