DigitalVolcano Software Support

Fool> I'm kindof getting tired of your responses, they're all rude on some level, and ignorant.

When a file is marked read-only, it means it _should_ only be read from. Most apps (Windows included) use this to flag the user and warn them, but give them the option of continuing and modifying/deleting the file anyway. Which is how it should be.

If you were talking about file security, you'd be a little closer to accurate... if I don't have NTFS permissions to delete a file, there's nothing that can be done to override this, except for changing the NTFS permissions themselves (which you have to have NTFS permission to do).

DC could certainly provide an option to ignore the read-only flag... as I never saw this issue in 1.4.7, I'm assuming it was able to delete read-only files.

PS: Different James than the OP, above

Duplicate Cleaner 2.0.5 (next update, not out yet) uses a different delete routine which isn't sensitive to read-only files (as per 1.x).

Same thing - there are delete errors and no files deleted. Tried moving them, tried renaming them, and not luck. Any suggestions or should we just punt?
Thanks

Next update should help - out very soon!

cannot delete file error. 3,528 files to delete. 0 success. Tried same things as CWJ, no joy.

error on download too!

2.0.5, XP SP3, NTFS

If there is intended difference in handling read-only files, I am not seeing it. (I hadn't, by chance I suppose, run into issues before, just testing.)

As a test, copied DuplicateCleaner install into a subdirectory. Marked the files in that directory as read-only.

Scan of install directory on Content. Finds the dups. Attempt to delete, bypass Recycle Bin & nothing deletes.

Log shows:

Delete Error: C:\DEV\DUPLICATE\DuplicateCleaner205\abc\AudioGenie3.dll : Access to the path 'C:\DEV\DUPLICATE\DuplicateCleaner205\abc\AudioGenie3.dll' is denied.
...

Removed the read-only attributes, & the files deleted as expected.

Also I'll note, that it also deleted the (then empty) subdirectory too. That was kind of unexpected.

Thanks for the tests. I'll need to an option in the next update to allow permenant deleting of Read-only files - it'll have to tweak the attributes first.