NIS 2005 uninstaller instructions

[farmor]

Has anyone gone through the lengthy uninstall and reinstall procedures when the initial attempt at installing NIS 2005 fails? This involves download of nis200598_reg_removal.reg and using it to cleanse the registry of NIS 2005 bits. Then download of Windows Script 5.6 and installation of it (why, since it wasn't there before?) then manually deleting any Norton folders and files. (According to the NIS 2005 manual, it was supposed to install over NIS 2004 and use its settings, but instead it wiped it out.) Is the reg removal program safe or does it destroy the system? I've had a year's worth of problems and downloaded bugs with Norton and am understanably suspicious. Thanks for any help and advice. (I've looked into AVG but believe I read it doesn't work with Netscape or 98 or both. Also a friend's computer was infected with a virus while using it. Have EZArmor loaded currently about which I've read raves and pans.)

 

[farmor]

No replies to my query so I finally braved it and went through the whole process. Well, it DOES do some DAMAGE. One of Symantec's removal instructions empties the Recycle Bin. In my opinion no software should do that without permission and without informing the user that it wants to do it.
And after all that,
NIS 2005 STILL WOULD NOT LOAD.

 

[iamnotageek]

We haven't had to remove a cratered NIS2005 initial install on win98, but have had to do it a couple times on XP, and it went ok. FWIW, there is a different removal utility used for xp (RnisUPG.exe). These cases happened after using utilites to migrate customers' data files and settings from their old machine to a new virgin xp machine. Seems that some things are transferred from the registry that shouldn't have been.

The ones that have been fun for us are the ones where NIS200x had been up and running and something happened to mortally wound it. Even after deleting the directories, the reinstall is pretty rocky - you have to ignore the error messages and just keep running LiveUpdate (once you get to that point) until all the errors go away. This is apparently a result of dll version differences, as the removal util (and the uninstaller) don't remove all the files from \system and/or \system32.