2.000.9 ?

[controler]

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 (20040128)
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)

[Mele20]

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.

[spy1]

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.8).

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 (20040128)
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)

[controler]

Thanks

I was feeling left out ;D

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

[Marcos]

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.

[Hazeleyze]

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 (20040128)
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)

[sig]

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.)

[Marcos]

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.

[Blackspear]

{QUOTE-> quoting: spy1 link=board=39;threadid=20993;start=0#msg126848 date=1075733031]
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.8).

Just a thought. Pete <-QUOTE}

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 ;D

[spy1]

{QUOTE-> quoting: Blackspear link=board=39;threadid=20993;start=0#msg126974 date=1075761457]2.0008 caused problems in some XP Machines, reboots, error messages with AMON, unable to shut down (system reboots instead), etc etc. <-QUOTE}

Wow - I'm glad I missed the bullet on that one. To the best of my knowledge ( ;D ) 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

[controler]

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

[WilliamP]

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 (20040128)
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)

[controler]

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

[tosbsas]

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

Ruben

[controler]

Uninstalled and redownloaded today
All better now ;D

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 (20040128)
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)

[sig]

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

[tosbsas]

Which server did you use ??

Ruben

[Mele20]

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?

[the mul]

What sort of problems are u having.

the mul

[Mele20]

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?

[Q Section]

Hello Everyone

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

Best wishes

[FanJ]

W 98 SE here:

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

Thanks ESET !

[hayc59]

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

[izi]

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)

[NewNOD]

Mele20 wrote:
{QUOTE-> There are more locked files that NOD can't scan than I saw in version 6. <-QUOTE}

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.8):
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:
{QUOTE-> 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? <-QUOTE}

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.

[NewNOD]

{QUOTE-> 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). <-QUOTE}

The "/prompt" switch negates the ability of the AH scanner to use the Quarantine option. Even if Quarantine is saved with the Profile you use with "/config=", placing "/prompt" in the registry command line params overrides the Quarantine Profile option (you can see this after runnng the scanner as the previously checked "Quarantine" will now be unchecked).

So, the latest that I have found is that the optimal setting is simply:

/ah /config = <Name of Profile>

With this you will have to use the Clean button (next to the Scan button) after the initial AH scan finishes. This will initiate the Alert box assuming viruses were found, and Quarantine will show "checked" on the Alert (again assuming you have selected this as an option in the Profile's Actions tab for the object type found to be infected).

See ya.

[FanJ]

Hi,

As far as my eyes were permitting me, I saw a little difference in two postings in this thread with respect to:
"Archive support module version":

reply # 14 from Controler:
Archive support module version: 1.011 (20040128)

reply # 23 from izi:
Archive support module version: 1.008 (20031127)

=====
Here comes my info at W 98 SE (Dutch):

NOD32 Antivirus System information
Virus signature database version:***1.619 (20040209)
Dated:***maandag 9 februari 2004
Virus signature database build:***4208

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 95-98-ME - Base
Version:***2.000.9
NOD32 for Windows 95-98-ME - Standard component
Version:***2.000.9
NOD32 For Windows 95-98-ME - Internet support
Version:***2.000.8

Operating system information
Platform:***Windows 98
Version:***4.10.2222 A
Version of common control components:***5.81.4807
RAM:***511 MB
Processor:***x86 Family 6 Model 8 Stepping 1

=====

[Computer Answers]

Hi All
I downloaded the 2.000.9 update via the auto update yesterday and it has fixed the restart on shutdown problem but if I do a restart I get the error message that I send to MS and then I get told the problem is AMON and directed to the NOD site telling me to update to 2.000.9?
Is anyone else still having problems with 2.000.9. I have enclosed yet another system info
Cheers
Computer Answers

NOD32 Antivirus System information
Virus signature database version:***1.619 (20040209)
Dated:***Monday, 9 February 2004
Virus signature database build:***4208

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 - Administrative tools
Version:***2.000.8
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:***247 MB
Processor:***Intel(R) Celeron(R) CPU 1.70GHz (1699 MHz)

[Mele20]

Computer Answers,

Could your problem have anything to do with your archive support version and build version being out of date?

NOD32 Antivirus System information
Virus signature database version:***1.620 (20040210)
Dated:***Tuesday, February 10, 2004
Virus signature database build:***4210

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 (20040128)
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:***1023 MB
Processor:***Intel(R) Pentium(R) 4 CPU 3.00GHz (2992 MHz)

[sig]

Seems to be running ok on XP so far. At least I haven't noticed anything untoward so far. ;)

Mele: I can't recall if you mentioned whether you downloaded a new install from the site or updated via the NOD updater since you have the newer archive support module. I used auto update to get the new version and have the older ardhive support module (1.008) whereas Controller as I recall downloaded an new install from the ESET site and got the newer version (1.011).

Just wondering if there's a difference between the version available for download on the ESET site and what was released via the updater. Although why that should be, I can't figure. ???

[FanJ]

Just to inform you:

I have send an IM to Jan, Marcos and Anders about those differences showed in "Archive support module version".
At the moment I don't know the answer.
Of course, I could have made some mistake..... ::)
So, let's wait awhile to give the ESET guys time to answer ;)

Cheers, Jan.

[sig]

Thanks, FanJ, especially since you were the one who first posted about the differences in module release numbers/dates. :)

[Mele20]

