Win2K - Stop Errors "inaccessible boot device"

[CraigRT]

I am not sure if win2k likes having itself cloned, I ghosted a HDD and was going to install it into a newer rig for a friend and when I go to boot it up for 1st time it says "***STOP: yada yada incaccessible boot device"
I tried the original HDD and the freshly cloned HDD and both do the same thing, the system is a P3 866 on an Asus CUV4X-E motherboard the HD's are Fujitsu 8 and 20 gig drives. the comp it was coming out of is an Asus P2B, P2 350 system.

can y'all help me out? I'd rather not tell the guy I have to format his drive cause he doesn't want that.

Thanks.

 

[Shadow07]

What are the hex numbers after the stop message? And, what version of Ghost are you using? You can try getting a Windows 98 boot disk, booting off of it, and typing FDISK /MBR at the prompt. Most times with the older versions of Ghost, it did not know how to properly handle NTFS Version 5.

 

[loosbrew]

well, the problem is because you gohsted the image froma one pc that has a totally different hardware config than the one you want to image. think about it, the image you made has all of the registry entries and drivers and such from the one machine, how would you expect it to work for some other mother board? if you dont have the same hardware configs than ghosting isnt the route you should go. maybe im wrong, but i would format and reinstall...

hth and good luck
loosbrew

 

[CraigRT]

well, for reasons that you are talking about I kept the file system at FAT32
and I dunno which version, it came with my old Soyo SY-6BA+IV.
the Hex numbers go like this:

*** STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)INACCESSIBLE_BOOT_DEVICE

 

[CraigRT]

I know it's not the way to go but it's not upto me, and I must say actually I've never had it not work, windows is suppose to detect new hardware, prompt for drivers, and install them, it's not suppose to not boot up at all. but I know what you mean. this thing woulda been setup and already running on a fresh install if it was me!

 

[Shadow07]

Check this link out.

 

[nortexoid]

it's probably due to differing chipsets controllering the ide channels...

for example, say you ghosted the hdd from a system w/ a via chipset and had installed the via ide bus master drivers for win2k on that particular system...u then toss it in an intel i815 chipset board and wonder why it's unable to access the boot-device when it's trying ot use the via ide bus master drivers on the intel i815 board...

basically, win2k is complete sh1t when it comes to handling boot devices that have altered, etc...i got the same error updating ide drivers and had to use the last good configuration, which has worked once and failed once...causing me reinstall my OS once...pain the ass.

 

[cheapbastich]

well, I get this error simply by installing sp1, or the hotfix for ata100-
so, bright guys, what causes it and how can it by fixed? still cant use
my system here..............going on 2 months now.........

 

[Shadow07]

I would try two different things here. One, I would use a Windows 98 boot disk and run FDISK /MBR. Second, I would not install the ATA100 hotfix, and then try to install SP1, if the problem is you install the hotfix then SP1.

Also, what are your system specs?

 

[yos]

Cheap--
Did you try this?

from MS Knowledge Base

-Yos