NOD32MOD_WINNT ENGLISH STANDARD

[kblist72]

About 4 days ago, I realized my subscription was up and I did the CC thing online and had it renewed for another year as I love the NOD32 app.

Well, things have gone asunder. I am not sure what I've done, but I cannot seem to install this new version (v2st) or the beta. When I do, it gives me a basic error window with the red "X" icon, with:

(121) NOD32MOD_WINNT ENGLISH STANDARD

Not too helpful. I have placed several emails with the support line and haven't gotten any further.

I'm running XP Pro (Version 2002), SP2 w/ 1.3Ghz/384MB Ram.

The application does not install completely; registry values need to be cleaned to do another install. The Nod32.xml was missing and was supplied via support contact/email.

I don't know if I overlaid V1, or pre-V20; I beleive it was doing an update but my broadband provider was also glitchy that day and the connection was lost (hung on "updating" but no apparent activity); I uninstalled the NOD I had running and put this new one on..

Its the first time I've ever had issues with this program.. Was hoping maybe it is an XP/SP2 issue; but perhaps I clobbered the registry? I dunno.

I could use any input here.. Thanks.
-KB72 (kblist@cox.net)

[Blackspear]

Hi Kblist72, welcome to Wilders.

Can you please uninstall Nod32

Then reboot your PC

Remove the Eset Folder from C> Program Files.

Cleaning the registry of the last remaining Eset file.

Reinstall a FRESH copy of Nod32 from here (http://www.nod32.com/index_dw.htm) using your new UN and PW.

Hope this helps…

Let us know how you go…

Cheers ;D

[kblist72]

Thank you..

I have no program to uninstall in the Start Menu\Programs,
But I removed the Eset folder with its install/logs contents.

As for cleaning the registry, no contents via HKLM\Software
were available to delete.

Per URL, I downloaded a fresh copy.

I'll reboot and install and return back.

[kblist72]

After reboot, received email from Eset support, suggesting I give them a dump from a tool called belarc. I did this.. it was a nice tool (www.belarc.com) I had not heard of it before.

Any way, I ran the fresh install and got the same 121 error.

[Blackspear]

-{ Quote: "After reboot, received email from Eset support, suggesting I give them a dump from a tool called belarc. I did this.. it was a nice tool (www.belarc.com) I had not heard of it before.

Any way, I ran the fresh install and got the same 121 error." }-
Belarc is a good tool ;D

Would appreciate if you can keep us up to date with the results you have...

Cheers ;D

[kblist72]

Per earlier recourse, I reinstalled fresh version and received error 121.
(see nsetup-1.log)
Per earlier email, I overlaid "setup.xml" (setup-orig.xml in zipfile)
and copied "nod32.xml" (which didn't exist) into the install directory.
I ran install again (see nsetup-2.log) and got same error.
I both cases, I ran the expert option, and chose not to save icon on desktop.

(nsetup-1)
[2004-09-29 01:39:52.345] CmdLine: /test
[2004-09-29 01:39:52.355] Resource: main.dll
[2004-09-29 01:39:52.355] Is program installed?
[2004-09-29 01:39:52.355] XML_ACCESS: C:\Program Files\Eset\install - C:\Program Files\Eset\install\setup.xml
[2004-09-29 01:39:52.365] Registry: old settings read
[2004-09-29 01:39:52.385] global.xml created
[2004-09-29 01:39:52.385] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:39:52.385] XML_ACCESS: C:\Program Files\Eset\install - C:\Program Files\Eset\install\setup.xml
[2004-09-29 01:39:52.385] Main settings added
[2004-09-29 01:39:52.385] Engines nups
[2004-09-29 01:39:52.395] InstallPath added
[2004-09-29 01:39:52.395] LogPath added
[2004-09-29 01:39:52.545] EngineFile extracted
[2004-09-29 01:39:52.565] EngineFile extracted
[2004-09-29 01:39:52.585] EngineFile extracted
[2004-09-29 01:39:52.605] EngineFile extracted
[2004-09-29 01:39:53.176] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\setupc.xml
[2004-09-29 01:39:53.176] SetupAddComponentDescToGlobal
[2004-09-29 01:39:53.176] Component added
[2004-09-29 01:39:53.176] Componet libraries
[2004-09-29 01:39:53.587] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\setupc.xml
[2004-09-29 01:39:53.587] SetupAddComponentDescToGlobal
[2004-09-29 01:39:53.587] Component added
[2004-09-29 01:39:53.587] Componet libraries
[2004-09-29 01:39:53.887] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\setupc.xml
[2004-09-29 01:39:53.887] SetupAddComponentDescToGlobal
[2004-09-29 01:39:53.887] Component added
[2004-09-29 01:39:53.887] Componet libraries
[2004-09-29 01:39:53.967] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:39:53.967] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:39:53.967] - krnstp.dll
[2004-09-29 01:39:53.977] - ps_upd.dll
[2004-09-29 01:39:53.987] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:39:53.987] - ps_amon.dll
[2004-09-29 01:39:53.987] - ps_nod32.dll
[2004-09-29 01:39:53.997] - ps_dmon.dll
[2004-09-29 01:39:53.997] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 01:39:53.997] - imon.dll
[2004-09-29 01:39:54.007] - ps_nms.dll
[2004-09-29 01:39:54.999] ExeLibs: Init
[2004-09-29 01:39:55.009] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:39:55.009] - krnstp.dll
[2004-09-29 01:39:55.019] - ps_upd.dll
[2004-09-29 01:39:55.019] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:39:55.019] - ps_amon.dll
[2004-09-29 01:39:55.029] - ps_nod32.dll
[2004-09-29 01:39:55.039] - ps_dmon.dll
[2004-09-29 01:39:55.039] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 01:39:55.039] - imon.dll
[2004-09-29 01:39:55.049] - ps_nms.dll
[2004-09-29 01:39:55.059] ExeLibs: Load Current State
[2004-09-29 01:39:55.059] Error: Couldn't open Administrator's XML : nod32.xml
[2004-09-29 01:40:16.750] Registry: root written
[2004-09-29 01:40:16.750] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:40:17.140] SetupCopyFiles
[2004-09-29 01:40:17.140] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:40:17.150] - krnstp.dll
[2004-09-29 01:40:17.441] - ps_upd.dll
[2004-09-29 01:40:17.631] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:40:17.631] - ps_amon.dll
[2004-09-29 01:40:17.631] AMONPLG Status: Install case begin
[2004-09-29 01:40:18.282] AMONPLG Status: Install case end
[2004-09-29 01:40:18.292] - ps_nod32.dll
[2004-09-29 01:40:18.292] NOD32PLG Status: Install case begin
[2004-09-29 01:40:18.322] NOD32PLG Error: GetDesktopFolder
[2004-09-29 01:40:18.322] NOD32PLG Error: CreateLink
[2004-09-29 01:40:19.514] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:40:19.734] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\NSetup\
[2004-09-29 01:40:19.754] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\
[2004-09-29 01:40:19.774] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\
[2004-09-29 01:40:19.794] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\
[2004-09-29 01:40:19.804] Exitcode: 121 NOD32MOD_WINNT_ENGLISH_STANDARD


