One solution is to get a new machine which does boot, and temporarily hook
this drive up as an additional slave to the IDE - and see whether you can
'see' it as a drive from the first one. At least you might be able to rescue
some data from it that way.

David Clover
========================
IT Support Manager
Maths and Computing Faculty
The Open University
========================
Ext: 59367/53529
Tel: 01908 653529
Fax: +44 (0)709 236 3568
Voicemail: +44 (0)705 069 9440
========================



-----Original Message-----
From: David Grabbe [mailto:[EMAIL PROTECTED]]
Sent: 10 March 2002 16:54
To: CF-Talk
Subject: RE: INACCESSIBLE_BOOT_DEVICE error on Win2k


        Both systems (fried and new) are IDE...the old m-board is "legacy" (old)
enough that I haven't been able to find a matching model.

David

-----Original Message-----
From: Neil H. [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 10, 2002 11:45 AM
To: CF-Talk
Subject: Re: INACCESSIBLE_BOOT_DEVICE error on Win2k


Are you using the same Drive Controller (I.e. IDE or SCSI).  We have found
that if you have the same motherboard to use temporarily you can install
drivers for whatever else you are using beforehand.

Let us know what you figure out.

Neil

----- Original Message -----
From: "David Grabbe" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Sunday, March 10, 2002 11:28 AM
Subject: WOT: INACCESSIBLE_BOOT_DEVICE error on Win2k


> Hello all,
>
>         This is not even remotely a CF question  :)  but the contributors
to
> this list have a broad range of experience, so I'm hoping somebody has run
> into this before and has a solution.
>
>         One of our older Win2k machines went down -- the m-board is fried
> (bad power supply) but the HD seems to be OK.  I tried hooking up the old
HD
> with a new m-board/processor.  When I try to boot up, Windows starts going
> through its normal boot sequence, but then always "blue-screens" with a
STOP
> error message that says "INACCESSIBLE_BOOT_DEVICE".  I've gleaned enough
> from MSDN to know that Win2k doesn't like it when there is a radical
> hardware change (i.e. different motherboard and proc), but their
suggestion
> to "reinstall Windows" isn't an option at this point.  Has anyone run into
> this before?  Any solutions?
>
> Greatly appreciative,
> David
>
>
>
> ------------------------------------
> David Grabbe
> Manager, Information Systems
> Church of the Great God
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> http://www.cgg.org <http://www.cgg.org/>
>
>
>


______________________________________________________________________
Why Share?
  Dedicated Win 2000 Server · PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
  Instant Activation · $99/Month · Free Setup
  http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to