From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24)
	id 1Apdgt-00040R-GL
	for qemu-devel@nongnu.org; Sat, 07 Feb 2004 20:24:55 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24)
	id 1ApdgN-0003TT-Lr
	for qemu-devel@nongnu.org; Sat, 07 Feb 2004 20:24:54 -0500
Received: from [80.65.225.144] (helo=phoenix.nolabel.net)
	by monty-python.gnu.org with esmtp (Exim 4.24) id 1ApdgM-0003TQ-Vp
	for qemu-devel@nongnu.org; Sat, 07 Feb 2004 20:24:23 -0500
Received: from axp.nolabel.net (axp.nolabel.net [192.168.0.2])
	by phoenix.nolabel.net (Postfix) with ESMTP id 431D117F43
	for <qemu-devel@nongnu.org>; Sun,  8 Feb 2004 02:24:21 +0100 (CET)
Subject: Re: [Qemu-devel] News
From: Sylvain OBEGI <katios@nolabel.net>
In-Reply-To: <20040208004547.GA22046@gnu.org>
References: <402032EC.1070400@free.fr>
	<1076199226.18012.6.camel@axp.nolabel.net>
	<20040208004547.GA22046@gnu.org>
Content-Type: text/plain; charset=iso-8859-15
Message-Id: <1076203511.15959.8.camel@axp.nolabel.net>
Mime-Version: 1.0
Date: Sun, 08 Feb 2004 02:25:11 +0100
Content-Transfer-Encoding: quoted-printable
Reply-To: qemu-devel@nongnu.org
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Le dim 08/02/2004 =E0 01:45, Lennert Buytenhek a =E9crit :
> Yeah, and an error about not being able to allocate memory during devic=
e
> detection (also happens if I try to scan for new hardware after install
> has completed.)

Yes, that's the error I was talking about, the one you mentionned in one
of your previous mail.
About the IOS error you got ("While initializing device IOS: Windows
protection error.  You need to restart your computer."), I have that one
if I specify a drive as hdb, but it's working if it is set as hdc.

Is there anyway to get Windows working at a higher resolution than
640*480 right now or do we have to whine until S3 emulation is complete?
;-)

I read that a dos driver is needed to make the cdrom works under
Windows, what's missing to have it recognized natively? (I guess that's
the same thing that causes the "drive in compatibility mode" message)

--=20

Sylvain OBEGI
Email : katios@nolabel.net
ICQ : 661913