problems with chkdsk

[Wigwam]

HI

i tried to run the boot-time scheduler for diskeeper but it said "volume slated to have chkdsk run...cannot run on a dirty volume". i always select the run chkdsk first option anyway.

i tried the manual defrag [which was working fine last night] and got the message that chkdsk has been scheduled to run...run chkdsk/f.

when i run chkdsk from the run prompt it runs fine in read only mode but tried /f and it says cannot lock volume and asks to schedule on reboot...btu never seems to run on rebooting.
i then tried the /r thing anf on reboot the light blue screen did come up but i got the message:
"cannot open volume for direct access". finished checking windows.

and diskeeper is still stuck in saying chkdsk has been scheduled by the OS or an app [itself!] to run and wont do anything on c [although it defrags my other partition fine]

please tell me how to solve this. in the meantime my startup has also noticably slowed and i always see the "starting windows" option before the users page but not before i just set this boot-time defrag

 

[Wigwam]

i just tried logging via safe mode to see maybe i could do anything from there but everytime it hangs when it scrolls down the drivers at "Mup.sys" . i left it for 15min at 1 stage but still no progression

 

[bacillus]

have you got zone alarm version 5 installed?

 

[Wigwam]

yes i do as a matter of fact.
what does that do/cause?

in the interim i have done a system restore to a couple of days ago. it allows normal functionality again in that when i rebooted after it, it ran chkdsk okay, and the "manual" diskeeper ran but been too chicken to run the boot time scheduler...and i wont now until i hear more about the ZAPro 5 problems!

 

[Wigwam]

DOH!
google is my friend. done a clean uninstall of ZAPro 5 and gone back to 4.5...