You know occasionally Windows XP boots up into a self-started CHKDSK run marked as a "consistency check"... you can press a key to skip it.
Well, my suggestion, LET IT RUN!!!
It's kindof like the maximal mount count exceeded, forcing fsck in Linux, I'm guessing.
I skipped this check a handful of times, and then one day I decided to just go ahead and play some MP3 off of my D drive. Much to my dismay, WinAmp couldn't find my playlist entries. So I decided to check the MP3 directory, and when I tried to open the D drive, I got an error box pop up saying the data structure on the drive was corrupt, and the drive couldn't be read. Joy.
A chkdsk later everything was jolley again, and MP3's flowed once again.
Either way, just let those consistency checks run.
I for one think that from day 1 there's something wrong with XP's disk management and/or drivers, as this never happened to me in Win2K. But hey, I'm just a stupid consumer, what do I know.
SunnyD
Well, my suggestion, LET IT RUN!!!
It's kindof like the maximal mount count exceeded, forcing fsck in Linux, I'm guessing.
I skipped this check a handful of times, and then one day I decided to just go ahead and play some MP3 off of my D drive. Much to my dismay, WinAmp couldn't find my playlist entries. So I decided to check the MP3 directory, and when I tried to open the D drive, I got an error box pop up saying the data structure on the drive was corrupt, and the drive couldn't be read. Joy.
A chkdsk later everything was jolley again, and MP3's flowed once again.
Either way, just let those consistency checks run.
I for one think that from day 1 there's something wrong with XP's disk management and/or drivers, as this never happened to me in Win2K. But hey, I'm just a stupid consumer, what do I know.
SunnyD
Facebook
Twitter