(nsetup-2)
[2004-09-29 01:42:18.645] CmdLine: /test
[2004-09-29 01:42:18.645] Resource: main.dll
[2004-09-29 01:42:18.645] Is program installed?
[2004-09-29 01:42:18.655] XML_ACCESS: C:\Program Files\Eset\install - C:\Program Files\Eset\install\setup.xml
[2004-09-29 01:42:18.665] Registry: old settings read
[2004-09-29 01:42:18.685] global.xml created
[2004-09-29 01:42:18.685] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:42:18.685] XML_ACCESS: C:\Program Files\Eset\install - C:\Program Files\Eset\install\setup.xml
[2004-09-29 01:42:18.685] Main settings added
[2004-09-29 01:42:18.695] Engines nups
[2004-09-29 01:42:18.695] XML_ACCESS: C:\Program Files\Eset\install - nod32.xml
[2004-09-29 01:42:18.695] InstallPath added
[2004-09-29 01:42:18.695] LogPath added
[2004-09-29 01:42:18.775] EngineFile extracted
[2004-09-29 01:42:18.805] EngineFile extracted
[2004-09-29 01:42:18.835] EngineFile extracted
[2004-09-29 01:42:18.855] EngineFile extracted
[2004-09-29 01:42:19.386] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\setupc.xml
[2004-09-29 01:42:19.386] SetupAddComponentDescToGlobal
[2004-09-29 01:42:19.386] Component added
[2004-09-29 01:42:19.386] Componet libraries
[2004-09-29 01:42:19.777] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\setupc.xml
[2004-09-29 01:42:19.777] SetupAddComponentDescToGlobal
[2004-09-29 01:42:19.777] Component added
[2004-09-29 01:42:19.787] Componet libraries
[2004-09-29 01:42:20.027] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\setupc.xml
[2004-09-29 01:42:20.027] SetupAddComponentDescToGlobal
[2004-09-29 01:42:20.027] Component added
[2004-09-29 01:42:20.027] Componet libraries
[2004-09-29 01:42:20.127] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:42:20.137] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:42:20.137] - krnstp.dll
[2004-09-29 01:42:20.147] - ps_upd.dll
[2004-09-29 01:42:20.147] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:42:20.147] - ps_amon.dll
[2004-09-29 01:42:20.157] - ps_nod32.dll
[2004-09-29 01:42:20.157] - ps_dmon.dll
[2004-09-29 01:42:20.167] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 01:42:20.167] - imon.dll
[2004-09-29 01:42:20.177] - ps_nms.dll
[2004-09-29 01:42:21.399] ExeLibs: Init
[2004-09-29 01:42:21.399] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:42:21.399] - krnstp.dll
[2004-09-29 01:42:21.409] - ps_upd.dll
[2004-09-29 01:42:21.419] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:42:21.419] - ps_amon.dll
[2004-09-29 01:42:21.429] - ps_nod32.dll
[2004-09-29 01:42:21.429] - ps_dmon.dll
[2004-09-29 01:42:21.439] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 01:42:21.439] - imon.dll
[2004-09-29 01:42:21.449] - ps_nms.dll
[2004-09-29 01:42:21.449] ExeLibs: Load Current State
[2004-09-29 01:42:21.459] Variables Expanded
[2004-09-29 01:42:21.459] Attempt to read Admin data
[2004-09-29 01:42:21.459] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:42:21.459] Admin xml added
[2004-09-29 01:42:40.977] Registry: root written
[2004-09-29 01:42:40.977] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:42:41.358] SetupCopyFiles
[2004-09-29 01:42:41.368] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 01:42:41.368] - krnstp.dll
[2004-09-29 01:42:41.698] - ps_upd.dll
[2004-09-29 01:42:41.889] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 01:42:41.889] - ps_amon.dll
[2004-09-29 01:42:41.889] AMONPLG Status: Install case begin
[2004-09-29 01:42:42.650] AMONPLG Status: Install case end
[2004-09-29 01:42:42.660] - ps_nod32.dll
[2004-09-29 01:42:42.660] NOD32PLG Status: Install case begin
[2004-09-29 01:42:42.690] NOD32PLG Error: GetDesktopFolder
[2004-09-29 01:42:42.690] NOD32PLG Error: CreateLink
[2004-09-29 01:42:44.052] XML_ACCESS: C:\Program Files\Eset\install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 01:42:44.272] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\NSetup\
[2004-09-29 01:42:44.292] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\
[2004-09-29 01:42:44.312] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\
[2004-09-29 01:42:44.332] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\
[2004-09-29 01:42:44.342] Exitcode: 121 NOD32MOD_WINNT_ENGLISH_STANDARD

