uhm so you trying disrespect / nullify what i said ? ...
please don't use arguments about malware detection here this post was about viruses and trojans not rest of malware (like spyware) ...
sorry but i said and i repeat this is about Avast! repeatly failing to prevent infection 'in time'... on correctly (High) set configurations on up2date VPS and program versions ... and that story came from multiple customers NOT just some rare ones ...
re:Tech = nowhere in my post is said that fail was when running multiple residents, Avast! was the single used. What you mean with 'I won't trust in non-technical complains about this kind of user' ? who You got in mind me or my customers? i doubt You know anything about me or them anyway so You not in position to even try to judge ...
But, like Alan, in this issues we need to know: file name, path, virus name, date of submition, etc.
filename useless, path useless, only what matter is hash of infected binary, date of submission and name ... but why i should repeat myself ... search some of my months old posts in virus section , i named some of them there ... (but to say at least one here from new ones 8.12.2005, Trojan-Clicker.Win32.Small.is )
what you want as proofs ? magic ? or You think network admins care about product which is failing writing up each missed piece ? no, they simple move to products which not fail them ... yes it's hard but true ...
it's problematic get samples of viruses / trojans which avast! not found for events which happened days or weeks ago ... most of them don't keep these ... and if samples are kept , they were always sent to Alwil ...
detection speed examples? ... trojans multiple times submitted in last year were added with 4+ months delays ... some were never added by Avast! (but for example Kasperky added them within days) ... from trojans submitted 2 weeks ago only one was added yesterday ... etc.
or You suggest to publish on some website what viruses, trojans, spyware, malware whatever is undetected by Avast! ? (some sort community driven site?) that's not bad idea ... why such site don't exist yet ?
--
related to multiple residents ...
until You prove me that resident solution Avast!+AVG is failing i will take your `comments` as just throwing 'genius' words into wind ...
tried it yet? we got 3 test machines running 24/7 with this config testing false alarms, various types of infections etc. against machine with just single of of them ... if we find moment where it fails ... then you right ... so far nothing such happened ...
also if you experiment often with multiple AV you find various combinations working w/o problem (if you don't fear to loose some performance) ... it's all about skills of these who config it ...
plus don't mismatch server side multi AV solution with clientside multi AV solution ... two totally different things ...