2.000.9 ?

IS this engine done by autoupdate?

Mine is still 2.000.6. I wrote to support about this but never heard back


NOD32 Antivirus System information
Virus signature database version:   1.614 (20040129)
Dated:   Thursday, January 29, 2004
Virus signature database build:   4194

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Archive support module version:   1.011 (2004012
Archive support module build version:   1083

Information on installed components
NOD32 For Windows NT/2000/XP - Base
Version:   2.000.6
NOD32 For Windows NT/2000/XP - Internet support
Version:   2.000.6
NOD32 for Windows NT/2000/XP - Standard component
Version:   2.000.6

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   447 MB
Processor:   mobile AMD Athlon(tm) XP2500+ (1855 MHz)

 

It hasn't been released yet for auto update. I know...it has been promised several times already....but wouldn't you rather wait than have it released with problems? If you just gotta have it now...go get it from the NOD32 website. I'm waiting for auto update to get it.

 

con - I understand why you haven't gotten 2.000.9 (since it hasn't been released through auto-update yet) - my question would probably be "Why don't you have 2.000.8?

I think, to be on the safe side, you should un-install (correctly!) the copy of NOD32 v.2 you've got now and do a fresh d/l and re-install (that may be the only way you'll get up to 2.000..

Just a thought. Pete

