NOD32 version 2 Installation Glitch

Installation of NOD32 version 2 on a computer with MS Windows 2000 Professional with Service Pack 4 hangs immediately after the 'system restart' program installation screen message; which is at the blue screen following the acutal 'windows shut-down' message. The system had to be manually powered down and powered back on; wherein the NOD32 program functioned flawlessly! The necessity of the manual intervention in the installation process could possibly make a novice a little nervous; and doubt the correct functioning of the NOD32 program itself, since the installation process could not complete on its own. Any ideas or questions would be welcomed.

POSTNOTE: A description of the inability of the NOD32 installation program to complete 'normally' was sent to the NOD32.com technical support center several days ago...no reply or acknowledgement of receipt of the problem description has been forthcoming.

 

Hi Vigilante,

Could you write down you configuration? And could you also include some non-standard software, which you use (if so)?

non-standard software = software other than from microsoft

This could help eset to solve you problem.

regards

Vigy

 

The hardware configuration is pretty much standard and mundane, and is as follows:

a. Abit KR7A-133 Motherboard
b. AMD XP1800 CPU
c. 512MB PC2100 DDR
d. ATI 8500LE w/128MB
e. Yamaha 16 Bit Sound Card
f. Western Digital 40GB IDE Hard Drive
g. Sony CRX-185E1 CD Unit
h. Mitsubishi 1.44 Floppy Drive
i. LS120 High-Density Drive
j. Linksys LNE100TX V5 NIC
k. Linksys BEFCMU10 V2 Etherfast Cable Modem
l. Linksys BEFSR41 V2 Etherfast Cable/DSL Router

The software configuration running normally during any program installation is pure Microsoft and as standard as it gets, and is as follows:

a. Microsoft Windows 2000 Professional Operating System w/SVC Pack 4 and all current updates.
b. Microsoft Outlook 2000 w/all updates (not running during NOD32 installation).
c. ZoneAlarm V4.0.146.029 Firewall Software (not running during NOD32 installation – even de-installed as an experiment during several subsequent NOD32 installation trials, in the event that a ‘service’ was running)

The only problem I have with the NOD32 package is with the inability to ‘hands-off’ complete the installation and the fact that the documentation does not match the software package; however, the on-line help is sufficient for most users to navigate the software setup scenarios. The only other difficulty I had was with my misguided understanding of how IMON handles infected email and email attachments; which was also transmitted to NOD32 support, and which they should now disregard.

 

Hi,

Can you start windows in safe mode?
You could try - when installing NOD32, try to disable AMON and IMON. When the computer starts normally, try to load them (but not at one time).

Vigy

 

You really have me guessing now!! The problem is not in the ability to START windows after the NOD32 installation, or even run the NOD32 program for that matter; but, rather the NOD32 installation program's ability to 'SHUT DOWN and RESTART' windows upon completing it's work of installing NOD32 initially on a clean system that had no trace of NOD32 installed, EVER!!

I'm not certain whether the AMON or IMON program modules would even be running at the point the NOD32 installation program is attempting to 'RESTART' windows during the initial NOD32 installation process. Besides, since this is the only software installation program that I have run across recently that 'HANGS' during the windows 'RESTART' process; I'm not sure why I would be troubleshooting the windows 'START UP' process in the first place!!

Maybe I misunderstand your question; if I did, perhaps you should elaborate??

I have to surmise that since I haven't received an acknowledgement from the NOD32 technical support team regarding my online request; and the fact that evidently no one else has had an NOD32 installation problem, that I must be alone having the described problem. It's not an overriding issue since the NOD32 program apparently does function correctly after the 'installation glitch'; it's just an annoyance on my part of having to tolerate a perceived 'buggy' installation package!!

Perhaps if the Eset on-line help and .pdf documentation for the NOD32 software corresponded to the current version's 'installed' modules, functioning, and 'actual' program screens; the need for the vast majority of the questions and opportunities for 'expert' opinions and demonstrations of 'self-perceived' technical prowess in the associated forums; here, and otherwise would be vastly diminished!!

 

Ok, sorry for that, I first thought you were having problem after the hard restart. Well, I didn't mean stopping AMON and IMON proces, but you can choose, whether AMON will load at startup or not. So you can install NOD32 with minimal protection - not loading AMON, IMON loading at startup.
Were you logged on as an admin?
BTW: You should have by default in windows set in enviroment variables TEMP and TMP to some directory.

Vigy

 

No sir; the only problem, other than the program documentation, is the actual NOD32 installation program, which doesn't work as it should; that is , does't 'restart' the computer upon completion of the installation process. Yes to your second part, I am the only one with administrative priviledges on the system, and the system temporary folders are just fine.

Thanks for the thoughts.

 

I had recently Installed NOD32 on a friends PC using Microsoft Windows 2000 Pro with Service Pack 4 and she went on smoothly and shutdown flawlessly to re-boot the System. You could possibly have Software or even Hardware Conflict, did you try installing NOD32 after terminating all 3rd party processes in Windows Task Manager? And does it appear “ALL” you’re Hardware properly installed, have you checked in Device Manager to see any obvious?

 

Possibly. However, the key issue here is that this is the 'only' software installation program that I have had 'any' difficulty with. So, as I said before, with nothing but MS software running and no peculiar hardware issues that I could even begin to 'speculate' about, your guess is as good as mine. I'm also starting to catch a glimpse in this and other forums of 'hanging' problems in both MS 2000 and XP environments; although they aren't necessarily installation involved! I've had a couple of emails indicating a few individuals having XP difficulties have received an updated .dll file; although, I've seen no signs of updated files on the Eset sites. So, I'm not so sure the current NOD32 version is as stable as the Eset people would lead us to believe! However, and to their favor, after my installation fiasco; the program has performed flawlessly, at least so far as I can tell! Still no answers regarding the error in the IMON on-line help or the inaccurate .pdf documentation.