Author Topic: VB100 Feb 2004 (WinNT)  (Read 11868 times)

0 Members and 1 Guest are viewing this topic.

Offline MWassef

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1315
VB100 Feb 2004 (WinNT)
« on: February 02, 2004, 05:11:27 PM »
February 2004 - Windows NT
avast (Alwil Avast! 4.1.319) failed this test , it is not mentioned if it is HE,PE or NE ??? ??? ::) ::)
MW

Offline MWassef

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1315
Re:VB100 Feb 2004 (WinNT)
« Reply #1 on: February 02, 2004, 06:35:00 PM »
related page: http://www.viry.cz/go.php
Could you please translate it into English ?  ::)
« Last Edit: February 02, 2004, 06:37:09 PM by minacross »
MW

Offline MWassef

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1315
Re:VB100 Feb 2004 (WinNT)
« Reply #2 on: February 03, 2004, 07:59:59 PM »
so?  ::)  ???
MW

whocares

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #3 on: February 03, 2004, 08:38:53 PM »

whocares

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #4 on: February 03, 2004, 08:39:55 PM »
Last XP-Test:

http://www.virusbtn.com/vb100/archives/tests.xml?200306
Kaspersky failed XP, avast Passed :)
This mean anything ?  ;)

Pavel Baudis

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #5 on: February 04, 2004, 10:38:55 AM »
February 2004 - Windows NT
avast (Alwil Avast! 4.1.319) failed this test , it is not mentioned if it is HE,PE or NE ??? ??? ::) ::)

Well, the history repeats again  >:( >:(. Although avast! did not miss a single ItW virus, the VB staff was not able to test the on access scanning at all. They said it is too complicated to test 'on execute' and FAIL to switch to 'on open'!!

I'm getting a little bit tired with their methodology.

Pavel

« Last Edit: February 04, 2004, 12:26:07 PM by Vlk »

Offline MWassef

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1315
Re:VB100 Feb 2004 (WinNT)
« Reply #6 on: February 04, 2004, 07:31:28 PM »
They said it is too complicated to test 'on execute' and FAIL to switch to 'on open'!!

are they joking or what ?  ::) ::)
that's the most ridiculous thing I ever heard of  :-\ :-\ :-\
MW

Pavel Baudis

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #7 on: February 04, 2004, 07:57:46 PM »
The exact quotation:

Changes to Alwil's on access scanner caused problems during the last review of the product and it proved troublesome again this time. With the configuration options available it is impossible to activate on-access scanning for many file types unless the files are executed. Clearly, this is infeasible when dealing with tens of thousands (or even merely dozens) of samples in test environment. Therefore, the on-access file capabilities of Avast! were untestable. Where on-demand scanning was concerned the results were good - unfortunately without on-access results the product does not qualify for a VB 100% award.

Really really sad reading - specially the part "it is impossible to activate on-access scanning"!!  >:( :(

Pavel

whocares

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #8 on: February 04, 2004, 08:30:26 PM »
We all feel with you, Pavel.. :) :)
that shows again how unhelpful & misleading AV-Tests can be


P.S.: I don't have avast here:

but I seem to remember that in the RS advanced tab,  there you can enable extra scanning on writing and Reading/Opening, BUT:

in only 1 of these two cases you can simply add the default extension list by pressing a button.
in the other case you have to manually add the extensions you want to scan (or copy them there from a board-posting, thx to you&Alwil ;D ;D ;) )

why not add the possibility to easily include the default-list in both cases ?

I know it's sort of an over-kill, but.....might this be an item for the wish-list ?


 ;)
« Last Edit: February 04, 2004, 08:31:44 PM by whocares »

Offline MWassef

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1315
Re:VB100 Feb 2004 (WinNT)
« Reply #9 on: February 04, 2004, 09:02:42 PM »
Pavel,
FRom where did you get these info? did they email you?  ::)
MW

Pavel Baudis

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #10 on: February 04, 2004, 09:42:43 PM »
Pavel,
FRom where did you get these info? did they email you?  ::)

No, it is the text from the magazine itself...

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11849
    • AVAST Software
Re:VB100 Feb 2004 (WinNT)
« Reply #11 on: February 04, 2004, 10:54:15 PM »
in only 1 of these two cases you can simply add the default extension list by pressing a button.
in the other case you have to manually add the extensions you want to scan)

Well, for the purposes of VB testing, simple putting an asterisk there should be enough...

Offline raman

  • Avast Evangelist
  • Advanced Poster
  • ***
  • Posts: 1062
Re:VB100 Feb 2004 (WinNT)
« Reply #12 on: February 04, 2004, 10:56:04 PM »
they only test with standard settings, do they? So just change the Standard and everything would be okay!:)
MfG Ralf

Pavel Baudis

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #13 on: February 04, 2004, 11:00:27 PM »
they only test with standard settings, do they? So just change the Standard and everything would be okay!:)

I think they state somethig different - they do not say they refuse to change it but that such change is impossible ?!?!


John-

  • Guest
Re:VB100 Feb 2004 (WinNT)
« Reply #14 on: February 06, 2004, 05:14:15 PM »
Windows NT => do they mean: Windows NT Workstation, Server, ...ect?

Or just: Windows NT, Windows 2000, Windows XP,...
Afterall the latest 2 are the modern versions of Windows NT.