From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CeJzK-0003GN-Qw for qemu-devel@nongnu.org; Tue, 14 Dec 2004 16:13:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CeJzI-0003Eb-9v for qemu-devel@nongnu.org; Tue, 14 Dec 2004 16:13:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CeJzH-0003EV-VI for qemu-devel@nongnu.org; Tue, 14 Dec 2004 16:13:40 -0500 Received: from [216.58.162.138] (helo=netraverse.com) by monty-python.gnu.org with esmtp (SSLv3:DES-CBC3-SHA:168) (Exim 4.34) id 1CeJku-0003En-1u for qemu-devel@nongnu.org; Tue, 14 Dec 2004 15:58:48 -0500 Received: from [69.165.224.96] (account lreiter HELO [10.1.0.1]) by netraverse.com (CommuniGate Pro SMTP 4.0.5) with ESMTP-TLS id 3708740 for qemu-devel@nongnu.org; Tue, 14 Dec 2004 13:25:27 -0700 Message-ID: <41BF53FA.4010307@verbmail.com> Date: Tue, 14 Dec 2004 15:58:34 -0500 From: Leo Whitman MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Windows 2000 disk full problem during install... Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: QEMU Developer Mailing List Hello, I was wondering if anyone had a chance to look into this problem more. I've done a great deal of research myself on it so far, but do not yet have a solution. Most of the c:\winnt\security\edb*.log files that fill up the disk are created during the hardware scan stage in the GUI portion of the install. I'm using Windows 2000 Professional, on QEMU 0.6.2 (latest from CVS) and have encountered the problem on any flavor of Linux I try. I did try to set the disk geometry manually with -hdacs to /16/63. This helped a bit - basically delayed the disk filling up until later in the hardware scan. Without this parameter, the log files fill the disk pretty much right at the beginning of the hardware scan. I also tried a small patch to hw/ide.c (without the multithread bits) , from Vladimir N. Oleynik. Basically only the s->status is set to READY_STAT instead of READY_STAT | SEEK_STAT in/around hw/ide.c:1472 from that patch. This did not solve the problem at all. I'm willing to keep investigating the problem, but was wondering if any others had ideas in the meantime. Thank you, Leo Whitman