HeyBub said:
You didn't install it properly is my guess. Google "Norton+resource+hog"
yields 226,000 hits.
Someone is going to have to contact Symantec then and let them know that the
product isn't hammering the CPU after their product is installed. I'll
guarantee that I installed it ptoperly and I won't be the one contacting them
since I have no problems using their products and my systems run just fine with
or without any of their products.
226,000 hits means nothing to me, you'll find my posts along with others who
have no issues with Symantec products, those that have or had issues who voice
out, and those that are followers who voice only on what they've read/heard
without ever using the product. Again, no matter the program/application, the
users mileage will vary due to the way their machine is setup, configured and/or
kept in a clean state (both system/OS wise and machine/hardware/software gunk
wise).
Symantec is not the only application developer in the world and they are most
certainly not the major cause of the many OS failures.
It IS a secret. It's not mentioned in their documentation nor is it part of
the normal uninstall process. Further, running it once is often insufficient.
Further-further FINDING it on Symantec's website is non-trivial.
I'll look into that since I haven't read one of their manuals since back when.
Either way manual or not, if an error did occur and I know they do, no matter
the application including other than Symantec, an error code number would be
generated which could be looked up for a possible solution. FWI, their removal
utility has been in circulation for at least the last 5-7 years.
We write software for a living and Norton has to be disabled before our
software will install properly (because we're adding things to the registry).
This is not true for AVG, Avast, and several other AV programs with which
we've experimented. Moreover, when Norton DOES interfere, it gives no
indication that it did so. The only clue we get is when our customers can't
run our product.
Then the code you write has anomalies of something on the dark side. I'm not
saying any malicious code is being written, yet I'd rather have an app that tags
code as a possible security risk and/or not tag it at all. If you don't see a
popup message that something was blocked as being potentially dangerous, then
it's truly obvious of who hadn't installed the Symantec application properly.
--
Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/
Suggested posting do's/don'ts:
http://www.dts-l.org/goodpost.htm
How to ask a question:
http://support.microsoft.com/kb/555375