Hmmm. I got mine from the website because Marcos told me to download it as he thought it would fix (it doesn't though) the irritating problem when using command line scanning (adv. heuristics or regular) and you get the box asking if you want to save changes made to your profile. I haven't made any changes. I never have gotten that box on my W98SE computer which has the 2.06 version still.

I have no idea why the website would have a later version of archive support.

Do you have a version of Administrative Tools? Like what Computer Answers has? I don't have ANY version of Administrative Tools!

[sig]

I'm guessing that Administrative tools appears only for the Administrative version (as in admin for network deployment) of NOD.

So it does appear that the full install version from the website has (or at least shows that it has) a newer version archive module than that downloaded via the updater. Well, FanJ sent out IM's so hopefully we'll get an explanation in due course.

[Computer Answers]

I may have overreacted. Since my last post I have restarted several times with no problems but it is still interesting as to why I have out of date archive support module. I will check on a clients computer today and compare.
Thanks for the comments
Bill
Computer Answers

[Blackspear]

I found both my affected XP systems required 2 reboots after the auto-update, before they finally returned to normal...

Cheers ;D

[FanJ]

Hi all,

Just only to inform you:

Both Jan and Marcos have informed me that ESET is looking at the "issue" about the "Archive support module version".

So please: let us all be patient and give the ESET guys the time to look at it !
Thanks for your understanding ! :)

Cheers, Jan.

[Vietnam Vet]

Hi FanJ,

Thanks for keeping us informed.

[snowbound]

Good show Jan ;D

Thanks for that. :)

Cookie? ;)




snowbound

[FanJ]

* Disclaimer 1 *

Every system is different.
Every setup is different.
Every user is different.

* Disclaimer 2 *

I did "some" testing.
Due to personal and physical circumstances I finally decided to do a fresh new installation.

* Thanks 1 *

Big thanks to two very dear friends here for re-checking "some" things.

* Thanks 2 *

Thanks to Marcos and Jan from ESET.

* Warning *

There is nothing special, particular, or whatever, in this posting.

[hr]
[hr]

System:
Windows 98 SE Dutch
IE and OE 5.5 SP2

Downloaded from the Eset-site fresh installation file:
The file nd98enst.exe has the following Checksum
MD5 - A563EC4EF71D32C0DC82EB2FFEA36D5E

After un-installation of existing NOD32 version-2 program, deleting directories and files, deleting software-firewall-rules, lots of rebooting and quick scandisk, and new installation.
Installation performed in Expert mode.

NOD32 Antivirus System information
Virus signature database version:***1.578 (20031212)
Dated:***vrijdag 12 december 2003
Virus signature database build:***4104

Information on other scanner support parts
Advanced heuristics module version:***1.004 (20031028)
Advanced heuristics module build:***1037
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 95-98-ME - Base
Version:***2.000.9
NOD32 for Windows 95-98-ME - Standard component
Version:***2.000.9
NOD32 For Windows 95-98-ME - Internet support
Version:***2.000.8

Operating system information
Platform:***Windows 98
Version:***4.10.2222 A
Version of common control components:***5.81.4807
RAM:***511 MB
Processor:***x86 Family 6 Model 8 Stepping 1


Servers for update:

www.nod32.com
www.eset.sk
www.esetsoftware.com

[hr]

After running update

NOD32 Antivirus System information
Virus signature database version:***1.626 (20040217)
Dated:***dinsdag 17 februari 2004
Virus signature database build:***4224

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 (20040128)
Archive support module build version:***1083

Information on installed components
NOD32 For Windows 95-98-ME - Base
Version:***2.000.9
NOD32 for Windows 95-98-ME - Standard component
Version:***2.000.9
NOD32 For Windows 95-98-ME - Internet support
Version:***2.000.8

Operating system information
Platform:***Windows 98
Version:***4.10.2222 A
Version of common control components:***5.81.4807
RAM:***511 MB
Processor:***x86 Family 6 Model 8 Stepping 1


Servers for update:

u1.eset.com
u2.eset.com
u3.eset.com
u4.eset.com

[hr]
[hr]

May I take the freedom to suggest to the ESET-mods, and mods and admins here, to start a sticky thread (maybe read-only) in which those NOD32 components are showed.

I think that would be a great service to the NOD32-users.

Show it for the versions of NOD32 for the different versions of Windows.
Different versions as, for example, shown here:
http://www.nod32.com/scriptless/download/download.htm

Maybe it is only needed for NOD32 version 2.

Of course there would be no need to change that thread every day; far from that.
Just change (update) it if there has been some PCU (Program Component Update) published, or something like that.

It's just a thought, but I guess it would be a great service to the NOD32 users....
They would be able to check their program-components for their version of Windows.

[danny9]

I just purchased NOD32 on 2/17 and received version 1.6 Sent email to tech support but no ans. yet. The download was for version 2. I wonder what gives with this?

[Phil_S]

1.627 is the current Virus Database version. Have a look at the module versions of your copy (Control Centre/NOD System Tools/Information/Information on Installed Components).

They should show versions 2.008 and 2.009.

[izi]

How to change Archive support module version from 1.008 (20031127) to 1.011 (20040128).

Run regedit, than find key:

HKEY_LOCAL_MACHINE\Software\Eset\Nod\CurrentVersion\InstalledComponents

find the entry:

ArchivesBuild

you can delete it, or decrease by 1.

Restart computer and run immediate update.

Izi