Ongoing XP NOD Install Problem

Discussion in 'NOD32 version 2 Forum' started by john smith, Feb 17, 2004.

Thread Status:
Not open for further replies.
  1. john smith

    john smith Registered Member

    Joined:
    Jun 14, 2003
    Posts:
    59
    I'm posting this because I haven't heard back from ESET support for several days; they asked me to post a "nsetup.log" to them, after running install in test mode, which I did.

    I am running XP Home (I have Admistrative status, there are no other users), and have had no trouble installing other programs, including NOD Version One, and AVG Trial edition. (I have removed both, and as many references to NOD as I can find in the registry, though I suspect I'm not getting them all). I've used NOD for several years, and would hate to give it up.

    Perhaps someone can see something in the attached file (nsetup_log.txt) which will give them a hint of the problem:


    Thanks for taking the time to read,

    John
     
  2. john smith

    john smith Registered Member

    Joined:
    Jun 14, 2003
    Posts:
    59
    Odd... the file attachment didn't seem to take. Here's the log:

    [2004-02-17 13:27:21.368] CmdLine: /test
    [2004-02-17 13:27:21.458] Registry: old settings read
    [2004-02-17 13:27:21.498] global.xml created
    [2004-02-17 13:27:21.498] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\global.xml
    [2004-02-17 13:27:21.498] XML_ACCESS: C:\Program Files\ESET\Install - C:\Program Files\ESET\Install\setup.xml
    [2004-02-17 13:27:21.498] Main settings added
    [2004-02-17 13:27:21.498] Engines nups
    [2004-02-17 13:27:21.498] InstallPath added
    [2004-02-17 13:27:21.498] LogPath added
    [2004-02-17 13:27:21.578] EngineFile extracted
    [2004-02-17 13:27:21.598] EngineFile extracted
    [2004-02-17 13:27:21.648] EngineFile extracted
    [2004-02-17 13:27:21.648] EngineFile extracted
    [2004-02-17 13:27:22.079] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpa\setupc.xml
    [2004-02-17 13:27:22.099] SetupAddComponentDescToGlobal
    [2004-02-17 13:27:22.099] Component added
    [2004-02-17 13:27:22.099] Componet libraries
    [2004-02-17 13:27:22.650] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpb\setupc.xml
    [2004-02-17 13:27:22.650] SetupAddComponentDescToGlobal
    [2004-02-17 13:27:22.650] Component added
    [2004-02-17 13:27:22.650] Componet libraries
    [2004-02-17 13:27:22.950] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpc\setupc.xml
    [2004-02-17 13:27:22.950] SetupAddComponentDescToGlobal
    [2004-02-17 13:27:22.950] Component added
    [2004-02-17 13:27:22.950] Componet libraries
    [2004-02-17 13:27:23.040] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\global.xml
    [2004-02-17 13:27:23.040] Cmd: 0 Exelib: NOD32 For Windows NT/2000/XP/2003 - Base
    [2004-02-17 13:27:23.040] - krnstp.dll
    [2004-02-17 13:27:23.040] - ps_upd.dll
    [2004-02-17 13:27:23.040] Cmd: 0 Exelib: NOD32 for Windows NT/2000/XP/2003 - Standard component
    [2004-02-17 13:27:23.051] - ps_amon.dll
    [2004-02-17 13:27:23.051] - ps_nod32.dll
    [2004-02-17 13:27:23.051] Cmd: 0 Exelib: NOD32 For Windows NT/2000/XP/2003 - Internet support
    [2004-02-17 13:27:23.051] - imon.dll
    [2004-02-17 13:27:23.051] - ps_nms.dll
    [2004-02-17 13:27:23.061] ExeLibs: Init
    [2004-02-17 13:27:23.061] Cmd: 2 Exelib: NOD32 For Windows NT/2000/XP/2003 - Base
    [2004-02-17 13:27:23.061] - krnstp.dll
    [2004-02-17 13:27:23.071] - ps_upd.dll
    [2004-02-17 13:27:23.071] Cmd: 2 Exelib: NOD32 for Windows NT/2000/XP/2003 - Standard component
    [2004-02-17 13:27:23.071] - ps_amon.dll
    [2004-02-17 13:27:23.071] - ps_nod32.dll
    [2004-02-17 13:27:23.081] Cmd: 2 Exelib: NOD32 For Windows NT/2000/XP/2003 - Internet support
    [2004-02-17 13:27:23.081] - imon.dll
    [2004-02-17 13:27:23.081] - ps_nms.dll
    [2004-02-17 13:27:23.091] ExeLibs: Load Current State
    [2004-02-17 13:27:23.091] Error: Couldn't open Administrator's XML : nod32.xml
    [2004-02-17 13:27:35.859] Registry: root written
    [2004-02-17 13:27:35.859] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\global.xml
    [2004-02-17 13:27:35.999] SetupCopyFiles
    [2004-02-17 13:27:35.999] Cmd: 3 Exelib: NOD32 For Windows NT/2000/XP/2003 - Base
    [2004-02-17 13:27:35.999] - krnstp.dll
    [2004-02-17 13:27:36.219] - ps_upd.dll
    [2004-02-17 13:27:36.290] Cmd: 3 Exelib: NOD32 for Windows NT/2000/XP/2003 - Standard component
    [2004-02-17 13:27:36.290] - ps_amon.dll
    [2004-02-17 13:27:36.290] AMONPLG Status: Install case begin
    [2004-02-17 13:27:36.670] AMONPLG Status: Install case end
    [2004-02-17 13:27:36.680] - ps_nod32.dll
    [2004-02-17 13:27:36.680] NOD32PLG Status: Install case begin
    [2004-02-17 13:27:36.690] NOD32PLG Error: GetDesktopFolder
    [2004-02-17 13:27:36.690] NOD32PLG Error: CreateLink
    [2004-02-17 13:27:38.743] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Owner\LOCALS~1\Temp\global.xml
    [2004-02-17 13:27:38.893] Deleting directory: C:\DOCUME~1\Owner\LOCALS~1\Temp\NSetup\
    [2004-02-17 13:27:38.903] Deleting directory: C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpa\
    [2004-02-17 13:27:38.903] Deleting directory: C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpb\
    [2004-02-17 13:27:38.903] Deleting directory: C:\DOCUME~1\Owner\LOCALS~1\Temp\nodtmpc\
    [2004-02-17 13:27:38.913] Exitcode: 121 NOD32 for Windows NT/2000/XP/2003 - Standard component
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hi,

    seems like there's a problem with creating the icon on the desktop. Haven't you noticed any problems with other programs not able to create a desktop icon? Are you able to create one?
     
  4. john smith

    john smith Registered Member

    Joined:
    Jun 14, 2003
    Posts:
    59
    Hi, Marcos,

    Good point. Mark from ESET e-mails me every several days with a question, and that was the last one. Haven't heard any more yet.

    In fact that is a problem. Right now I'm running NOD32 Version One, and it functions fine, but did *not* create a scanner icon on the desktop as it originally did.

    On the other hand, I also installed "Anaphod Explorer," a program for managing an iPod, and it created its desktop icon just fine.

    XP has always bewildered me with it's install paths. I'm sure it's an XP problem, but I don't know what to do about it. I'm not up for a reformatting just now, since the thing is functioning.

    John
     
  5. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    We had this with only one system about 6 months ago, we ended up uninstalling version 1, deleting the Eset folder from program files, then we used regcleaner and removed all remaining entries and reinstalled version 2 from a fresh download. This fixed the problem, only ever seen it on that machine, not before and not since.

    Hope this helps...

    Cheers :D
     
  6. john smith

    john smith Registered Member

    Joined:
    Jun 14, 2003
    Posts:
    59
    I had tried all of that except for the fresh download; tonight I tried it with that, but to no avail. I'm certain it's an XP problem, likely some registry error; I tried a System Restore to a reasonable time back (always a bit weird when much time has past and programs have been added and deleted), but still no go. I may carry this over into an XP group, but suspect I have a reformat in the future. I do my backups, but it takes days to put everything back. Sigh.

    Thanks anyway,

    John
     
  7. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Afraid so, a format will fix the problem...

    Cheers :D
     
  8. steve1955

    steve1955 Registered Member

    Joined:
    Feb 7, 2004
    Posts:
    1,384
    Location:
    Sunny(in my dreams)Manchester,England
    Have you tried a repair install of Xp instead,at the best it will save your progs etc at worst you'll still have to format(if you think it is a XP prob have you tried to contact Microsoft support,it may be an issue they know and have a solution for!)
     
  9. john smith

    john smith Registered Member

    Joined:
    Jun 14, 2003
    Posts:
    59
    Thanks. First I'll try one of the windowsxp newsgroups; next I'll try the repair install, and last of all, the reformat. XP is the best version of Windows I've ever used, but I'll never love Windows.

    John
     
Thread Status:
Not open for further replies.