Mike Kennedy

I'll try out your suggestions later... Thank you. You reminded me of one matter - though it's probably not significant... In a BAT file, one way to check if a FOLDER EXISTS is to execute "IF EXIST X:\PATH\TO\FOLDER\NUL"... That test has been broken in most/all versions of Windows, going back to Win95, and maybe 3.1/3.11. If CC happens to be using something like that.... - Mike

Thanks, Willy2, for updating the thread. Just in case... I've tried the new build of CC, but the issue remains in it. In some tests a few weeks ago, this computer also (wrongly) deleted the stated folder, but in more recent tests it never does. I do not know why this behaviour has changed. I tried many many combinations of the main CC options, on both PCs, and could not identify any impact on this bug. The 2 PCs are very similar (XP-SP3, exact same folder, etc), so the problem does not seem to be related to the parsing of PATHs and folder-names. - Mike.

Small update: I ran a few more simple tests... - In all these cases where the stated folder (ie, stated in the INCLUDE option) was NOT EMPTY, then the folder itself was NOT deleted (correct action). - In all cases where the stated folder WAS EMPTY, then the folder itself was deleted (incorrectly). Perhaps that's the full explanation of the bug! If so, my apologies for not spotting it earlier. - Mike.

Perhaps, but (I assume) it's very unlikely... AFAIK, Recuva was not installed when I was running the tests. I use mostly the default settings and default install, with, perhaps, 2/3 other options set, - and, obviously, our troublesome "include" bits. I'll experiment a little with some of these, though I could end up with thousands of combos to test! No probs... Thank YOU very much for participating in the thread. Hopefully, others will be alerted, and, hopefully, someone browsing the source will have an "aaaah!!" moment, and fix it! - Mike

Willy, Apologies for the delay... Good. I just suggested that as a possible explanation. I was wrong! Agreed! I since tried CC on another PC. Exactly as per the conditions in my first post in this thread. And it DID delete the stated folder (when it should not have done so). I tried re-loading CC, manually re-creating the folder, etc, and, in the few tests I ran, it DID delete the folder EVERY time. I did NOT yet create/check the INI file - maybe CREATING the INI file will have an effect! Very strange! - Mike

Willy, Yes. And the subsequent "Edit" option (of the same line, and the INI file) confirmed the settings. Yep - I agree fully that these INCLUDE/EXCLUDE screens are confusing - as per your other thread here. Every time I use them, I have to "experiment" with the settings, to achieve the result I want - especially with the "Drive/Folder" bits... In my INI file, the "RECURSE" option was active. To repeat: the issue is that the REMOVESELF option seems to be active in the code, even when the RECURSE option is selected. Update: I ran some more tests, and, sometimes, the "main" folder is NOT deleted - which is the correct behaviour. I don't know what conditions hold it (correctly), and what conditions delete it. Maybe, if these settings are adjusted, the new values are not correctly activated internally until the code is reloaded? - Mike

I agree with both sentiments - however, I quoted the "Download" folder merely to ILLUSTRATE the issue. That differs from my experience - as per the example I quoted. Correct. Apologies for the repetition: I chose the 2nd of the 3 "options" at point 3 - as confirmed by selecting the "Edit" function - yet CC DID delete the folder itself. - Mike.

Hi, Using latest build (v2.32.1165), under XP-SP3. Under Options, Include, I specified: - a Folder (actually C:\Windows\SoftwareDistribution\Download\) - "All Files" - "Include Files and Subfolders" CC correctly deletes all the Files and sub-folders, but it also deletes the "Download" folder. I would have expected that action if I had specified "Include files, subfolders and the folder itself". Probably a small matter in most situations, but, sometimes, the absence of a folder could be problematic. - Mike