From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BQeYa-0006j1-Ok for qemu-devel@nongnu.org; Wed, 19 May 2004 23:49:20 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BQeY3-0006O6-NZ for qemu-devel@nongnu.org; Wed, 19 May 2004 23:49:18 -0400 Received: from [203.63.55.34] (helo=wallace.eclinic.com.au) by monty-python.gnu.org with smtp (Exim 4.34) id 1BQeY2-00062m-Px for qemu-devel@nongnu.org; Wed, 19 May 2004 23:48:47 -0400 Subject: Re: [Qemu-devel] Re: Qemu-devel Digest, Vol 14, Issue 38 From: Leigh Dyer In-Reply-To: <200405191240.07909.bobb@absamail.co.za> References: <200405191240.07909.bobb@absamail.co.za> Content-Type: text/plain Message-Id: <1085024495.20108.53.camel@shawn.local> Mime-Version: 1.0 Date: Thu, 20 May 2004 13:41:35 +1000 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bobb@absamail.co.za, qemu-devel@nongnu.org On Wed, 2004-05-19 at 12:40 +0200, Bob Barry wrote: > Leigh - > > On Wed, 2004-05-19, you wrote: > > I also tried > booting a Win2k system, but it failed with an > > INACCESSIBLE_BOOT_DEVICE error (common when > > trying to transplant a Win2k system in to a new PC) > > I just encountered the INACCESSIBLE_BOOT_DEVICE error > while trying to install WINNT4 using today's CVS, and Vaclav > reported the same yesterday. Is there a workaround for it? > Not that I know of - it usually means that the OS doesn't have drivers for, or hasn't properly detected, the IDE controller. I haven't been able to get my preinstalled Win2k system to boot on the PCI bus yet (though I haven't tried much yet), and an attempt to install a fresh Win2k system with PCI enabled yesterday got just over halfway through the hardware probe and then moved no further (well, in the three hours or so that I ran it). I also tried installing NT4, but it failed before getting to any INACCESSIBLE_BOOT_DEVICE messages - the first-stage installer, after detecting the IDE controller, failed to see any drives connected to the controller. Thanks Leigh