32-Bit XP SP2
CFP only security program
Custom Firewall mode & Clean PC Defense+ mode
This issue started at least during the first version 3 final where it would sometimes not prompt the user prior to actually clearing the Firewall or Defense+ log. Very difficult to duplicate since it doesn’t always happen.
if this happens frequently maybe saving Documents and Settings\All Users\application data\comodo\Firewall Pro\cfplogdb.sdb in a separate folder before clearing could provide us with the log db file that was in place when this issue occurs.
Maybe it is some DB related issue. If this is the case the failing DB could make this issue reproducible at will.
I’ll test this too never paid attention to clear dialogs. (I guess I just considered them a nuisance :P)
Something like this. The outcome shoud be to save the log db until this issue can be reproduced. The latest log backup should be the one that triggered this issue. As for CFP Logviever default behaviour those confirm dialogs will not be displayed if the affected (D+, F+ or both) log is empty. Sometimes the log is filled but the logviewer windows is not yet updated thus it looks empty. In this case the confirmation alert will be displayed.
Anyway to backup succesfully the affected CFP log db no new entry should be logged before using the Logviever “Clear” menu option.
It look easier said than done. :-X
As for those WOS enties I guess those should be CFP SPI entries. If this is true they only list blocked connection to closed ports.
No clue here about the system entries. Anyway I gess that a new bugreport topic should be opened to let otherm members reproduce this.
No, actually. When they are empty (I know for a fact they are because I just cleared them and diabled logging in all rules and in the Settings screen), it actually always prompts me. BTW I usually click on the main branch for both the Firewall and Defense+, not the sub-branches like “Today”, “This Week”, etc…
But the attached is really the database log right before I encountered the issue again.
Ugh :-. I started one for v2.4 in the past and it never was fixed until v3. The only difference is at least v3 has one extra option in the Setting so that the log doesn’t get produced at all.