Competition for Bitdefender's HIVE and NOD32's AH?

Discussion in 'other anti-virus software' started by quexx88, May 5, 2005.

Thread Status:
Not open for further replies.
  1. quexx88

    quexx88 Registered Member

    Joined:
    Nov 26, 2004
    Posts:
    235
    Location:
    Radnor, Pennsylvania
  2. tazdevl

    tazdevl Registered Member

    Joined:
    May 17, 2004
    Posts:
    837
    Location:
    AZ, USA
  3. Firecat

    Firecat Registered Member

    Joined:
    Jan 2, 2005
    Posts:
    7,927
    Location:
    The land of no identity :D
    TruPrevent is very heavy and really not that good at zoo malware detection.....NOD's AH has proven to be quite good at detecting zoo malware...and also when it comes to ITW it catches less than NOD...
     
    Last edited: May 5, 2005
  4. bigc73542

    bigc73542 Retired Moderator

    Joined:
    Sep 21, 2003
    Posts:
    23,873
    Location:
    SW. Oklahoma
    I have used tru prevent and it is heavy on my comp, if it is heavy on this one it is going to be heave on any of them. And like it has been said TP is nowhere in the class of nods AH.
     
  5. Stefan Kurtzhals

    Stefan Kurtzhals AV Expert

    Joined:
    Sep 30, 2003
    Posts:
    701
    Guys, you cannot compare heuristic scanning with a behaviour blocker. TruPrevent detects the API calls of already active malware in memory, NOD32's AH or Bitdefender's HIVE detects malware proactively before it gets executed.

    Both systems have advantages and disadvantages, effectively you need both.
    <snip>

    That is probably the reason why Panda went for a behaviour blocker - they weren't able to produce a good unpacking engine like KAV, BD or NOD do have.

    <Post has been reviewed and relevant portions returned to thread... <puff-m-d>
     
    Last edited by a moderator: May 6, 2005
  6. iwod

    iwod Registered Member

    Joined:
    Jun 25, 2004
    Posts:
    708
    guys...i think we all based our opinion on version 1.0 May be 2.0 has improved since then?
     
Loading...
Thread Status:
Not open for further replies.