This is a general Windows question I placed in this category because the PC just happens to use W2K, but likely (maybe) applies to all Windows versions. It's a real simple question.

If a PC with Windows 2000 installed gets irreparably damaged, but the hard drive is still perfect and pristine, can that hard drive be installed into another comparable PC (replacing any hard drive it had) such that it will more-or-less seamlessly boot up with your W2K and all your other stuff?

[Note: MBR stands for Master Boot Record]

I believe that when transferring hard drives from one computer to the other windows will have to be reinstalled.

I concur with townsbg. You could only "switch" hard disks from one machine to another (without a reinstall of the OS) with up to Win98SE.

Even then there were a couple of things that should be performed to avoid problems/slowdowns of the "new" machine.

Thank you, both responders. Though I'm disappointed to hear the bleak truth.

I don't know how this theoretical situation applies to linux but doing so in windows could lead to registry as well as driver issues so it is best just to start over.

I don't know how this theoretical situation applies to linux

Some folks without CDROMS or USB Boot support do pull their IDE Hardrive and install via IDE to USB adapter. No registry in Linux. Plus the kernel will recognise the new Hardware and install appropriate drivers/modules usually to get you up and going enough to finish tweaking hardware if needed.

For a Drive that ran for years though on one computer and is loaded with changes specifically for said computer lets say like a Hewlitt Packard. It will be a crap shoot moving it to a lets say a Acer Box. Kinda hit and miss. YMMV

Thanks for sharing that. So pertaining Linux, would it be best to reinstall?

I think with windows the big problem is the registry. Drivers will have to installed specific for the hardware and hopefully the old completely uninstall and not conflict with the new but the registry stores hardware information & it could be looking for hardware thats not there which could possibly cause a crash or lockup. I could be wrong about that though but I do know that its best to start over because there are already so many variables that can cause a crash that you don't want a few more.

Your files could always be moved off the drive and your OS reinstalled provided you have the installation media (ie disk or floppies).

Thanks for sharing that. So pertaining Linux, would it be best to reinstall?

If you can boot as far as init 3 (which is what you would call and I am trying to explain in loose terms, \>) which inti 3 gives you access to a bash shell prompt (which is usually this symbol $) you can pretty much do anything to get to a Desktop and from there straighten out any sound issues or any other hardware related issues like wireless.

Lockups,freezes, mostly (because beta testing Linux software you can experience a lockup. Because we are a communty who collectively work out the bugs in New Software as Testers. Of which I am one) are 90% usually Hardware related.

If you lets say swap a drive from one computer to another. It won't freeze or lockup .
It will either stop booting giving a error message (which is possible to work around sometimes) or once getting to a Desktop. You will have no sound or wireless or whatever. Which can be tweaked later wih the right Linux firmware and driver.

The Kernels now a days come packed with different modules/drivers to meet a lot of different hardware needs. Vesa driver will give you a screen on a computer from Pentium MMX to Dual Core.

Just one command in Debian based distros will reconfigure your system to bring up a screen from a init 3 prompt.

dpkg-reconfigure xserver-xorg

as root user. In Ubuntu you would just type sudo in front of that command to run it as root.

When a system boots, it is the system BIOS program that runs first. After doing the preliminary checks, it gets ready to load the Operating System; for that, it looks for Master Boot Record information inside the computer. This is available in the C partition of the Internal Hard drive. Just in case the internal Hard disk has failed to run, BIOS program will look for the next device for MBR.

That's mighty enlightening y'all -- thank you!

I started this thread because I was just thinking ahead: I presumed my PC was irreparably damaged when it's power supply box (external/detached) shorted out with a very loud crack; and after the short-out I saw my CD access light dim and pulsating. I thought, "Oh no! ..some crazy unregulated power is still bleeding through". As it so happens though, when I eventually purchased a new power supply box, everything was just 100% fine.
Unbelievable luck!