NOD32MOD_WINNT ENGLISH STANDARD

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)

 

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

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

 

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

 

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

 

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..

 

No worries.

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

 

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!

 

Good to see you have had a result.

I use 2 registry programs: Registry Mechanic available from here and Regseeker available here

Hope this helps...

Cheers

 

Graci.. I'll check them out..

 

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!

 

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

Are you a Nod32 reseller?

Cheers

 

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.

 

Wilders Security hosts the "Official" Nod32 Forum as well as forums for other world class software.

Hope this helps...

Cheers

 

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

 

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.

 

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.

 

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

 

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

You might like to run through Extra Settings for Nod32 to give Nod a bit of a tweak...

Hope this helps...

Cheers

 

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.

 

Thanks for that Scrood.

Cheers