From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DpXUv-0000Fy-VA for qemu-devel@nongnu.org; Mon, 04 Jul 2005 16:24:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DpXUe-000069-2S for qemu-devel@nongnu.org; Mon, 04 Jul 2005 16:24:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DpXUb-00005G-L3 for qemu-devel@nongnu.org; Mon, 04 Jul 2005 16:24:37 -0400 Received: from [64.233.184.201] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DpXX5-0006PC-5B for qemu-devel@nongnu.org; Mon, 04 Jul 2005 16:27:11 -0400 Received: by wproxy.gmail.com with SMTP id i22so673502wra for ; Mon, 04 Jul 2005 13:21:07 -0700 (PDT) Message-ID: <23bcb87005070413215d25664d@mail.gmail.com> Date: Mon, 4 Jul 2005 16:21:06 -0400 From: Doctor Bill Subject: Re: [Qemu-devel] Re: Qemu Windows Host & Client Feedback In-Reply-To: <42C91488.7050402@secureit-mu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <23bcb87005063014284513c1d0@mail.gmail.com> <23bcb87005070322535a8cacac@mail.gmail.com> <42C91488.7050402@secureit-mu.com> Reply-To: Doctor Bill , 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 Yes, it definitely acts like a stuck key. But none of the pressing none of the keys on my keyboard relieves the problem. Only restarting the QEMU virtual machine. However, I did figure out 90% of the time the problem occurs because I press the windows key to switch tasks. If I remember to first press CTRL+ALT+2 first, I completely avoid those occurrences. Another 5% happens when I don't focus the mouse onto the window before Windows finishes starting. Again, if I am patient I can avoid this 5%. The last 5% consist of cases when another window pops up and takes the focus on it's own, or for yet unexplained reasons. About the only way to avoid this 5% is if I avoid multitasking foreground processes. I would say this is a very serious usability problem, but for "alpha" software I consider it mild because everything has a workaround. More serious to me are the networking problems with SAMBA. However, I am not convinced those are bug. It could just be I am making some bad guesses on how to configure samba due to lack of documentation. So I will try not to take up peoples time on this list until I know if it is user errors or software errors. Bill