just curios about update version number

Nod32 on my computer updated at 1:11:25 a.m. today (July 13). According to the event long and elsewhere the current version is 1.1167 (2005713). On the Eset page and also on Webyourbusiness update page the version number is 1.1167 (2005712). Why the discrepancy in the date?

 

I got our update information from nod32.sk - they have it down as 20050712:

http://www.nod32.sk/support/info.htm#CurVersion

It's almost certainly down to when it was updated on the various sites. I try to keep my numbering system in line with nod32.sk, which I would imagine is the source of the update - ie, updates get released out of slovakia, and regardless of MY timezone, the timezone and timestamp of the update as issued is what I record on our web site. This can often be AHEAD - ie, on the 13th when it's still the 12th here, but isn't very often lagging behind...

hth

Greg

 

Greg, it is not just your site that has the discrepancy. The Eset site:

http://www.nod32.com/support/info.htm#CurVersion

has the same discrepancy. Version 1.1167 but dated July 12th?

 

Couldn't it be that your NOD32 updated to v. 1.1167 on July 13th though the update was actually issued on July 12th? Note that updates are issued by Eset's engineers in Slovakia so there's a difference in time.

 

In my case, yes. I updated about 12:30AM on July 13th (My time zone of course).

 

in theory - yes - but it's more likely that a date/time difference will be the other way - unless the computer wasn't connected to the internet. The geography/timezone difference is normally that a Slovakian release is AHEAD of the date which the USA is currently on - ie, it can be the 13th in Europe, and the 12th in the USA, but it would be impossible for the date to tbe 13th in the USA and still only be the 12th in Europe/Slovakia.

If jayt's computer was turned off, or not accessing the net, then it's possible to update DAYS after the release.

http://www.nod32.sk/support/info.htm#CurVersion - 1.1167 - 20050712
http://www.nod32.it/support/info.htm#CurVersion - 1.1167 - 20050712
http://www.nod32.com/support/info.htm#CurVersion - 1.1167 - 20050712
http://www.nod32.ch/support/info.stm#CurVersion - 1.1167 - 20050712
http://www.nod32-es.com/support/update.htm#CurVersion - 1.1167 - 20050712
http://www.nod32.com.br/support/info.htm#CurVersion - 1.1167 - 20050712

now every site I see has the correct date of issue of the update - I think there must have been a connectivity issue - but this machine updated at 23:26 hours - mountain time (which would have been past midnight on the East coast and in Europ) - but the update shows as 1.1167 (20050713).

To me it looks likely that the date in update log comes from the update server - and being that they span at least 8, possibly 9 hours of timezones, that could explain why a large difference can show. What doesn't make sense, is that this machine updates from the office mirror - the office updates every hour, so this machine should never be more than 3 hours behind the issue of the Eset update - right?

If the update goes to the update servers at 11:59 in Slovakia, and has the date of July 12th, and my machine should update in 3 hours at most - My machine is going to be still at the 12th July, but the update server in Europe will almost certainly be moved through the midnight period and have it's date set at the 13th.

It's FAIRLY clear to me how a date CAN get messed up - but I can see how it could be a little off-sync.

hth

Greg

 

You're in a timezone AHEAD of slovakia though Firecat - JayT is in a timezone BEHIND Slovakia - I think trying to understand one update at a time will simplify the whole process... don't you agree?

 

I think that I'm stuck in a time warp or something. When I go to the Eset Web site it says the current version is 1.1152 20050623. My version is 1.1167

 

Same here Firecat.

 

Nope, that doesn't explain it. I have dsl and it is constantly on.

Note: