qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Doug Stanley <dstanley@imtco.com>
To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu and Longhorn
Date: Wed, 16 Feb 2005 11:12:48 -0500	[thread overview]
Message-ID: <42137100.1080905@imtco.com> (raw)
In-Reply-To: <1108542177.16634.13.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2821 bytes --]

I thought from what I read that longhorn required a 3d accelerator
card and relied heavily on directX. I thought it was something
crazy like you need atleast an geforce FX5200 just to run longhorn
at a decent speed...

Perhaps that's the problem? Maybe it's doing all the directX in software
and making it take twice as long...but I'm not really a windows or
longhorn expert, so I may just be talking out my a**.

Atleast it installs though right ? ;)

Doug

Darryl Dixon wrote:
> 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 <esrever_otua@pythonhacker.is-a-geek.net 
> <mailto:esrever_otua@pythonhacker.is-a-geek.net>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

[-- Attachment #2: dstanley.vcf --]
[-- Type: text/x-vcard, Size: 304 bytes --]

begin:vcard
fn:Douglas Stanley
n:Stanley;Douglas
org:Integrated Marketing Technologies;IT
adr:;;2945 Carquest Dr.;Brunswick;Ohio;44212;US
email;internet:dstanley@imtco.com
title:Systems Administrator
tel;work:330-220-6715
x-mozilla-html:FALSE
url:http://www.imtco.com
version:2.1
end:vcard


  reply	other threads:[~2005-02-16 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  8:22 [Qemu-devel] Qemu and Longhorn Darryl Dixon
2005-02-16 16:12 ` Doug Stanley [this message]
2005-02-16 18:51 ` Fabrice Bellard
2005-02-16 21:56   ` Natalia Portillo
2005-02-16 22:20   ` Darryl Dixon
2005-02-17 11:11     ` Darryl Dixon
2005-02-17 12:52       ` Jernej Simončič
2005-02-18  0:19         ` Natalia Portillo

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=42137100.1080905@imtco.com \
    --to=dstanley@imtco.com \
    --cc=esrever_otua@pythonhacker.is-a-geek.net \
    --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).