I use Eset Smart Security 3.0.621.0. During a full scan of my computer Eset makes a logfile of 61 thousand lines which is 15 MByte big. If I examine this logfile in UltraEdit, I see that most of those lines are related to the scan of 2 files. Those 2 files are big installaler files (130 MByte each) and password protected (at least according to the messages Eset writes in it's logfile). I estimate that about 55,000 messages of those 61,000 messages are related to these 2 files. Every message says something like "I can't scan a file in this file, because the file is probably password protected". Well, there are thousands of files in this big installer file and that's why there are thousands of messages in the logfile. Can't Eset Smart Security skip scanning a file the moment it detects that it can't open it? At least skip writing log messages about it? I think 1 message saying that the file seems to be password protected and therefore it is not being scanned any further should be enough. That would make the scanning of my system much faster I think.