inaccessible boot device

  • Thread starter Thread starter George Post
  • Start date Start date
G

George Post

Moved windows 2000 pro system drive to another computer
and it reports inaccessible boot device. Should be have
started detection of new computer. When I place the drive
back in the orignal computer it boots perfectly. Using IDE
connection off motherboard no raid just simple IDE drive.

I have tried using the winds 2000 pro CD to repair files
and console (fixmbr) and still get the same error. Put the
drive back in the original computer boots perfectly.
Powerquest (drive image) and Microsoft acknowledge the
problem but none of articles fix the problem. How can I
get this drive to boot?
 
Don't try repair the first time you get the option, try it the second.
You'll start the install, have the option of repair or install, choose
install. You'll then get the option to repair a current install or
remove that install and do a fresh one. Choose repair there, I've
hear that's the trick, haven't played with it though.
 
George - W2k, unlike NT, is very tightly bound at installation to the
hardware (motherboard, etc) it's installed on. You cannot simply move
the hard drive to another machine unless that new mainboard is virtually
identical to the original. If you search this newsgroup for threads with
the word "motherboard" in the subject line, you'll find many posts
detailing how to rectify your situation, many of them pointing to
various Microsoft knowledgebase articles. Sorry, I don't have that info
at hand.
 
These articles could help:

How to troubleshoot "Stop 0x0000007B" error messages in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;822052#6g; You
Receive a Stop 0x0000007B Error After You Move the Windows XP System Disk to
Another Computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314082

NT/2k/Xp/2k3 system, unlike 9x, cannot replace the chipset drivers
on-the-fly because it doesn't have direct access to the hardware; that's why
that Stop error occurs if the chipsets are different and there is no
appropriate registry keys and the drivers preinstalled. The same Stop could
appear also if the BIOSes are different, i.e. ACPI-awared and non-ACPI, and
this is the HAL compatibility issue (ACPI - Standard). Modern BIOSes are
pretty good ACPI-awared so this case is more rare and obsolete.

XP and W2k3 are very tightly bound at setup time to the hardware set of CPU,
chipset, HDD and video adapter, and you cannot replace that set at once
during upgrade w/o re-activation Windows. Moreover, IIRC, the activation
permits you changing every main hardware component no more than 3 times w/o
re-activation. But all that is an activation issue only.
 
Moved windows 2000 pro system drive to another computer
and it reports inaccessible boot device. Should be have
started detection of new computer. When I place the drive
back in the orignal computer it boots perfectly. Using IDE
connection off motherboard no raid just simple IDE drive.

I have tried using the winds 2000 pro CD to repair files
and console (fixmbr) and still get the same error. Put the
drive back in the original computer boots perfectly.
Powerquest (drive image) and Microsoft acknowledge the
problem but none of articles fix the problem. How can I
get this drive to boot?
Click to expand...
......................................
MOVING W2K TO NEW HARDWARE - several relevant posts
-------------------------------------------------------

From: "Bruce Chambers" <[email protected]>
Newsgroups: microsoft.public.win2000.hardware
Subject: Re: New Computer, but W2K refuses to run
Date: Fri, 20 Jun 2003 18:43:17 -0600

Greetings --

Normally, unless the new motherboard is virtually identical to the old one
(same chipset, IDE controllers, etc), you'll most likely need to perform a
repair (a.k.a. in-place upgrade) installation, at the very least (and don't
forget to reinstall any service packs and subsequent hot fixes):

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175

What an In-Place Win2K Upgrade Changes and What It Doesn't
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952

If that fails:

How to Move a Windows 2000 Installation to Different
Hardware
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q249694&ID=KB;EN-US;Q2
49694

Bruce Chambers

Help us help you:


----
You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

................................................
From: "James Barr" <[email protected]>
Subject: Re: Replaced Motherboard
Date: Wed, 28 Aug 2002 20:20:26 +0100

I had the same problem once and did the following which sorted it out:

Create an NT boot disk (format a disk on a 2000 machine [either pro or
server] copy to that disk the following files

boot.ini
ntdetect.com
ntldr
)
then edit the boot.ini and make sure the arc paths are correct for your
system then delete the /fastdetect switch.

Then boot from the floppy disk. Once you've booted once from the floppy it
should be OK to boot from the Hard Disk

Hope this helps

James

.....................................
From: "Bruce Chambers" <[email protected]>
Subject: Re: changing motherboards and CPU's
Date: Wed, 22 Jan 2003 19:53:20 -0700

Greetings --

Unless the new motherboard is virtually identical to the old one (same
chipset, IDE controllers, etc), you'll most likely need to perform a repair
(a.k.a. in-place upgrade) installation, at the very least (and don't forget
to reinstall any service packs and subsequent hot fixes):

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175


Bruce Chambers
Microsoft MVP - Shell/User

----
You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

........................................
[Source of following lost - sorry.]

Boot using your Windows CD
Go to the Repair Console and run the following options.

chkdsk c:
fixboot c:
fixmbr c:

See if they resolve the issue. Sometimes Windows 2000 disks aren't totally
pleased with being popped onto a new board as such.
 
Check out microsoft knownledge base article 822052 I've
use this many times with success..
 
Back
Top