1883 Missed

Discussion in 'NOD32 version 2 Forum' started by guilijan, Nov 27, 2006.

Thread Status:
Not open for further replies.
  1. guilijan

    guilijan Registered Member

    Joined:
    Jun 25, 2006
    Posts:
    206
    What happen again with Nod updates?
    It updates from 1882 to 1884 but no 1883.
    The scheluder updates are setting to every hour.

    And what is this?
    Time Module Event User
    25/11/2006 23:22:56 Kernel Statistical information has been sent to ESET, spol. s r.o.
    25/11/2006 22:43:03 Kernel Statistical information has been sent to ESET, spol. s r.o.
    25/11/2006 22:43:02 Kernel Statistical information has been sent to ESET, spol. s r.o.
    25/11/2006 22:43:01 Kernel Statistical information has been sent to ESET, spol. s r.o.
    25/11/2006 22:42:59 Kernel Statistical information has been sent to ESET, spol. s r.o.
    25/11/2006 22:42:58 Kernel Statistical information has been sent to ESET, spol. s r.o.
     
  2. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    If you have 1884, you also have the content from the 1883 update.
    And for statistics details, take a look in the help file.
     
  3. guilijan

    guilijan Registered Member

    Joined:
    Jun 25, 2006
    Posts:
    206
    Brian N thanks for your answer.
    Ok with the update but if you look in
    http://www.eset.eu/virus-info/aktualizacie
    You can see 2hours and 10 minuts between the two updates, and I missed 1883 but the shceduled updates are setting to do it every hour.

    And the second question, take a look to the time.

    Time Module Event User
    25/11/2006 23:22:56
    25/11/2006 22:43:03
    25/11/2006 22:43:02
    25/11/2006 22:43:01
    25/11/2006 22:42:59
    25/11/2006 22:42:58
     
  4. Stan999

    Stan999 Registered Member

    Joined:
    Sep 27, 2002
    Posts:
    566
    Location:
    Fort Worth, TX USA
    It would seem to me that the time on that site doesn't mean that the update servers have been updated at that exact same time.

    Here is mine set to check every hour.
    US CST:

    Time Module Event User
    11/27/2006 9:06:27 AM Kernel The virus signature database has been successfully updated to version 1885 (20061127).
    11/27/2006 3:06:22 AM Kernel The virus signature database has been successfully updated to version 1884 (20061127).
    11/27/2006 0:06:21 AM Kernel The virus signature database has been successfully updated to version 1883 (20061127).
     
    Last edited: Nov 27, 2006
  5. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    The time you see on eset.eu is when the site has been updated, not when the actual signature update has been issued.
     
  6. guilijan

    guilijan Registered Member

    Joined:
    Jun 25, 2006
    Posts:
    206
    Ok and what about the second part of the question?
    What about this

    Time Module Event User
    25/11/2006 23:22:56
    25/11/2006 22:43:03
    25/11/2006 22:43:02
    25/11/2006 22:43:01
    25/11/2006 22:42:59
    25/11/2006 22:42:58
     
  7. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,148
    Location:
    Denmark
    No idea why it sends statistics that fast. It should only send during updates & startup/reboot etc.
     
  8. Elwood

    Elwood Registered Member

    Joined:
    Sep 12, 2005
    Posts:
    205
    Location:
    Mis'sippi
    Probably depends on how Threatsense is configured.
     

    Attached Files:

  9. guilijan

    guilijan Registered Member

    Joined:
    Jun 25, 2006
    Posts:
    206
    May be. I have change it now setting to send whit update.
    what skin are you using? Or it's corporate version?
     
  10. Elwood

    Elwood Registered Member

    Joined:
    Sep 12, 2005
    Posts:
    205
    Location:
    Mis'sippi
    It's just Windows ME.

    I have a new XPHE SP2 pc that I plan to get going Friday when I get a monitor. Couldn't afford to get both the pc and monitor at the same time.
     
Thread Status:
Not open for further replies.