My NIS 2009 appears to be working almost exactly as intended by Symantec. And it has been working this way for perhaps 6 months. Improvements are still needed as mentioned below..
I am using XP SP3.
NIS 2009 performs a lot of tasks, some very brief, other very lengthy. Unfortunately, the user has very little control over what NIS 2009 is going to do, does not necessarily know what NIS 2009 is doing at any given time, and can never be certain in real time when NIS 2009 is actually performing a task, such as a scan or even an update, other than by user intuition and experience. The problem is that when I sit down to use my PC, I want it to be fully operable at peak speeds. I do not want NIS 2009 to preempt my use of the my PC, even for 1 minute. That minute or hour, as the case may be, is never convenient when the PC is being used by the user and slows to be crawl. No body should have to put up with this when a simple notification with options would do the trick.
I asked tech support about 6 months ago to request improvements in their notifications within NIS 2009 to tell the PC user when NIS 2009 is about to perform any task, briefly describe the task, and give the user the option to opt out at that time and reschedule at a later time, which may be in minutes or hours. Additionally, it would be nice for the user to be able to interrupt a scan at any time and continue the scan at a later time. Further, it would be wonderful if NIS 2009 would provide a brief listing of the results of the tasks performed after the task completes so that the user, if interested, knows what has occurred. The previous versions of NIS that I used over numerous years always provided this kind of info. For instance, during updating, the user always knew what NIS was downloading and installing. It seems silly to me that Symantec would drop this type of procedure.
Does anyone know if Symantec is doing anything about the issue I have raised?
Another thing, "Ccsvchst" has failed to close normally on many occasions. Someone said to turn "anti-phishing" off. I did and the problem appears to be solved. Is Symantec providing a fix for this annoyance?
Thanks for any help or knowledge anyone can provide to help overcome the above deficiencies.