Larry Posted June 22, 2008 Share Posted June 22, 2008 I was just wondering about these two. Currently, I still have 2.7, but is it still safe using it? Are the detection and definitions less than v3? Or am I still OK with v2.7? Link to comment Share on other sites More sharing options...
lal krishna Posted June 23, 2008 Share Posted June 23, 2008 I was just wondering about these two. Currently, I still have 2.7, but is it still safe using it? Are the detection and definitions less than v3? Or am I still OK with v2.7?I still use 2.7 and I like it better than version 3. Link to comment Share on other sites More sharing options...
KotaXor Posted June 23, 2008 Share Posted June 23, 2008 Me too, I'm using 2.7.39 and it is working fine....by the way, the definitions version numbers is the same for both v3 and v2.7 Link to comment Share on other sites More sharing options...
FundamenTos Posted June 23, 2008 Share Posted June 23, 2008 I'm using 2.70.39 also. Tried using the newest version with the MarsuFix, but NOD kept deleting the fix. Since I'm not that versed at the new interface, I couldn't get around to exclude it (if it needs to be done). So I went back to good ol' 2.7. Link to comment Share on other sites More sharing options...
Escobarretje Posted June 23, 2008 Share Posted June 23, 2008 ESET v3 is better then v2. The detection rate is improved, and if you have a virus v3 can mostly clean it well v2 can't do that. So I really advice you to upgrade! Marsu fix is working, and nodlogin too. All common bugs are fixed now so here it's working great with nodlogin. Link to comment Share on other sites More sharing options...
Noddy Posted June 28, 2008 Share Posted June 28, 2008 NOD32 2.70.39 here, too - does not aspire to behave like a firewall, an anti-spyware, an anti SPAM utility and an HIPS rolled into one. Consequently hogs much lower CPU cycles than V3 (any build.) Not to mention the level of compatibility with other utilities. Link to comment Share on other sites More sharing options...
Larry Posted June 29, 2008 Author Share Posted June 29, 2008 alright, well thanks for clearing this up guys :frusty: Link to comment Share on other sites More sharing options...
myidisbb Posted June 29, 2008 Share Posted June 29, 2008 ESET v3 is better then v2. The detection rate is improved, and if you have a virus v3 can mostly clean it well v2 can't do that. So I really advice you to upgrade! Marsu fix is working, and nodlogin too. All common bugs are fixed now so here it's working great with nodlogin.but do you have control like 2.7 allowed you?is the firewall version comparable to the others? Link to comment Share on other sites More sharing options...
lal krishna Posted July 12, 2008 Share Posted July 12, 2008 NOD32 2.70.39 here, too - does not aspire to behave like a firewall, an anti-spyware, an anti SPAM utility and an HIPS rolled into one. Consequently hogs much lower CPU cycles than V3 (any build.) Not to mention the level of compatibility with other utilities.Well said.And all the cracked appz in your PC won't connect to the www without your knowledge,if you stay with v.2.(If you didn't know already,NOD32 V.3 acts as a proxy server,and a cracked appz can phone home without your knowledge thru this. Link to comment Share on other sites More sharing options...
Noddy Posted July 13, 2008 Share Posted July 13, 2008 Another point is that my NOD32 2.70.39 is permanently fixed ever since installation (I use the 'B-effect' fix which has been working consistently.) I don't see most of the V3 builds in a position to be able to boast of this - the V3 fix that works on a particular build may cease to work on newer releases and even when it works, it doesn't work for each & everyone. Consequently, V3 Users are forced to keep rotating their loyalties in trying out different fixes to find out the one that works for them.Moreover, most of the V3 fixes are false-positively-targeted by ESET as 'Hacks' but surprising not the 'B-effect' fix for my 2.70.39 (. . . . . . not yet.) :rolleyes: Link to comment Share on other sites More sharing options...
KotaXor Posted July 18, 2008 Share Posted July 18, 2008 Another point is that my NOD32 2.70.39 is permanently fixed ever since installation (I use the 'B-effect' fix which has been working consistently.) I don't see most of the V3 builds in a position to be able to boast of this - the V3 fix that works on a particular build may cease to work on newer releases and even when it works, it doesn't work for each & everyone. Consequently, V3 Users are forced to keep rotating their loyalties in trying out different fixes to find out the one that works for them.Moreover, most of the V3 fixes are false-positively-targeted by ESET as 'Hacks' but surprising not the 'B-effect' fix for my 2.70.39 (. . . . . . not yet.) :unsure: I am using nsane fix....working very well... :P Agree with you! :wacko: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.