4 replies
by rameter Accepted solution
by thechas Accepted solution
Well, to be honest, it is a big mistake to move a Windows XP or newer hard drive to a different system and boot up to diagnose a problem.
Not only have you triggered an activation event, you have greatly expanded the size of the registry. Should you move this drive back to the original system, all of the hardware and system file issues along with activation will turn up again. The registry might even grow even larger.
At this point, while it would be good to find the root cause of the original problem, your best option is to back up your personal files, format the drive and install Windows XP fresh from the CD.
After Windows is installed:
Install all the device drivers for the hardware.
Download and install Windows XP service pack 3, your anti-virus and firewall applications.
Go online and run Windows update.
Then, install your application software.
As far as fixing this type of problem in the future:
Create a slipstream disk with your current Windows service pack level.
Boot from the disk and perform an in-place upgrade / repair installation of Windows.
Chas
by seanferd Accepted solution
you don't put the drive under investigation into another system as a boot device. You connect it and set the jumper as a slave device.
You boot with the working OS of the good machine so you can read the data off the HDD with the corrupted install.
Also, it never helps to willy-nilly try "stuff" to fix a system. You find out where and what the actual errors are and then find the procedure to fix those errors. Fixing the boot record will have absolutely no effect on a machine that "mysteriously" reboots. It already booted up in the first place.
by twors88 Accepted solution
This discussion is closed to new replies.
Trending Malware posts
Sort by Trending