From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BYHqk-0007wU-C8 for qemu-devel@nongnu.org; Thu, 10 Jun 2004 01:11:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BYHqi-0007wI-M5 for qemu-devel@nongnu.org; Thu, 10 Jun 2004 01:11:38 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BYHqi-0007wF-Kc for qemu-devel@nongnu.org; Thu, 10 Jun 2004 01:11:36 -0400 Received: from [206.72.67.39] (helo=claudius.sentinelchicken.org) by monty-python.gnu.org with smtp (Exim 4.34) id 1BYHpv-0000ZL-NK for qemu-devel@nongnu.org; Thu, 10 Jun 2004 01:10:48 -0400 Date: Wed, 9 Jun 2004 22:10:45 -0700 From: Tim Message-ID: <20040610051045.GA1675@sentinelchicken.org> References: <000a01c44e94$c844b990$0401a8c0@putte2k> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000a01c44e94$c844b990$0401a8c0@putte2k> Subject: [Qemu-devel] IDE issues?? (Was re: NE2000 problem found) 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 > Guest: Windows 2000 sp4. Sorry to change the subject, but how did you go about getting sp4 to install? I have tried numerous changes and installation methods within the guest OS, but SP4 just refuses to install. It stops while "checking for disk space" right before the final step, and then stops, saying "an error occurred". I am currently booting with: qemu -pci -cirrusvga -m 256 -cdrom win2k-install-cd.img\ -hda win2k-cow.img -boot c -n "$TUN_SCRIPT" I created the win2k-cow.img with: qemu-mkcow win2k-cow.img 6144 It has been this way for quite a while, and under slightly different boot options. I read in another thread that the IDE driver shows up in a weird place in win2k's device manager. Is it possible there are still issues that need to be worked out with the IDE emulation? Sorry, I don't know enough about this low-level stuff to debug it myself. Are there some logs in the guest or in qemu that I can turn on that would help someone squash this one? I appreciate any guidance. thanks, tim PS- the cirrus emulation under win2k has been great so far (only tested this evening). Some broken-ness when switching modes in guest, but after a restart of qemu, it all went back to normal.