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 1App46-0002Ur-BX for qemu-devel@nongnu.org; Sun, 08 Feb 2004 08:33:38 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1App3U-0002Em-19 for qemu-devel@nongnu.org; Sun, 08 Feb 2004 08:33:31 -0500 Received: from [193.252.22.28] (helo=mwinf0304.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.24) id 1App3T-0002ED-Da for qemu-devel@nongnu.org; Sun, 08 Feb 2004 08:32:59 -0500 Received: from free.fr (ATuileries-112-1-2-187.w80-14.abo.wanadoo.fr [80.14.188.187]) by mwinf0304.wanadoo.fr (SMTP Server) with ESMTP id 9D3A7A803FB2 for ; Sun, 8 Feb 2004 14:32:53 +0100 (CET) Message-ID: <40263AD5.90800@free.fr> Date: Sun, 08 Feb 2004 14:34:13 +0100 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] News References: <402032EC.1070400@free.fr> <1076199226.18012.6.camel@axp.nolabel.net> <20040208004547.GA22046@gnu.org> In-Reply-To: <20040208004547.GA22046@gnu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Lennert Buytenhek wrote: > On Sun, Feb 08, 2004 at 01:13:46AM +0100, Sylvain OBEGI wrote: > > >>>Tell me if you see improvements. >> >>I got to install Win98 SE completely (still with the memory allocation >>problem during install). But it seems that keyboard and mouse controls >>stop working in VM after a few grab-ungrab cycles (3-4 it seems) > > > Me too! By the time it gets to the end of the install, I > can't enter my product key because the keyboard appears to generate > just weird scancodes (Windows gives some popup asking me if I want to > enable an on-screen keyboard to enter my product key because my keyboard > doesn't seem to be able to generate Western letters oor something.) > Mouse still works then though. Yes, I see now similar problems in the XP install. I have not investigated yet... It is either a PIC related problem or a keyboard emulation bug. > Yeah, and an error about not being able to allocate memory during device > detection (also happens if I try to scan for new hardware after install > has completed.) I also see this error, but I did not try to correct it yet. Fabrice.