From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Igsxa-0007qU-7X
	for qemu-devel@nongnu.org; Sat, 13 Oct 2007 22:12:06 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IgsxY-0007oT-Jd
	for qemu-devel@nongnu.org; Sat, 13 Oct 2007 22:12:05 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IgsxY-0007oE-Dd
	for qemu-devel@nongnu.org; Sat, 13 Oct 2007 22:12:04 -0400
Received: from rv-out-0910.google.com ([209.85.198.191])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <waxdragon@gmail.com>) id 1IgsxY-0007eM-3j
	for qemu-devel@nongnu.org; Sat, 13 Oct 2007 22:12:04 -0400
Received: by rv-out-0910.google.com with SMTP id g11so4357801rvb
	for <qemu-devel@nongnu.org>; Sat, 13 Oct 2007 19:12:02 -0700 (PDT)
Message-ID: <9b0d5f320710131912i1b4ef3a7lbe5c7e1d6dcbda80@mail.gmail.com>
Date: Sat, 13 Oct 2007 22:12:02 -0400
From: WaxDragon <waxdragon@gmail.com>
Subject: Re: [Qemu-devel] QEMU keyboard issue with Gujin-2.2
In-Reply-To: <691521.34631.qm@web26908.mail.ukl.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <691521.34631.qm@web26908.mail.ukl.yahoo.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.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://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 10/11/07, Etienne Lorrain <etienne_lorrain@yahoo.fr> wrote:
>  Hello,
>
>  I did more search on the keyboard problem, just posted on the forum
> but here seems to be a better place:
>

  This may not be the same issue, but I've seen strange behaviour
also.  ReactOS has a built in kernel debugger that seems to have a
problem with the mouse input.  If the mouse is "grabbed" by the QEMU
SDL window, and you are in the kernel debugger, moving the mouse will
generate "garbage" charaters, usually rendering the debugger useless.
Real hardware, VMWare, and QEMU *without* the mouse grabbed do not
exhibit this behaviour.
  QEMU has acted this way for quite some time, seems forever.  I've
mentioned it on #qemu to little interest, but since it's not a huge
issue for me, I've not looked into a great deal. Thought I would
mention it.

WaxDragon

-- 
22:38 <@WaxDragon> false ^ true
22:39 < false> :(
22:39 < false> dont you think you can XOR me and get away with it! I
always return!