[Blackspear]

Have you tried emptying your "Temp" folder including "Offline files", uninstalling and reinstalling as I advised above...

This time install standard version, not expert...

I have experienced an install where the Temp Folder was causing the problem...

Cheers ;D

[kblist72]

Nope.. still get 121 error.
What is the "PLG" section regarding?
I keep seeing it, regardless if I'm saving the icon to the desktop or not.

[2004-09-29 02:17:43.100] NOD32PLG Status: Install case begin
[2004-09-29 02:17:43.120] NOD32PLG Error: GetDesktopFolder
[2004-09-29 02:17:43.120] NOD32PLG Error: CreateLink


Log:
[2004-09-29 02:17:31.784] CmdLine: /test
[2004-09-29 02:17:31.794] Resource: main.dll
[2004-09-29 02:17:31.794] Is program installed?
[2004-09-29 02:17:31.794] XML_ACCESS: C:\Program Files\ESET\Install - C:\Program Files\ESET\Install\setup.xml
[2004-09-29 02:17:31.804] Registry: old settings read
[2004-09-29 02:17:31.834] global.xml created
[2004-09-29 02:17:31.834] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 02:17:31.834] XML_ACCESS: C:\Program Files\ESET\Install - C:\Program Files\ESET\Install\setup.xml
[2004-09-29 02:17:31.834] Main settings added
[2004-09-29 02:17:31.834] Engines nups
[2004-09-29 02:17:31.834] XML_ACCESS: C:\Program Files\ESET\Install - nod32.xml
[2004-09-29 02:17:31.834] InstallPath added
[2004-09-29 02:17:31.834] LogPath added
[2004-09-29 02:17:32.034] EngineFile extracted
[2004-09-29 02:17:32.064] EngineFile extracted
[2004-09-29 02:17:32.094] EngineFile extracted
[2004-09-29 02:17:32.114] EngineFile extracted
[2004-09-29 02:17:32.595] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\setupc.xml
[2004-09-29 02:17:32.595] SetupAddComponentDescToGlobal
[2004-09-29 02:17:32.595] Component added
[2004-09-29 02:17:32.595] Componet libraries
[2004-09-29 02:17:32.975] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\setupc.xml
[2004-09-29 02:17:32.975] SetupAddComponentDescToGlobal
[2004-09-29 02:17:32.975] Component added
[2004-09-29 02:17:32.975] Componet libraries
[2004-09-29 02:17:33.266] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\setupc.xml
[2004-09-29 02:17:33.266] SetupAddComponentDescToGlobal
[2004-09-29 02:17:33.266] Component added
[2004-09-29 02:17:33.266] Componet libraries
[2004-09-29 02:17:33.356] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 02:17:33.356] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 02:17:33.356] - krnstp.dll
[2004-09-29 02:17:33.366] - ps_upd.dll
[2004-09-29 02:17:33.376] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 02:17:33.376] - ps_amon.dll
[2004-09-29 02:17:33.386] - ps_nod32.dll
[2004-09-29 02:17:33.386] - ps_dmon.dll
[2004-09-29 02:17:33.396] Cmd: 0 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 02:17:33.396] - imon.dll
[2004-09-29 02:17:33.396] - ps_nms.dll
[2004-09-29 02:17:34.548] ExeLibs: Init
[2004-09-29 02:17:34.548] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 02:17:34.548] - krnstp.dll
[2004-09-29 02:17:34.558] - ps_upd.dll
[2004-09-29 02:17:34.568] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 02:17:34.568] - ps_amon.dll
[2004-09-29 02:17:34.568] - ps_nod32.dll
[2004-09-29 02:17:34.578] - ps_dmon.dll
[2004-09-29 02:17:34.588] Cmd: 2 Exelib: NOD32MOD_WINNT_ENGLISH_INET
[2004-09-29 02:17:34.588] - imon.dll
[2004-09-29 02:17:34.598] - ps_nms.dll
[2004-09-29 02:17:34.598] ExeLibs: Load Current State
[2004-09-29 02:17:34.598] Variables Expanded
[2004-09-29 02:17:34.598] Attempt to read Admin data
[2004-09-29 02:17:34.598] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 02:17:34.608] Admin xml added
[2004-09-29 02:17:41.798] Registry: root written
[2004-09-29 02:17:41.798] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 02:17:41.948] SetupCopyFiles
[2004-09-29 02:17:41.958] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_BASE
[2004-09-29 02:17:41.958] - krnstp.dll
[2004-09-29 02:17:42.279] - ps_upd.dll
[2004-09-29 02:17:42.459] Cmd: 3 Exelib: NOD32MOD_WINNT_ENGLISH_STANDARD
[2004-09-29 02:17:42.459] - ps_amon.dll
[2004-09-29 02:17:42.459] AMONPLG Status: Install case begin
[2004-09-29 02:17:43.090] AMONPLG Status: Install case end
[2004-09-29 02:17:43.100] - ps_nod32.dll
[2004-09-29 02:17:43.100] NOD32PLG Status: Install case begin
[2004-09-29 02:17:43.120] NOD32PLG Error: GetDesktopFolder
[2004-09-29 02:17:43.120] NOD32PLG Error: CreateLink
[2004-09-29 02:17:44.151] XML_ACCESS: C:\Program Files\ESET\Install - C:\DOCUME~1\Kerrie\LOCALS~1\Temp\global.xml
[2004-09-29 02:17:44.382] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\NSetup\
[2004-09-29 02:17:44.402] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpa\
[2004-09-29 02:17:44.422] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpb\
[2004-09-29 02:17:44.442] Deleting directory: C:\DOCUME~1\Kerrie\LOCALS~1\Temp\nodtmpc\
[2004-09-29 02:17:44.452] Exitcode: 121 NOD32MOD_WINNT_ENGLISH_STANDARD

