logging verbosity not applying?

[Pixelize]

I seem to be getting the same log information no matter what verbosity level selected. After searching the Forum I've made sure that ThreatSense Engine parameter setup -> 'Log all objects' is unchecked.

I'm attaching a .txt file with sample few records for 'Warning' and 'Error' verbosity levels.

Shouldn't records like '...is OK (internal scanning not performed)' have disappeared in the verbosity level 'Error'?

Thanks in advance for your comments.
P.S. I'm evaluating trial version 3.0.669.0 downloaded about a week ago running Win2k pro.

Pixelize

[Marcos]

This has nothing to do with logging verbosity that is applied for event log records.

In order for the clean files not to appear, go to Computer scan -> Scan setup, select the desired scan profile, go to the ThreatSense parameters setup, select Other and untick the "Log all objects" checkbox.

[Pixelize]

OK, yes; it is the log size that I am concerned about as NOD32 has crashed once while browsing a huge scan log; that is why I changed the parameter you mention and, mistakenly, the verbosity level. I've just re-checked the config and re-ran a custom 'smart scan' profile with 'log all objects' unchecked and the logging info. '.. is OK (internal scanning not performed)' is still there ( .txt file attached). Maybe a system restart required??

Config in both Computer Scan -> Scan Setup and Tools -> Scheduler -> ... task setup show 'log all objects' unchecked.

The huge log problem with in-depth scans did seem solved.

Thanks.
Pixelize