how2move w2k to new MB??

[adelatorre2]

I have a working win2k system running on a gigabyte bx2000+ w/P3-650, I run sysprep -nosidgen -pnp, the system shuts down.

I then move the HD & video card to a new asus a7v133 mb and boot, the system halts with an inaccessible_boot_device message.

Drive is a 27gb seagate ata/66, it was on the primary ide controller in both systems.

I can not figure out why this is happening.

Any help greatly appreciated.

[Bovon]

We sometimes encounter problems when moving a hard drive from one bios system to another, but they will usually boot. Try to get into bios, and set it to auto detect the hard drive. If the new bios has not detected the drive parameters, it will not know where to start looking for the boot info. When a system is first loaded onto a hard drive, the boot data is put at a certain place. If that drive is placed into a new system, the bios may not know where to find the boot data, and will fail.

A couple of other things I forgot to mention.

Recheck that the ribbon cables have the red stripe on #1 pin, both on the mobo IDE header, and on the hard drive...be sure they are plugged in good.

Swap out the ribbon cable, if you have another...

Check to be certain you have the drive jumpered as master.

Check that the power cable is seated good.

[This message has been edited by Bovon (edited 04-15-2001).]

[daveleau]

There are ways to get into the registry and kill alll the BX chipset resources and then let them be found again by the KT133A chipset, but this is a dirty way to do this. It is highly recommended that you reformat the OS partition. Any other partitions with data will be fine.

Dave

[flash4master]

you can sometimes pull it off with Win98, but Win2K is a major PITA to switch hdd's...just back everything up and format

[adelatorre2]

It just blows me away that an operation as routine as upgrading a MB is impossible without a complete OS re-install.

I thought that this was the whole point of the sysprep utility, so you could move an existing system to new hardware and have it redetect what it needs.

Windows 2000 sucks in this respect. I've moved NT from 486 all the way up to P3 and never had a problem.

[BBA]

Motherboard replacement is not "Routine".

I would classify it as the major 'system upgrade' component.

( Even MS considers that the same...wait until XP is here and you have to re-register it after changing a video card, lol ).

Anyway, Win98 seems to be the best at motherboard swaps for recovering itself. The W2K designers had no intentions of supportting that.

[ooops]

One last thing to try before a clean install , is to continue to re-boot the system ( 5-10 times ) ..... I've done this in the past , and I "think" it's Win2000's way of slowly readjusting itself ...... but ideally a clean re-format and install is always preferred ...... I've read deep in MS Support files somewhere , they even advise in certain instances to re-boot continually through some probs .... go figure....