Warp <war### [at] tagpovrayorg> wrote:
>   The other, lighter defragger is behaving the exact same way: It's just
> refusing to move these small files, and consequently failing to defrag the
> one huge file. No reason is given in either the visual representation of the
> drive (all these tiny files are colored as regular, movable data) nor the
> analysis reports for this.

>   I can't understand why both programs are doing this.

Sounds like there's some serious reason to not touch them. Maybe they're
currently open whenever you run defrag?

Tried booting in safe mode and then defragging? That should reduce the number of
processes running, and thus the number of open files.

Post a reply to this message