Well let me tell you why.
SP2 rearranges almost every system file on your computer.
It may use 400 MB to backup SP1,
then a couple of GB's to install the SP2 files,
then it deletes the original OS files.
After the install your files have literally moved about 3GB down the disk.
An area of the disk that may not have been used for years.
Even if you do a defrag there is still a completely different arrangements
on your disk so moving the system files back to the front of the disk puts
them in a different locations.
If you have a bad spots on your disk (bad sectors) they will not show up
until something is written to them or something that is there needs to be
read, but the sector is bad now.
File Errors - how many different kinds? Many.
Now let's look at the logical recovery of a file error.
Is it data - recover your data file or recreate it.
Is it a program file - recover the backup program file or reinstall the
program.
Is it a driver - BSoD or strange symptoms. Debugging and reinstalling
driver.
Is it a system file - opps, a bad sector or a bad driver corrupted it, or a
virus, - debugging.
So before you do any of these recover things you first what to know why.
The first place to start is to check the disk to make sure the disk is good.
Check disk with scan for bad sectors in Recovery Console.
Next use disk MFG diagnostic software.
Next scan for viruses.
disk clean up
adware cleanup,
Now you start debugging or recovery of files.
Where is NTFS all this time?
No where because it is simply a structure on the disk.
The NTFS.sys driver is what makes it work and the only thing that uses that
is the XP OS.
BSoD's are sometimes on purpose to protect the files.
About the only thing that can clobber NTFS is a bad disk.
And that's why NTFS is the safest File System Windows has ever had and that
is why it needs to be used but it does not cause errors. I only retains the
files that were corrupted by software and bad hardware.
SJ
