Update problem

Discussion in 'NOD32 version 2 Forum' started by Karl_Menshy, Nov 7, 2003.

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

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    Hi all,

    am trying to update an older NOD install from a local update directory with the fresh downloaded files (mirrored). However I get an error message, that the update files are damaged. Is there an issue with the updates right now? Have cleaned the updfiles directory and re-downloaded all files several times now but the downloads are identical, so it is not an issue of a damaged file transfer. Server is www.nod32.com.

    The strange thing is that hitting the "update now" button once more in fact DOES the update without complaints and NOD is running fine with latest version engine/defs.

    Any help/comments?

    Thanks,

    Karl
     
  2. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    After investigating this issue some more here is my conclusion:

    What I was trying to do was to update a partition with no internet access from a mirror on a CD-R. The issue does not happen if one copies the update files on the HD and removes the read-only attribute. That explains why it works from CD by hitting the update button twice: files are copied to updfiles directory and set read/write, then used for update on the second update hit.

    Can anybody from the NOD team confirm that NOD needs rw access to the update files?

    Thanks

    Karl
     
  3. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    Ok, let me try to add some more info and describe the problem maybe in a more understandable way:

    Updating NOD from the internet works ok. However, burning mirrored update files to a CD and trying to update from there leads to an error message, that the update files are damaged.
    Hitting the update button once more finally does the update, although of course I have no way to check whether it is done correctly.
    The workaround from msg 2 does NOT work :(.

    Could anybody from the NOD team please confirm that the update files that download by using the mirror function from nod32.com are ok/matching the info in the update .ver files?

    Just to let you reproduce the problem, here's in steps what I did: downloaded the latest v2 standard, installed, selected local mirror on CD-R, latest version downloaded by the admin module on the other partition.

    Any help is appreciated.

    Thanks,

    Karl
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Karl,

    I put update files from my mirror (only with virus signature db update) to CD and updated NOD32 fine. Did you update program components as well?
     
  5. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    Thanks for the reply.

    I tried to update with or without component update. Same result. Works only on the second try. Have verified with MD5 checksums that the updated sig files are the same as those updated from the internet on the other partition, so it actually seems to work on the second run, but why not on the first and why only from an offline mirror... o_O

    Any ideas?

    Btw, never had such a problem before...
     
  6. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    A few screenshots to illustrate the problem and mabe give some hints and clues as to where the reason is...

    First the usual update msg.
     

    Attached Files:

  7. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    The error msg.
     

    Attached Files:

  8. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    The message after hittin the update button once again
     

    Attached Files:

  9. Karl_Menshy

    Karl_Menshy Registered Member

    Joined:
    Apr 18, 2003
    Posts:
    135
    And finally it is done
     

    Attached Files:

Thread Status:
Not open for further replies.