I've used "Easy Duplicate Finder" on 64 bit Win7 and 32 bit WinXP machines. The last paragraph in the post describes a problem to which I am seeking.
On the Win7 64 bit machine, I particularly like the feature that allows me to delete all the duplicates within a given directory when a duplicate has been found in that directory. In most cases, I'm pretty sure where the redundant files are stored, and I want to clean out those directories, but I don't want to delete anything that is not replicated elsewhere. That feature enabled me to do that very quickly. Using another tool, I was able to quickly delete the resulting empty directories.
The above, "delete all in given directory," feature does not seem to be present on the WinXP 32 bit machine installation.
On the Winxp 32 bit machine, when commanding the deletion of a group of selected files, the machine will return the message that some of those files have not been deleted. Going back and "trying again" yields the same result even after a substantial wait, yet I can immediately delete each file manually one by one. Most all of the reasons listed for why a file or files can't be deleted don't make sense inasmuch as I can delete files one by one. When seeking to delete some groups of files, "Easy Duplicate Finder" does tax the processor to the point where it is consuming half of processor resources, but whether or not the deletion fails does not seem to be related to processor load or required processing time. As I've sorted the files by size, all the files in any deletion group are roughly the same size; it is not that I'm accidentally including a large file into the group. The deletion problem does not seem to be tied to where individual files are located in some higher level directories or the type of file being deleted.
Suggestions on how to get around the problem will be welcomed.
