There was a potential issue with earlier builds of DK V7 and boot time
defragmenting. They were neglecting to verify that no other processes had
the drive opened for write access during the boot time defrag. Initially,
Executive's response was that it was a BIOS issue but they eventually
released an update (Build 430) that includes the following:
The Diskeeper NTFS boot-time engines have been modified in this build to
verify they have exclusive access to the volume being defragmented. This
change ensures that no other drivers or services can modify the volume while
the boot-time defragmentation is running. If the volume cannot be locked,
an error message appears describing this and the boot-time defragmentation
will not run.
This may have been what you saw on your system.
- Greg/Raxco Software
Microsoft MVP - Windows File System
Disclaimer: I work for Raxco Software, the maker of PerfectDisk - a
commercial defrag utility, as a systems engineer in the support department.
Want to email me? Delete ntloader.
Jim Romanchek said:
I don't have an explanation for why it crashed. The computer had been running
slowly. I did a normal defrag and it helped a lot. As I was exploring
different capabilities of DK I saw the boot time option and thought I could
improve the performance even more. When I ran it, I got page after page of
"file recovery notices" or something like that. When all was over, the system
wouldn't boot. It just hung up. Eventually I reformated the drive and reloaded
everything. Since then I've been gun shy of ever trying the boot time defrag
again.
I was running W2k, SP2 I think back then. It was on my son's computer and he
used AOL IM all the time. I'm just guessing that it was caused by some of the
debris that IM leaves on the hard drive.
Jim