This thread is a little confusing; normally you cannot switch a hard drive to another computer with a different motherboard and boot it unless it uses the same chipset for IDE controllers. The result is a 7b type error (inaccessible boot device). You can access it as a "slave" -- and that may be what you did to scan it.
If you have reinstalled the OS on
his computer and are still unable to boot in any configuration -- but do not want to do a completely clean install -- there may be one last hope -- but it will likely result in all programs needing to be reinstalled since registry information will have been lost for them.
Since you have reinstalled the Operating System there are no System Restore points left to access -- so it will only be possible to try the first stage of the instructions below >>
------------------------
If you do not have an XP CD download rc.iso from Elvandil's post here:
http://forums.techguy.org/windows-nt...ml#post4622868
Burn the .iso file to CD. With Nero or Roxio you should only need to "open" the file and it will start the burner's ISO burning program.
DeepBurner can also be used to burn ISO files, I recommend the “portable” version:
http://www.deepburner.com/?r=download
Once that is done, you need to boot with either that or the XP installation CD to the Recovery Console. You may need to ensure that the CD drive is the first boot drive in the BIOS setup if it just boots to the same screen. Setup is accessed by looking for the key to press on the first data you see on the screen -- often F2
Directions are given here:
http://attachments.techguy.org/attac...chmentid=62075
There are several things to note about this operation.
1 > it is not a "reinstall" of Windows, but a method of accessing System Restore.
(this does not apply to your situation)
2 > all command lines are one line with appropriate spacing -- the doc file does not always reflect this.
3 > you must complete all 3 parts for it to be a proper restore. (
won't apply after an OS reinstall which removes restore points)
4 > in the first part of this document you are given the command:
copy C:\windows\repair\system C:\windows\system32\config\system
you may get a "file not found" when running this command. If you do, substitute this command instead:
copy C:\windows\repair\system.bak C:\windows\system32\config\system >> See also: http://support.microsoft.com/kb/307545/en-us note the warning in this article. But if you have an OEM system and no other choice but a clean install -- try it anyway.
--------------------------------------------
By the way:
A Page Fault in Non Paged Area can be a RAM fault -- has the memory been tested? If not I would do this before trying the above.
Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.
Beginners Guides: Diagnosing Bad Memory Memtest86 - A Stand-alone Memory Diagnostic