incurable Posted December 27, 2007 Share Posted December 27, 2007 Hello, I didn't find information about v2.2 if it's better than v2.1I'm using NOD32 v2.70.39 with Nsane Autofix v2.1 (it works perfect!)-It's good for me to have always the latest autofix (nsane autofix v2.2) ?..or v2.2 works only for new NOD32 v3.0 ? Link to comment Share on other sites More sharing options...
LoKz Posted December 27, 2007 Share Posted December 27, 2007 Hello,I didn't find information about v2.2 if it's better than v2.1I'm using NOD32 v2.70.39 with Nsane Autofix v2.1 (it works perfect!)-It's good for me to have always the latest autofix (nsane autofix v2.2) ?..or v2.2 works only for new NOD32 v3.0 ?.This post has been edited by incurable: Today, 05:23 PMYou have to wait for a new update fix by nsane.. thank you also i know somebody is gonna help you but try using the search button too :) Link to comment Share on other sites More sharing options...
zaid786 Posted December 27, 2007 Share Posted December 27, 2007 The latest fix version for nod32 2.7 is 2.3.2 by b effect. It excludes nod32fix.reg from being detected as earlier versions of nsane fix is detected. Link to comment Share on other sites More sharing options...
martina Posted December 27, 2007 Share Posted December 27, 2007 nsane's fix v2.1 for NOD32 v2.x is undetected and still works.nsane's fix v2.2 for NOD32 v2.x is detected but works just fine if you put nod32fix.reg into your ignore list (via AMON - setup - exlusions).v2.2 of the fix was mainly built due to a data loss IIRC. it uses a newer installer and might fix one or two non-critical things.so if you're happy with NOD32 v2.70.39 and nsane's fix v2.1 there really is no compelling reason to upgrade just now IMO. Link to comment Share on other sites More sharing options...
HATE9X Posted December 27, 2007 Share Posted December 27, 2007 I didn't have any probs with 2.2 fix.. Did it start detecting it just lately? Link to comment Share on other sites More sharing options...
martina Posted December 27, 2007 Share Posted December 27, 2007 I didn't have any probs with 2.2 fix.. Did it start detecting it just lately?no, it's been a while, others have been reporting it too. Link to comment Share on other sites More sharing options...
Atasas Posted December 27, 2007 Share Posted December 27, 2007 Same applies to both- must be excluded from scaning in AMON ; Exclutions... Link to comment Share on other sites More sharing options...
accat131 Posted December 28, 2007 Share Posted December 28, 2007 Sounds like a noob question but how can you tell if you have been detected...I'm running NOD32 v2.70.39 not sure which version of the fix I have 2.2 but I may be running 2.1..It seems like it updates still with no problems. Unlike me getting older by the day. Link to comment Share on other sites More sharing options...
Atasas Posted December 28, 2007 Share Posted December 28, 2007 Sounds like a noob question but how can you tell if you have been detected...I'm running NOD32 v2.70.39 not sure which version of the fix I have 2.2 but I may be running 2.1..It seems like it updates still with no problems. Unlike me getting older by the day.If it updates, what's wrong? :wacko: For safety( potential of detection when running updated scan) it could want to delete "Malitious" Fix, but other than that works a treat? Link to comment Share on other sites More sharing options...
incurable Posted December 28, 2007 Author Share Posted December 28, 2007 I will keep NOD32 v2.70.39 & FiX v2.1 :P When v2.2 is needed I'm gonna install it!(it detects v2.2 as a virus btw)-..also I saw NOD32 v3.0 & I didn't like it :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.