NOD32 Antivirus System information
Virus signature database version:   1.614 (20040129)
Dated:   Thursday, January 29, 2004
Virus signature database build:   4194

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.011 (2004012
Archive support module build version:   1083

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.8
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.8

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   768 MB
Processor:   AMD Athlon(tm) Processor (1325 MHz)

 

Thanks

I was feeling left out

But about 2 weeks ago I did uninstall NOD and reinstalled it off the site and I guess I got 2.000.6 for some reason.
Is 8 any better?
Spy 1

Ya know the KAV 5.0 mods keep claiming KAV detects most comercial keyloggers with their new extended and redundent updates but the news is they don't . NOT A ONE.
It is nice to see trojan Hunter detecting them though.
Andreas ( A2 )also claims to detect alot of stuff but even after I send them in, he doesn't add them.
packed or unpacked. Just a little tib bit there


con

 

Well, the new version brings some new enhancements, such as Internet filter (blocks exploits, such as those made by Lovsan, Nachi, Red code, etc.), a possibility to modify the subject of infected email, automatic notification before license expiry plus some others.

 

If the new version isn't out yet, why does mine say 2.00.9? Unless I'm reading it wrong.

NOD32 Antivirus System information
Virus signature database version:   1.615 (20040202)
Dated:   Monday, February 02, 2004
Virus signature database build:   4196

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.011 (2004012
Archive support module build version:   1083

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.9

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   512 MB
Processor:   AMD Athlon(tm) XP 1800+ (1537 MHz)

 

Did you download NOD from the ESET site? The new version has been available in the download section for some time for new downloads.

But it hasn't been generally released to the auto update for all users. (Although some people who had issues with previous versions were instructed by ESET to add a specific additional server to the update setup to get the new .9 program components via the update module.)

 

That's right. The new version is currently available only as an installer on our website. We estimate it could be released within the following days as a standard component upgrade.

 

2.0008 caused problems in some XP Machines, reboots, error messages with AMON, unable to shut down (system reboots instead), etc etc.

So, as soon as this was seen, it was immeadiatly removed from the servers...

2.0006 was put back up for download.

2.0009 is the latest version available if you download from www.nod32.com As Marcos said, it will be available shortly as a component upgrade (automatically), within days.

Cheers

 

Wow - I'm glad I missed the bullet on that one. To the best of my knowledge ( ) 2.0.0.8 has been working flawlessly here - it certainly hasn't been causing any computer problems that I've noticed.

Oh, well - I'll look forward to seeing what 2.0.0.9 brings. Pete

 

The reason I asked is my version 2.000.6 has a shutdown problem.
it doesn't matter if i leave IMON on or not.
I get the error Hidden IMON not responding during shutdown.
I have to exit NOD before shutting down.

con

 

Got the new version last week. Everything is great. NOD32 Antivirus System information
Virus signature database version:   1.615 (20040202)
Dated:   Monday, February 02, 2004
Virus signature database build:   4196

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.011 (2004012
Archive support module build version:   1083

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.9

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   512 MB
Processor:   Intel(R) Pentium(R) 4 CPU 1.80GHz (1794 MHz)

 

Still don't see the autoupdate to 2.000.9
Mine still shows 2.000.6
Have autoupdate set to automatic. Am I suppose to select a differnt download site?

con

 

there was a temp site out there, but don't know if still funcional

Ruben

 

Uninstalled and redownloaded today
All better now

NOD32 Antivirus System information
Virus signature database version:   1.617 (20040206)
Dated:   Friday, February 06, 2004
Virus signature database build:   4202

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.011 (2004012
Archive support module build version:   1083

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.9

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   447 MB
Processor:   mobile AMD Athlon(tm) XP2500+ (1855 MHz)

 

I just received the program update via auto update so it's now been released to all users.

 

Which server did you use ??

Ruben

 

Can I go back to 2.6 and avoid the auto update? I don't like 2.9. It has a lot of problems on XP Pro SP1. I want to use 2.6. Can I do so?

 

What sort of problems are u having.

the mul

 

There are more locked files that NOD can't scan than I saw in version 6. Plus, upgrading did not fix the constant box I get, when I use the command line scanning (regular or adv. heuristics) or when I run NOD32 scanner, that claims I have made changes to one or another of my profiles. I have made no changes but I still get that irritating box which Marcos said would go away in version 9. So, if I still get that box and see more locked files, why not use the earlier version?

 

Hello Everyone

FYI - Win 98SE here and no problems with auto update 2.000.9.

Best wishes

 

W 98 SE here:

I just got the new one via update: no problem so far

Thanks ESET !

 

i also got the update today?? i think
can eset confim this. or can someone
post the build numbre's

 

NOD32 Antivirus System information
Virus signature database version:   1.618 (20040209)
Dated:   9. februar 2004
Virus signature database build:   4206

Information on other scanner support parts
Advanced heuristics module version:   1.005 (20031222)
Advanced heuristics module build:   1047
Internet filter version:   1.001 (20031104)
Internet filter build:   1012
Archive support module version:   1.008 (20031127)
Archive support module build version:   1078

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version:   2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version:   2.000.8
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version:   2.000.9

Operating system information
Platform:   Windows XP
Version:   5.1.2600 Service Pack 1
Version of common control components:   5.82.2800
RAM:   256 MB
Processor:   Intel(R) Celeron(R) CPU 1.70GHz (1700 MHz)

 

Mele20 wrote:

I have a VBScript that I wrote (main function is to post message boxes on desktop after scheduled scans complete), and it also allows me to save individual scan results along with the date of the scan. Because of this, I have many individual scan text files going back to the time I implemeted the VBScript. I checked and had one from when I still used version 2.000.6. I ran a text file compare of the 2.000.6 scan with a 2.000.8 scan and then a 2.000.9 scan. The only differences in the text files were the obvious: date of scan, number of files scanned, time to scan in seconds, etc. BUT, the files excluded from scanning due to "locks" (or password protection, etc.) were exactly the same.

By the way, I'm glad you brought this up because it prompted me to do this file compare; as it turns out, one of the differences in 2.000.9 compared to .6 and .8 is the "time of termination:" line at the end of the log:

Was (under 2.00.6 & 2.000.:
time of termination: xx:xx:xx total scanning time: xxxx sec (xx:xx:xx)

Is (under 2.000.9)
time of completion: xx:xx:xx total scanning time: xxxx sec (xx:xx:xx)

Since I extract this line with the VBScript using REGEX, I'll have to change the parameters to find "completion" as opposed to "termination".

Mele20 also wrote:

Mele20,

I know I've been following your travails with this issue (maybe too closely ), but I still don't have this issue after upgrading to 2.000.9. As I discussed in previous threads, the "culprits" creating the behavior (prompting to save Profiles after each context menu scan) are using the AH context scanner with the "/shext" switch in the registry or when using the standard context menu scanner (regardless of settings). Also, the general distinction between a Profile (a set of options that can be set and saved via the GUI in NOD32) and "command line" scanner of Paolo's AH context scanner (changes to its functionality can't [officially] be set via GUI and thus cannot be saved via GUI; settings are only impacted via manual registry key modifications**) is very important. A Profile (used by the standard context scanner) will prompt for a change even when it's just the Target folder or file that has changed because a Profile includes Targets as one of its parameters...if you scan a different folder/file than those that are already included in the Profile, NOD doesn't know whether you want to make this change by permanently adding the Target, so it prompts you to save. The AH scanner, on the other hand, does not use Profiles that can be saved via the GUI**, so it does not prompt for the save (except it seems in your case). The "/shext" switch which was added by Paolo to the default switches in the latest version of the AH scanner essentially tells the AH scanner to use a Profile just like the standard context scanner (including the annoying prompt). Removing the switch, barring any other strangeness, removes the Profile behavior from the AH scanner and thus the prompt.

Just ran an interesting test:
**/shext is not the only switch which makes the AH scanner use a Profile. The [undocumented] "/config=" switch allows you to set a specific Profile to be used (I noticed the switch being reported in the scheduled scan results so I thought I'd give it a try with the AH scanner). If you set the AH scanner with this switch (assuming you have a Profile named Manual Scan):

/config=Manual Scan

the AH scanner WILL use the GUI settings (from the GUI Actions tab, Setup tab, etc. for that Profile). Modifying some of the settings proves this to be the case as the expected results are obtained after making/saving changes in the Profile then re-running the AH scanner (for instance, unchecking or checking Quarantine on the Actions tab or checking or unckecking Archives on the Setup then saving the Profile).

Be sure the Profile selected is set to "use this profile for scanning objects from within the context menu". I won't go into details, but the options on the Actions tab didn't work correctly in all cases if this was not set.

And, best of all, the use of the Profile provides the benefits of:

- setting the AH scanner from the GUI instead of via registry settings (except of course initial setup to remove the "/shext" switch and and add "/config=;
- surprisingly, invoking the Manual Scan Profile from the registry switch DID NOT cause the "save prompt" to appear as it does when using the "/shext" switch;
- it allows you to use Quarantine with the AH scanner (which as far as I know does not have a registry switch to set it otherwise) by setting it in the GUI and saving the settings to the Profile.

Be sure to include the "/ah" switch or the Advanced Heuristics will not be utilized. Also, the "/prompt" switch is about the only other thing I see as being beneficial. Most other switches and their equivalent behaviors become settable at the GUI level (at least the ones that I had been using, both AH scanner defaults and ones I added).

**One oddity:

The AH scanner shows this in the scan results:

Command line: /config=Manual Scan C:\WINDOWS\Desktop\Misc DeskTop

Scanned disks, directories and files: Scan\; C:\WINDOWS\\Desktop\Misc DeskTop\
Directory path Scan\ is invalid.

Notice that NOD32 takes the last word of the Profile name (regardless of what you name the Profile) and adds it to the scanning Targets, in this case "Scan\". It has no impact, however, on the scanners continuing to scan the valid directory(ies) selected via right-click. This oddity may be enough to prevent some from using it (maybe even me in the long run), but I thought I'd post the info anyway.

Also, I know you have XP and I'm testing on Win98, so no telling what the differences might be. Wish I could test XP also, but I don't want to buy another NOD32 license to do so.

Oh, and so far, everything else in 2.000.9 seems to be functioning as usual in Win98 (meaning no new bugginess). Keeping my fingers crossed.

See ya.