diman111 Posted August 18, 2010 Report Share Posted August 18, 2010 Winamp takes to start up long time about 15-20 seconds. Only swiching off ClamAV helps reduce that time to 1 second. Datailed discussion here Winamp Forum Link to comment Share on other sites More sharing options...
m0unds Posted August 18, 2010 Report Share Posted August 18, 2010 Winamp takes to start up long time about 15-20 seconds. Only swiching off ClamAV helps reduce that time to 1 second. Datailed discussion here Winamp Forum have you tried adding winamp to the list of exceptions? it might alleviate the issue for you Link to comment Share on other sites More sharing options...
diman111 Posted August 19, 2010 Author Report Share Posted August 19, 2010 I found that ClamAV checks some temporary files during winamp's startup in folder user\AppData\Local\Temp. I'm not sure that adding the whole user\AppData\Local\Temp to the list of exceptions is safe... Link to comment Share on other sites More sharing options...
alfred Posted August 19, 2010 Report Share Posted August 19, 2010 I found that ClamAV checks some temporary files during winamp's startup in folder user\AppData\Local\Temp. I'm not sure that adding the whole user\AppData\Local\Temp to the list of exceptions is safe... Hey Diman, You are correct, adding the exclusion for the whole dir would lead to some unsafe operating conditions. Do you know the file names or types it working with? You may be able to exclude those. al Link to comment Share on other sites More sharing options...
diman111 Posted August 19, 2010 Author Report Share Posted August 19, 2010 Hey Diman, You are correct, adding the exclusion for the whole dir would lead to some unsafe operating conditions. Do you know the file names or types it working with? You may be able to exclude those. al These files are dll and lng. It's not good to exclude dll i think. Anyway it's bad when cloud AV works so slowly:), seems to be a bug? Link to comment Share on other sites More sharing options...
alfred Posted August 19, 2010 Report Share Posted August 19, 2010 These files are dll and lng. It's not good to exclude dll i think. Anyway it's bad when cloud AV works so slowly:), seems to be a bug? Hard to say honestly, from reading the thread it sounds like Avast is exhibiting the same behavior no? If you know the precise dll files you can put them in exclusions. The lng files are not something we scan so that is likely not the issue. Do you have both Avast and IMP installed? al Link to comment Share on other sites More sharing options...
diman111 Posted August 19, 2010 Author Report Share Posted August 19, 2010 Hard to say honestly, from reading the thread it sounds like Avast is exhibiting the same behavior no? If you know the precise dll files you can put them in exclusions. The lng files are not something we scan so that is likely not the issue. Do you have both Avast and IMP installed? al No Avast, Norton, AVG don't affect winamp. But ClamAV and Kasperskiy do. Please read this http://forums.winamp.com/showthread.php?p=2688962&posted=1#post2688962. I have installed ClamAV and Avast. Swichin off ClamAV makes winamp startup much faster. Link to comment Share on other sites More sharing options...
alfred Posted August 19, 2010 Report Share Posted August 19, 2010 No Avast, Norton, AVG don't affect winamp. But ClamAV and Kasperskiy do. Please read this http://forums.winamp.com/showthread.php?p=2688962&posted=1#post2688962. I have installed ClamAV and Avast. Swichin off ClamAV makes winamp startup much faster. OK, do you know which files (dll's) it's dropping in the temp dir? Do they have a predictable name? al Link to comment Share on other sites More sharing options...
diman111 Posted August 20, 2010 Author Report Share Posted August 20, 2010 OK, do you know which files (dll's) it's dropping in the temp dir? Do they have a predictable name? al Now I cheked dll's file names and it seems I was wrong, in the temp I see only *.lng instaled by Winamp(I Check it by ClamAV's history). And you say that dlls aren't scaned by ClamAV. Link to comment Share on other sites More sharing options...
alfred Posted August 20, 2010 Report Share Posted August 20, 2010 Now I cheked dll's file names and it seems I was wrong, in the temp I see only *.lng instaled by Winamp(I Check it by ClamAV's history). And you say that dlls aren't scaned by ClamAV. Hmm. No, .dll files are scanned, it's .lng files that should not be being reviewed. Effectively unless it's a PE file our Free product does not do anything to it. Can you upload an lng file so I can look at it? al Link to comment Share on other sites More sharing options...
diman111 Posted August 20, 2010 Author Report Share Posted August 20, 2010 Hmm. No, .dll files are scanned, it's .lng files that should not be being reviewed. Effectively unless it's a PE file our Free product does not do anything to it. Can you upload an lng file so I can look at it? al I mistook, I was going to write .lng are not scaned. As I see there are 2 folders winamp puting temps to (and maby there are even more I don't know): C:\Users\diman\AppData\Local\Temp C:\Users\diman\AppData\Roaming\Winamp Attached winampa.lng renamed to winamp.txt because forum doesn't allow lng attachments. winampa.txt Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.