From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FfGW7-0007J9-19 for qemu-devel@nongnu.org; Sun, 14 May 2006 09:20:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FfGW5-0007If-Fd for qemu-devel@nongnu.org; Sun, 14 May 2006 09:20:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FfGW5-0007IZ-9f for qemu-devel@nongnu.org; Sun, 14 May 2006 09:20:13 -0400 Received: from [213.247.139.22] (helo=mail.sub.ru) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FfGYH-0001zo-4w for qemu-devel@nongnu.org; Sun, 14 May 2006 09:22:29 -0400 Received: from unknown ([213.247.139.22]) by localhost (webmail.sub.ru [213.247.139.22]) (amavisd-new, port 10024) with SMTP id 47916-19 for ; Sun, 14 May 2006 17:20:08 +0400 (MSD) From: Mikhail Ramendik Subject: Re: [Qemu-devel] w98se slow with kqemu, apparently some systems only Date: Sun, 14 May 2006 17:20:06 +0400 References: <200605141624.39231.mr@ramendik.ru> <200605141628.24354.mr@ramendik.ru> <44672665.2090608@wasp.net.au> In-Reply-To: <44672665.2090608@wasp.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605141720.07088.mr@ramendik.ru> Reply-To: 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 В сообщении от 14 мая 2006 16:45 Brad Campbell написал(a): > Do you have the idle driver loaded in win98 as per the qemu docs? > Otherwise it will use 100% cpu, where as NT based systems know how to hlt > the processor Thanks, I have done so now. The situation has improved, the speed with kqemu and without kqemu is now approximately the same; but it is still much worse than what was reported by the person for whom kqemu actually works. For me, with this driver, the bootup to the logon prompt takes about 15 sec, and after the logon button is pressed, it takes about 12 sec more to get to the desktop (and be able to work, not look at the hourglass). This does not change whether -no-kqemu is used. For the person for whom it works, with the same image - without the driver! - bootup took 6 sec to logon prompt, then 3 sec to desktop. In fact the very first Windows bootup after the install, where it probably did hardware detection, took nearly an hour. (kqemu was enabled). -- Yours, Mikhail Ramendik