Russell,
what it is saying is that chkdsk needs to fix a problem on your volume c:
i.e. chkdsk /f . I couldn't tell you how to disable chkdsk, to me that doesn't sound like the way
to go anyway- you need to correct the errors and that will turn off the chkdsk (sorry if this sounds
basic but I've found the best way to correct problems on computers is to think in in basic &
black/white terms and start investigating.... start with what you know, then go from there).
how are you starting chkdsk, ru starting it from a command prompt or are you starting it from your
windows cd? I'm not sure whether it has any basis or not to this problem but I'm just investigating
(my thinking is the 1st option would be running it from the GUI which MAY be causing a conflict of
some sort with defrag) ... I personally would use the later of the 2 options myself. from what
you've said it tells me that chkdsk hasn't fixed the problem, so...why not? why not try the other
way and see if that does the trick, can't hurt can it?
here's a clue that I would follow up on...now I'm not saying this is the answer, not at all, but its
just something I came across that I hadn't heard about before that relates to chkdsk & defrag
problems so it sparked my curiosity... just a note of warning, it does say that you should be pretty
competent before playing in this area (which I am assuming you are not overly so) but that doesn't
stop you from investigating and possibly giving a professional a heads up to what the problem could
be, if you get my meaning. anyway here's the clue:
"You cannot defragment volumes that the file system has marked as dirty, which indicates possible
corruption. You must run chkdsk on a dirty volume before you can defragment it. You can determine if
a volume is dirty by using the fsutil dirty query command. "
PROCEED AT YOUR OWN RISK.
my next advice would be to contact a real professional to get their advice- try here:
http://www.microsoft.com/communities/MVP/MVP.mspx
let me know how you get on, I'd be very interested.
good luck.
Paul
Paul l still get this message when l try to defrag straight after boot up