update.ver reverting to 1.939 from 1.940??

I just noticed that update.ver reverted on the engine from 1.940 to 1.939 - any idea what gives?

tia

Greg Hewitt-Long

 

nod it's back to 1.940 - what's going on Eset

last night it was:


[ENGINE2]
version=1.940 (20041205)
build=5027
type=engine
level=2
base=5011
date=05.12.2004
file=nod5A9B.nup
size=77015
category=engine
buildregname=EngineBuild


then it reverted to:


[ENGINE2]
version=1.939 (20041203)
build=5025
type=engine
level=2
base=5011
date=03.12.2004
file=nod0BB2.nup
size=76897
category=engine
buildregname=EngineBuild

now back to:

[ENGINE2]
version=1.940 (20041205)
build=5027
type=engine
level=2
base=5011
date=05.12.2004
file=nod5A9B.nup
size=77015
category=engine
buildregname=EngineBuild

grrr...

 

it's done it again - it's back to 1.939.

Are all the update servers not correct? I think my mirror is set to use any update server - so I think that 1 of the servers is out of step - and every few updates, it grabs a 1.939 version and then the next time it grabs a 1.940.

Any input?

 

I'm on 1.939 and just tried to manual update and it said my "nod32 is up to date. no update necessary". The nod32 site shows 1.940 as the latest ....strange......maybe eset servers are infected with viruses

 

i had no problem...nod32 has been updated to 1940 this morning...in spain

 

Ditto here, 1.940 when i booted up earlier today.



snowbound

 

I'm also seeing 1.940 since 11:11am PSDT yesterday.

 

NOD32 on our desktops are updated to 1.940 - I'm talking about the update.ver file we are getting for our "mirror" - it was reverting to 1.939 and then driving forward again, then reverting.

I've since changed my update server from "select automatically" to "u6.eset.com" - ie, I'm hard setting it to the USA based update server, rather than let it pick a different one each time. Since that time, I have not had the update.ver revert - even when it did revert, it never affected the NOD32 installations on the windows xp machines we had updating from the mirror.

regards

Greg Hewitt-Long

 

Even stranger, I installed NOD32 on someone's computer yesterday, and it said that it's version 2.12.4..

 

Was this before or after you went to the pub

LMAO

 

I'm currently up to 1.941 N. America pacific mountain time )

Neil

 

Same here Neil, that came through a while back down here Don't forget we're in your future

Cheers

 

Idem...i guess im in the middle...lol..

 

it must have been due to different update servers being at different levels for a while - since I hard set my update server to a single server, rather than "automatic", the problem has been resolved.

The problem wasn't so much for our desktop users - as nod32 will ignore a revision if it has gone backwards on the update server it is using, but the version number on our web site (see signature) which pulls it's version number from the update.ver file found on our updates mirror - this gives our web site an automatic update rather than us having to notice a change an put the file in place or update a config file.

Any chance of Eset putting the latest fix information into a similar file so I can code an automatic update of our virus definitions database in a similar way?

ie, a pipe separated, or csv update file for the latest update - perhaps in the format:

ID
update version
update type
what_added
date stamp
notes

or similar??

cheers

Greg Hewitt-Long

 

Quickly now, send me the lotto numbers, I'll buy a ticket and send it to you. We'll split the winnings! Failing that, just give me a heads up when I'm going to bump my noggin'

Neil

 

LOL, ooops watch out for that cliff, oh well that pigeon mail must have arrived to late even for those in my past