From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BXDcf-0005dC-KI for qemu-devel@nongnu.org; Mon, 07 Jun 2004 02:28:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BXDcd-0005c7-Ue for qemu-devel@nongnu.org; Mon, 07 Jun 2004 02:28:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BXDcd-0005bS-28 for qemu-devel@nongnu.org; Mon, 07 Jun 2004 02:28:39 -0400 Received: from [206.72.67.39] (helo=claudius.sentinelchicken.org) by monty-python.gnu.org with smtp (Exim 4.34) id 1BXDc2-0008Tr-S4 for qemu-devel@nongnu.org; Mon, 07 Jun 2004 02:28:03 -0400 Date: Sun, 6 Jun 2004 23:28:17 -0700 From: Tim Subject: Re: [Qemu-devel] NE2K PCI and Windows 98SE & Cirrus Logic Message-ID: <20040607062817.GB5496@sentinelchicken.org> References: <40C39F70.5070205@dad-answers.com> <1086584098.887.18.camel@shawn.local> <20040607052424.GD3296@sentinelchicken.org> <1086586624.887.21.camel@shawn.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1086586624.887.21.camel@shawn.local> 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 > > I am using the most recent CVS (at least, as of this afternoon), and the > > following command line: > > > > qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT" > > > You're running Windows 2000 with PCI enabled? I didn't think this worked > yet - certainly all of my attempts so far to get this running have > failed. Did you have to do anything special to get PCI mode working with > Windows 2000? Nope, not really. I always rip my install media to files, and install from there, but other than that, nothing extraordinary. In fact, I installed with the same exact line above off a fairly recent CVS, with only the boot option changed to `d'. My host system is Debian unstable, using a custom 2.6.6 kernel, based on Debian's kernel source. The NIC in windoze detects as a "Realtek RTL8029 (AS)-based PCI Ethernet Adapter". One quirk though... when I first did the install the other night, I had forgotten to set up my network startup script. Windows installed fine, detected the NIC even, and let me configure it. From then on, ipconfig from the command line reported the proper network configuration, however, the GUI interface for changing the TCP/IP settings was not configured as I had done during install. Even after I changed the settings manually and "rebooted", the win2k guest OS wouldn't update the TCP/IP config. (This is even after I got the network tun0 script working). Later, I re-installed, with the network script operational, and haven't yet ran into the same difficulties (though, I haven't extensively tested). The GUI interface in win2k does report the proper network config though. On the downside I have not been able to install SP4 yet. No matter which install method I use, I always get "An error occured", and then it quits. Thanks so much for your verbosity Microshaft... hope that helps, tim