Charizard_Fire_God
*tiwts widdw head*
*sigh* I should probably post this on an actual computer forum... ah well, tch, here goes. Harddrives: Westerd Digital 40GB, Western Digital 80GB, Maxtor. 1 Partition each. WD 80GB has a dynamic partition. Norton GoBack installed on WD 40GB. All 3 HDDs compressed with NTFS's option.
If I wanna run a check on Maxtor, it does one at startup. Then it leaves an uncompressed, corrupted bootex.log.
It's a vicious circle. Ta fix it chkdsk has ta run at startup. But if it runs at startup it writes to bootex.log, and even though it finds the error and fixes the index it's still writing to it, tch, so it remains corrupted. It's a vicious circle.
Ta fix it I gatta put in the WinXP CD and boot the Recovery Console. Then I run "chkdsk /p", then "del bootex.log", fixing the error without writing to the log. My partition table gets damaged and I have ta use Partition Table Doctor so I can see what's on it again.
Internet advice said that bootex.txt becomes corrupted if tha scan is interrupted. I scanned twice, no interruptions, same problem. I have WinXP SP2, and scanned my HDD for bad sectors, found none. Its wires are properly connected and I've had no issues with it.
So why is it that bootex.log is always corrupt on my Maxtor when I run a scandisk at startup??? My Maxtor driver is okay btw. And I cannot config write caching. Tch... driver seems ta handle it automatically. >.=.>
If I wanna run a check on Maxtor, it does one at startup. Then it leaves an uncompressed, corrupted bootex.log.
It's a vicious circle. Ta fix it chkdsk has ta run at startup. But if it runs at startup it writes to bootex.log, and even though it finds the error and fixes the index it's still writing to it, tch, so it remains corrupted. It's a vicious circle.
Ta fix it I gatta put in the WinXP CD and boot the Recovery Console. Then I run "chkdsk /p", then "del bootex.log", fixing the error without writing to the log. My partition table gets damaged and I have ta use Partition Table Doctor so I can see what's on it again.
Internet advice said that bootex.txt becomes corrupted if tha scan is interrupted. I scanned twice, no interruptions, same problem. I have WinXP SP2, and scanned my HDD for bad sectors, found none. Its wires are properly connected and I've had no issues with it.
So why is it that bootex.log is always corrupt on my Maxtor when I run a scandisk at startup??? My Maxtor driver is okay btw. And I cannot config write caching. Tch... driver seems ta handle it automatically. >.=.>