![](http://content.invisioncic.com/d154966/set_resources_6/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
testor
-
Posts
3 -
Joined
-
Last visited
Posts posted by testor
-
-
There is nothing wrong with your computer, it is an issue with Defraggler v1.08.132.
Not believing Defraggler would have a problem, I tested 18 hard drives in at least 7 computers. DOS prompt Chkdsk and GUI started 'error checking' was run on reboot with same results.
Version 1.07 worked great and the new features being introduced in v1.08 looked very good.
I made a mistake in downloading, then deleting, version 1.07 before v1.08 testing was complete. Now I need v1.07 back... How can I find it so it can be used until v1.08 is fixed?
I'm a newbie to the board and as such, I made a mistake and posted this under a different thread. Sorry for confusion.
-
There is nothing wrong with your computer, it is an issue with Defraggler v1.08.132.
Not believing Defraggler would have a problem, I tested 18 hard drives in at least 7 computers. DOS prompt Chkdsk and GUI started 'error checking' was run on reboot with same results.
Version 1.07 worked great and the new features being introduced in v1.08 looked very good.
I made a mistake in downloading, then deleting, version 1.07 before v1.08 testing was complete. Now I need v1.07 back... How can I find it so it can be used until v1.08 is fixed?
$BadClus:$Bad fragments
in Defraggler
Posted
What is and how do we get rid of $BadClus:$Bad fragments.
Defraggler v1.16 & v1.17 quits when it starts processing this large portion of the hard drive. When I look at several blocks $BadClus:$Bad fragments are referenced and mixed with actual file names. An 80gb drive with only 9gb of data.