NIS 2004, Windows Update, XP compatibility

[Bob]

Since installing Norton Internet Security 2004 under XP I
have had problems.

1 The start up process seems to stall before the NIS icon
appears with the egg timer visible when the cursor is over
the task bar. Sometimes it loads after a few minutes.

2 Windows Update seems to stall when updating. It
downloads the files OK but hangs when the installation
begins.

Are there known compatibility problems with NIS2004?

Bob

 

[Rick \Nutcase\ Rogers]

Hi Bob,

Are there known compatibility problems with NIS2004?

Yes, uninstall it, return it to the store. Or at least that's what I would
do. There are other antivirus and firewall programs that are far less
intrusive on a system than Norton's utilities are. It (Norton's firewall) is
also a known cause of the update site failure. Either that, or try getting
help from Symantec:
http://www.symantec.com/techsupp/

Antivirus program:
AVG from www.grisoft.com

Firewalls:
http://www.kerio.com/kpf_home.html
http://www.zonelabs.com/store/content/home.jsp
http://www.tinysoftware.com/home/tiny2?la=EN

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Crusty \(-: Old B@stard :-\)]

There is a problem (that I have experienced an quite a few computers) with
Norton AntiVirus 2004 not playing nice with the page file. When it happens
the symptoms you describe are exactly as I have experienced. I was able to
get around the problem by putting the pagefile on a different hard drive
(not a different partition on the same hard drive).

Another work around is to set the pagefile as "system managed" on the
Windows partition, if all you have is one hard drive.

 

[Guest]

I completely agree with Rick's position. Unfortunately for me, the 60 day Symantec return period had expired before my problems arose. I have since been working with Symantec technicians, spending hours and hours uninstalling, manually editing the registry, performing clean boot's, etc. etc.

I purchased NIS 2004 to reduce the likelihood of damage to my system. In my 20 years of computer experience, no program or virus has ever damaged my system to the extent NIS did!

The biggest problem is that NIS installs a large number of peices into various files and folders throughout your system. Symantec doesn't seem to be able to find where these are. Furthermore, Symantec's instructions aren't always possible to follow. (I wonder if anyone at Symantec has ever actually seen an XP system!!!)

----- Bob wrote: -----

Since installing Norton Internet Security 2004 under XP I
have had problems.

1 The start up process seems to stall before the NIS icon
appears with the egg timer visible when the cursor is over
the task bar. Sometimes it loads after a few minutes.

2 Windows Update seems to stall when updating. It
downloads the files OK but hangs when the installation
begins.

Are there known compatibility problems with NIS2004?

Bob

 

[R. McCarty]

Here's the drill for Removing/Cleaning up Symantec to get ready
to install a new version. NIS, unfortunately has a track record
of not handling upgrades of itself over earlier versions or when a
different product is added over an older one (NIS over Nav,etc)
1. Run Add/Remove Programs uninstaller for NIS
2. --------------------------------------- for Live Update
3 ---------------------------------------- for Live Reg
4. Download and Run RNis.Exe (Removes Registry Keys)
- Available on Symantec's Web site, new version is now
out to handle version 2004
5. Search your C: drive for all instances of "Symantec"
a. Remove the Common Files folder \Symantec
6. Reboot & rerun your installer.
** Symantec's services must start properly, especially
CCevnt.Sys. When the start mode of certain NIS
services are wrong (Boot, instead of Demand, etc)
you'll get the startup situation you describe.
Just make sure before you do this procedure that you have a
valid Image/Backup of your PC. Over the past 4-months I've
encountered this type of issue numerous times.

I completely agree with Rick's position. Unfortunately for me, the 60 day

Symantec return period had expired before my problems arose. I have since
been working with Symantec technicians, spending hours and hours
uninstalling, manually editing the registry, performing clean boot's, etc.
etc.

I purchased NIS 2004 to reduce the likelihood of damage to my system. In

my 20 years of computer experience, no program or virus has ever damaged my
system to the extent NIS did!

The biggest problem is that NIS installs a large number of peices into

various files and folders throughout your system. Symantec doesn't seem to
be able to find where these are. Furthermore, Symantec's instructions
aren't always possible to follow. (I wonder if anyone at Symantec has ever
actually seen an XP system!!!)