Possible Bug: exclude directory not exact
Posted: Thu Jan 05, 2012 3:39 pm
I've found something to not work as it is probably intended.
It makes perfect sense to protect the C:\Program Files folder, which I would want to do.
I also have another folder however, "C:\Program Files NoInstall", which I use for portable software and single executables (such as the sysinternals suite).
Duplicate Cleaner refuses to remove files from this directory with the "protect C:\Program Files" option on.
Accordingly, it seems to protect C:\Program Files* instead of "C:\Program Files".
If this is intended behaviour, please rename it accordingly.
I would however find it unwanted to automatically exclude a user generated directory.
By the way, nothing to do with this, but I've been wondering about this; MD5, SHA-1 and SHA-256 can be used, but I have not found enough information on the web to decide which one of them is best to use. Maybe you could add a small overview of the differences and their use under different scenarios. I've found sha-1 to be fairly slow, for instance.
It makes perfect sense to protect the C:\Program Files folder, which I would want to do.
I also have another folder however, "C:\Program Files NoInstall", which I use for portable software and single executables (such as the sysinternals suite).
Duplicate Cleaner refuses to remove files from this directory with the "protect C:\Program Files" option on.
Accordingly, it seems to protect C:\Program Files* instead of "C:\Program Files".
If this is intended behaviour, please rename it accordingly.
I would however find it unwanted to automatically exclude a user generated directory.
By the way, nothing to do with this, but I've been wondering about this; MD5, SHA-1 and SHA-256 can be used, but I have not found enough information on the web to decide which one of them is best to use. Maybe you could add a small overview of the differences and their use under different scenarios. I've found sha-1 to be fairly slow, for instance.