[Blackspear]

Do you have any other antivirus programs installed?

Are you using a registry monitor such as Tea Timer in Spybot Search and Destroy or SSM?

Cheers ;D

[kblist72]

No to both..

The only anti-vir I have is NOD, which is no longer functional until
getting around this 121 error.

I ran Lavasoft's Adaware earlier today (new update downloaded)

I have used SpyBot in the past, but not for some time.
I'll redownload it off of zdnet and see if anything comes up.

[Blackspear]

-{ Quote: "No to both..

The only anti-vir I have is NOD, which is no longer functional until
getting around this 121 error.

I ran Lavasoft's Adaware earlier today (new update downloaded)

I have used SpyBot in the past, but not for some time.
I'll redownload it off of zdnet and see if anything comes up." }-
Are you installing from a Administrator Account, not as a guest account?

[kblist72]

SpyBot found 44 issues and fixed them; also immunized against 2200+ others.

The only 'active' accounts on my XP box are admin accounts. I don't think there is a way to slice/dice permissions with those, right?

[Marcos]

The problem is the NOD32 installer is not getting the directory name from the oper. system for some reason (e.g. if user profiles are stored on a server). We'll need to gather more Belarc logs to see what the systems affected have in common.

[kblist72]

My system is a stand alone one; ie, not on a network, if that is what you mean.

I have 3 admin accounts, 2 of them are primarily used.

I can try pasting an image of my Belarc data here if desired; I don't see a file upload option.

[kblist72]

On a whim, I tried the other admin account and it still gives me the error.
I need to get some sleep, but will return back in about 7 hours. (3am here)


Thanks for all the quick and elightening responses.

[Blackspear]

Does you "Temp" folder exist here, and when you look inside this folder, is it empty?

C:\Documents and Settings\Kerrie\Local Settings\Temp

Cheers ;D

[kblist72]

It wasn't; I had the folder hidden so I didn't see it at first.

Is there an automatic way to purge this? I'm suprised that the Norton "Cleanup" didn't go there yesterday when I purged out a bunch
of things.

Will try install again.. Thanks for that tip.

[kblist72]

Expert/desktop option disabled installation ran.
Still got 121 error .

[Blackspear]

-{ Quote: "Expert/desktop option disabled installation ran.
Still got 121 error ." }-
Have you heard back from Eset regarding the Berlac log that you sent them?

Cheers ;D

[Blackspear]

-{ Quote: "...I'm suprised that the Norton "Cleanup" didn't go there yesterday when I purged out a bunch of things...." }-
Did you have Norton installed?

If so, can you do a registry clean of anything that remains of it...

Cheers ;D

[kblist72]

Nothing back yet from Eset regarding the Berlac log..

I've used norton to clean up registry problems using the "one button fix" feature.

[rumpstah]

Hi kblist72:

Do you have Norton Utilities installed?

-{ Quote: "Nothing back yet from Eset regarding the Berlac log..

I've used norton to clean up registry problems using the "one button fix" feature." }-

[kblist72]

Uh, Norton SystemWorks.. same thing basically I guess.
It has Norton Utilities within the suite.

[rumpstah]

That may be causing your issue since it monitors system activities.

Can you disable using msconfig? I have seen this hault software installs.

-{ Quote: "Uh, Norton SystemWorks.. same thing basically I guess." }-

[kblist72]

It does not appear to be resident; there is a ghost icon, but that is it.
(via msconfig)
Although, the running task list does seem to bear quite a few listings..
May have to go through and interrogate some of the entries.


Running tasks (user)
explorer.exe
taskmgr.exe
GoogleFah.exe
iexplore.exe
GWREMIND.EXE
callerid.exe
SETI@home.exe
GoogleFahCore_6...
jusched.exe
sqlmangr.exe
AIRPLUS.EXE
GoogleDCC.exe
wcescomm.exe
zlclient.exe
GhostStartTrayAp....
realsched.exe
webshots.scr

Running tasks (NETWORK SERVICE)
msdtc.exe
WISPTIS.EXE
svchost.exe
svchost.exe

Running tasks (LOCAL SERVICE)
alg.exe
svchost.exe

Running tasks (SYSTEM)
mgtgsvc.exe
tcpsvcs.exe
ServUDaemon.exe
nvsvc32.exe
NPROTECT.EXE
sqlservr.exe
mdm.exe
inetinfo.exe
GHOSTS~2.EXE
SAgent2.exe
spoolsv.exe
svchost.exe
mqsvc.exe
svchost.exe
lsass.exe
services.exe
winlogon.exe
csrss.exe
smss.exe
vsmon.exe
NOPDB.EXE
snmp.exe
System
System Idle Process

[rumpstah]

You may want to disable the following and then try your NOD32 install.
NPROTECT.EXE (Norton Unerase Protection)
GHOSTS~2.EXE (Norton Ghost Start Service)
NOPDB.EXE (Norton Speed Disk)

-{ Quote: "It does not appear to be resident; there is a ghost icon, but that is it.
(via msconfig)
Although, the running task list does seem to bear quite a few listings..
May have to go through and interrogate some of the entries.


Running tasks (user)
explorer.exe
taskmgr.exe
GoogleFah.exe
iexplore.exe
GWREMIND.EXE
callerid.exe
SETI@home.exe
GoogleFahCore_6...
jusched.exe
sqlmangr.exe
AIRPLUS.EXE
GoogleDCC.exe
wcescomm.exe
zlclient.exe
GhostStartTrayAp....
realsched.exe
webshots.scr

Running tasks (NETWORK SERVICE)
msdtc.exe
WISPTIS.EXE
svchost.exe
svchost.exe

Running tasks (LOCAL SERVICE)
alg.exe
svchost.exe

Running tasks (SYSTEM)
mgtgsvc.exe
tcpsvcs.exe
ServUDaemon.exe
nvsvc32.exe
NPROTECT.EXE
sqlservr.exe
mdm.exe
inetinfo.exe
GHOSTS~2.EXE
SAgent2.exe
spoolsv.exe
svchost.exe
mqsvc.exe
svchost.exe
lsass.exe
services.exe
winlogon.exe
csrss.exe
smss.exe
vsmon.exe
NOPDB.EXE
snmp.exe
System
System Idle Process" }-

[kblist72]

This problem is unresolved. The references in the registry that I mentioned to Eset which were outside HKLM\Software "should not cause this problem."

The log was not helpful enough for them to determine "what program on your computer is causing the installation problem"

Solution/Suggestion was to re-install XP, as they stated, "A clean install of Windows should certainly fix the problem, but it is up to you to make that decision"

Should.. Should.. not a Does/Not. All I can say is, Oh Joy. :)
A refund has been offered, but that does not protect me from viruses.

Not sure what to do, but looks like I have some more quality time with my PC to look forward to this weekend. On the bright side, I'll get a virgin XP Ghost image, and maybe one with all the service packs and patches. (about 50-60 downloads, I reckon)

[Blackspear]

-{ Quote: "This problem is unresolved. The references in the registry that I mentioned to Eset which were outside HKLM\Software "should not cause this problem."

The log was not helpful enough for them to determine "what program on your computer is causing the installation problem"

Solution/Suggestion was to re-install XP, as they stated, "A clean install of Windows should certainly fix the problem, but it is up to you to make that decision"

Should.. Should.. not a Does/Not. All I can say is, Oh Joy. :)
A refund has been offered, but that does not protect me from viruses.

Not sure what to do, but looks like I have some more quality time with my PC to look forward to this weekend. On the bright side, I'll get a virgin XP Ghost image, and maybe one with all the service packs and patches. (about 50-60 downloads, I reckon)" }-
Unfortunately when it gets to a stage like this, then a format of Windows “should” resolve your problem. This industry (computers) uses the term “should” because unlike most other industries there are so many variables.

On the bright side, I am yet to see a computer come through one of my shops that Nod32 can not be installed on…

All the best…

Cheers ;D

PS. Rumpstah may have more suggestions, though having Eset respond in the manner they have, it may also be towards the end of the road for his advice :(

[kblist72]

Thanks.. I was admittedly surprised, but understand..
I hope it is not something to do with SP2, but I cannot be sure until I try the 'refresh OS' process.. And if it is, I'll have to go to something else, unfortunately.

[Blackspear]

-{ Quote: "Thanks.. I was admittedly surprised, but understand..
I hope it is not something to do with SP2, but I cannot be sure until I try the 'refresh OS' process.. And if it is, I'll have to go to something else, unfortunately." }-
It's not, SP2 works well with Nod32...

I would still hold off for a little while to see if Rumpstah has any further suggestions...

Cheers ;D

[kblist72]

Agreed, but I can't hold off for too long... I have a business trip coming up in a week and I want the PC protected while I'm gone so my wife can use it without issue.

[Blackspear]

-{ Quote: "Agreed, but I can't hold off for too long... I have a business trip coming up in a week and I want the PC protected while I'm gone so my wife can use it without issue." }-
Rumpstah sent you a PM...

Cheers ;D

[kblist72]

Got the PM, but had already started the refresh process.. I'm 4.5 hours in, with 2 ghost images saved.

Anyone having problems downloading updates from NODs servers tonight?
All 4 seem to be failing for me; Internet is working fine otherwise..
Have put up SE version of Lavasoft Adaware and Spybot and updated both just fine.
Also seemed to have more of "Nortons Utils" running in the background.. the NAV might have been clobbering the install.. have disabled most of the Norton's SystemWorks functionality now..

[Blackspear]

-{ Quote: "Got the PM, but had already started the refresh process.. I'm 4.5 hours in, with 2 ghost images saved…" }-
No worries.


-{ Quote: "…Also seemed to have more of "Nortons Utils" running in the background.. the NAV might have been clobbering the install.. have disabled most of the Norton's SystemWorks functionality now.." }-
May I make a suggestion that you try everything without Norton System Works.

Good to see you are imaging… A good practice.

Hope this helps…

Cheers ;D

[kblist72]

Well, after all was said and done, my system is up and protected.
I think in all, it took about 11.5 hours with a few breaks (leaving the computer to run its task(s)).

I actually did not notice the above suggestion with the 3 files, but I susepct you were on the right track.. I suspect "NProtect" may have been at fault for the install, but can't be sure. I know the "NAV" caused my system to lock up at one point, probably trying to clobber the NOD process or something. The only use I have for the Norton SystemWorks are the embedded utils for Ghost and the 'One Button Fix' feature. Although, I think I could probably find a better registry cleaner/fixer-upper.

While I regret the hours spent to get to this point, I do now have a fresh system and feel confident moving forward now.

If of interest, I have 4 total images now:
- (1.04GB) Virgin XP , drivers (printer,soundcard,wifi card)
- (2.097GB) XP , SP2 (and all patches)
- (2.097GB) XP/SP2 , internet/security applications
- (2.097GB) XP/SP2+ , Internet/Windows Applications (and addl patches)
(I did notice a "Spanned image file, ".GHS" which seem to follow the
last session recorded.. can anyone confirm this? - Not sure if its a temporary file -to delete - or not) The last 3 were high compression; I realized the default was "Fast" after I had already recorded the first session.

There's technically a 5th I would like to do, but these being burned
are on hold until I get a dvd burner; each is around 1.7-2 Gig a piece.
I have my .NET applications to throw up now, so I'll have some more work ahead of me on this new day. :)

Thanks to all for helping me on this.. I have a better appreciation for what is running in one's system! :)

[Blackspear]

Good to see you have had a result.

I use 2 registry programs: Registry Mechanic available from here (http://www.winguides.com/) and Regseeker available here (http://www.snapfiles.com/get/regseeker.html)

Hope this helps...

Cheers ;D

[kblist72]

Graci.. I'll check them out..

[Guiwas]

-{ Quote: "The problem is the NOD32 installer is not getting the directory name from the oper. system for some reason (e.g. if user profiles are stored on a server). We'll need to gather more Belarc logs to see what the systems affected have in common." }-

This was the ONLY site I found with Google about this error!
I solved this issue on a customers' PC today.
On that PC it was caused by insufficient registry permissions for the installing user. Although logged in as a user in the administrator group the access to certain keys (e.g. ESET) was not allowed.

It was changed by right-click on key>permissions>tick appropriate boxes.
Then I deleted the ESET key in software.
Restarted and then re-installing NOD32 (commercial version) finished normally.

Hope this helps!

[Blackspear]

Guiwas, welcome to Wilders, and thanks for the information.

Are you a Nod32 reseller?

Cheers ;D

[Guiwas]

Blackspear,
Thanks for your welcome and
Yes, I am an NOD32 reseller in the Netherlands since around 1 year now.
and a very happy one too, for that matter.

You are quick with your reply!
I just surfed back to my own post to copy it to the NOD reseller e-mail forum and saw your reply.
What is this 'wilders security' that it has special forums on NOD32?

Thanks again, Guiwas.

[Blackspear]

-{ Quote: "What is this 'wilders security' that it has special forums on NOD32?" }-
Wilders Security hosts the "Official" Nod32 Forum as well as forums for other world class software.

Hope this helps...

Cheers ;D

[Lu4]

Just trying NOD32 out on trial,
and can't get the dam thing to install
as kblist72, said.
Since I haven't bought it, but have heard so much about it,
I thought I'd give it a try. I guess I won't
get any preferential treatment,
but I did a search on google and found this post.
Tried everything here, said, (changed "permissions", don't have
and never will have Symantec)
and still no luck.
I also have a mail into the NOD techs.
I have WinXP, Adaware, TDS, Kerio 4.12 Firewall,
Registry firewall on my machine,
and just installed Avast Pro v4.5 trial which at least installed itself
on my machine.
Any leads?
thanks, Lu

[ronjor]

-{ Quote: "just installed Avast Pro v4.5 trial" }-

Welcome Lu4.

Uninstall Avast and try a reinstall of NOD. You might want shut down any running programs except your firewall while you install NOD.

[Lu4]

Already done that.
Un-installed Avast twice,
Tried re-installing NOD32;
shut down registry firewall,
and still no luck.
I haven't tried turning off my Kerio firewall,
but have never had a problem installing
any program with it on so far.

[ronjor]

Lu4

I'm not sure why NOD won't install for you. Others may have ideas as to the problem.

There are certain antivirus programs that do not get along with each other on the same hard drive.

There will be other replies.

[Marcos]

Please make sure the "documents and settings\all users\desktop" folder actually exists on the disk. If you are using other than English version of Windows XP, the name of the folder may be translated to the corresponding language.

[Lu4]

Thanks Marcos!
And also the quick response from your techs!!!

The problem was located in my WinXP not having a "Desktop"
Folder (empty) in Documents and Settings/Users.

You may want to suggest a program change to make this empty
folder on application starts, as I am probably not the only
one out there with this folder missing.
(I don't keep icons on my desktop).

I am very happy with NOD32 v 2.12.3.

It passed my scan test on my system,
when many others failed. (Kaspersky v5.0, Avast 4.5 pro, AVG, etc.)

Where did the others fail?

"ARCHIVE" scanning!

I have some rar and ace archive 100MB to 300MB
in size, and even though ESET did not scan through them,
they are smart enough to list these files in the "real-time"
scanning log, as to a possible potential threat, if opened.
(that is all you really need anyways.)

As for the other AV's that I tried?

They all "blue-screened" me half-way to 3/4's through the scan.
(Kaspersky at least informed me that it was caused by a large
archive, where the others just left you in the cold and NO explantation,
even on restart and checking of logs!)

This is as bad as having a virus.
Don't they get it?


Thanks for all your help guys.
I am sure I'll be using this program.

Lu



Nigel Cook <cook@eset.sk>
To: lu4
Subject: Re: [support] Support request: cannot tryout trial
Date: Fri, 18 Feb 2005 08:42:31 +0100

--------------------------------------------------------------------------------

Hello Lu,

Regarding this error code: On some WinXP systems, the "Documents and Settings\All Users\Desktop" folder is not created automatically. Please make sure it actually exists on the disk, otherwise create it.

Regards,
Nigel.

Eset Technical Support
Website: www.eset.com
Email: support@eset.com
NOD32 Help Forum: www.wilderssecurity.com/forumdisplay.php?f=16

[Blackspear]

-{ Quote: "Regards, Nigel." }-Good to see you had a result, and thanks for keeping us up to date with your progress, as we all learn this way. I also see you have met our Wilders Bandicoot, also known as Mr Cook, Mr Coot, or that liddle rodent that scurries about the halls of Wilders ;) ;D :lurking:

You might like to run through Extra Settings for Nod32 (http://www.wilderssecurity.com/showthread.php?t=37509) to give Nod a bit of a tweak...

Hope this helps...

Cheers ;D

[scrood]

I thought I'd add this to help others, because a Google search turned up nothing when I looked.

I was trying to install NOD32 2.12.3 on WinXP Pro SP-2. I first got the same error the OP had (which is how I found this thread!). OK, so the NOD32 installer needs work (sorry, it does), I'll manually create the "...All Users\Desktop" directory. But then, I got this error:

(120) Error occured while registering the service. NOD32MOD_WINNT_ENGLISH_STANDARD

After some frustration, I finally figured out the problem. I was extracting the setup files to "C:\Program Files\NOD32\Setup", and then trying to install NOD32 to "C:\Program Files\NOD32". This made the installer throw a fit because it tries to create a "C:\Program Files\NOD32\Setup" directory of its own, and again, it needs work (sorry again, but it's still true).

So, just keep the default "install" directory, and don't rename it to "setup". By the way, the reason I tried using "C:\Program Files\NOD32\Setup" was that it's habit--lots of installers these days want to save their setup files, and they preconfigure for you that exact (relative) directory. I was just trying to maintain consistency, but the NOD32 installer couldn't handle it.

Hope that helps someone.

[Blackspear]

Thanks for that Scrood.

Cheers ;D

[Georgio]

It is possible that NOD32 cannot place shortcut to your desktop. Check if this folder exists: C:\Documents and Settings\All Users\Desktop. If not create it and try to install again.

[Pat445]

Hello. After searching for answers all day, I´ve finally found this page. I have the same problem posted here, but I run Windows 98. I want to try Nod32 and I downloaded the 2.50 version. When it´s almost finished the install, it pops up a message:
(121)Nod32Mod_Win98_Spanish_Inet

and the installation failed. I read all this posts and suggestions, but I don´t know how to adapt the steps to Windows 98, cause the folder desktop doesn´t exists. I uninstalled Norton systemworks 2004 Pro. I guess I will have to delete some registry keys or something. If anybody could help me, I would really appreciate it. Thanks so much.
PS: I´m not an english speaker, so my writing is not very good, I apologize in advance.

[alglove]

-{ Quote: "(121)Nod32Mod_Win98_Spanish_Inet

and the installation failed. I read all this posts and suggestions, but I don´t know how to adapt the steps to Windows 98, cause the folder desktop doesn´t exists. I uninstalled Norton systemworks 2004 Pro. I guess I will have to delete some registry keys or something. If anybody could help me, I would really appreciate it. Thanks so much.
PS: I´m not an english speaker, so my writing is not very good, I apologize in advance." }-
In Windows 98, the folders are C:\Windows\Desktop and C:\Windows\Temp . If you still have problems, it may be something to do with Norton Systemworks 2004.

[Marcos]

-{ Quote: "Hello. After searching for answers all day, I´ve finally found this page. I have the same problem posted here, but I run Windows 98. I want to try Nod32 and I downloaded the 2.50 version. When it´s almost finished the install, it pops up a message:
(121)Nod32Mod_Win98_Spanish_Inet
" }-

The 121*_Inet error means that there was a problem installing IMON or EMON. I'd suugest to try repairing the lsp stack (there's a free utility lspfix available on the web) or the entire Winsock. Be careful with that and do it only if you know what you are doing.

[Pat445]

Thanks for your replies. About Norton, I deleted any traces of it in my system, I search and there´s not a single process or archive of Norton. The two folders (Desktop and Temp) exists.
About the Lspfix, I really don´t know how or what to fix. But my Internet connection is working fine, at least, I am able to access the net.
Should I run Lspfix anyway?
Maybe I should try another antivirus, like Avast?
I have Nod32 in my job, and I like Nod so much !!
Thanks so much for your attention.

[alglove]

-{ Quote: "About the Lspfix, I really don´t know how or what to fix. But my Internet connection is working fine, at least, I am able to access the net.
Should I run Lspfix anyway?" }-
Yes, run LSPFix. The "LSP" is a part of the Windows TCP/IP that lets programs (like antivirus and firewalls) install "plugins" like a chain. Sometimes this chain gets broken. Some parts of TCP/IP will still work, but others get broken.

Here is a link to LSPFix. It is easy to run. Just download it and go!

http://www.cexx.org/lspfix.htm

[Blackspear]

Further information here:

http://www.wilderssecurity.com/showthread.php?p=462132#post462132

Cheers ;D

[Pat445]

It didn't work. I executed the LspFix. These are the files that appears in the list "Keep":
rnr20.dll
mswsosp.dll
msafd.dll
rsvpsp.dll
The list "Remove" appears empty. I clic in "Finish".
After restarting, I proved to repair winsock32, following the instructions that are in the tutorial:

http://www.wilderssecurity.com/showthread.php?p=462132#post462132
I tried again to install Nod32, but the same error appears.
I will try with other alternatives. Thank you anyway.

[Marcos]

Have you tried repairing Winsock by following Blackspear's instructions?

[Pat445]

Yes. I reinstall TCP/IP after deleting the keys and restarting but there is no change. Still getting the error.
Thanks.

[Blackspear]

-{ Quote: "Yes. I reinstall TCP/IP after deleting the keys and restarting but there is no change. Still getting the error." }-Did you try the actual Winsock XP Fix (http://www.spychecker.com/program/winsockxpfix.html) tool and then repair IMON? (http://www.wilderssecurity.com/showpost.php?p=450639)

Cheers ;D

[Pat445]

No, I have Windows 98, and Winsock XP Fix is for Win XP, no?

[Blackspear]

-{ Quote: "No, I have Windows 98, and Winsock XP Fix is for Win XP, no?" }-This one (http://www.tacktech.com/display.cfm?ttid=257) works for Windows 98. After running this tool, then repair IMON. (http://www.wilderssecurity.com/showpost.php?p=450639)

Let us know how you go...

Cheers ;D

[Pat445]

Thank you. I´ll try this. I have to go out now, but tomorrow I let you know if it works
Cheers

[Pat445]

No, it didn´t work. I ran WinsockFix, but I couldn´t get to the point of seeing the Nod32 window, because it just refuses to install. I think this is it. I´ll try other alternatives. Thanks so much anyway for your effort with the help and patience.
Greetings for all of you from Argentina.

[Marcos]

Well, a log from setup might explain whether the problem occurs during the installation IMON or EMON. If the former, you might want to try repairing TCP/IP per Blackspears instructions.