04-04-2009 11:29 AM - edited 04-04-2009 11:31 AM
Please read my post before you respond.........forums don't count.................In the real world, most users haven't a clue about forums like this.
how about an announcement on the symantec home page or an email?
You certainly know how to find our email addresses when it is subscription renewal time.
04-04-2009 12:27 PM
mangurian wrote:Please read my post before you respond [ ...
Why should I bother if all you can do is be rude?
<< You certainly know how to find our email addresses when it is subscription renewal time. >>
You seem to be under the illusion that I am Symantec if you say that. Stick around a while and when you know how this place works and learn some manners perhaps I'll pay more attention.
04-04-2009 12:36 PM
04-04-2009 02:14 PM
huwyngr wrote: ..............
"As for the reluctance to stand up and say "We screwed up" I don't expect this in the menu display problem until they know that they did"
Quote from page 3, 4 down.............
" i did a new vista install on a 2nd hdd with nothing on it but vista ultimate fully updated,
then i installed nis 09, it was ok until nis updated"
----------
"since the update, users may have context menu problems. We are looking into this to see if it's Symantec caused, or outside our control."
Remember the people posting here are paying customers, and must be just the tip of the iceburg.
There are many more out there that have no idea that the update caused (or triggered) the problem.
I thought it was one of three other new progs I'd just installed,
it was only when I back tracked that I worked out it was the NIS update to be the problem.
I was lucky, I had an image of Vista to fall back on, and some free time.
04-04-2009 02:43 PM
04-04-2009 04:40 PM
I was wondering does this problem affect Norton 360 and NAV 2009 or is it only NIS 2009.
04-04-2009 04:50 PM
04-04-2009 06:49 PM
04-04-2009 11:34 PM
04-07-2009 12:45 AM
Well, Symantec (Mike, specifically) did say that they are aware of the right-click context menu graphical issue...
However, that was almost 2 whole weeks ago. Since then, we have not heard a single peep from him (and Symantec). Were they able to reproduce this problem in-house? If so, is this problem being actively worked on? What sort of priority (in terms of fixing it) does this problem have with their programming team? High priority? Low priority? .. or no priority at all? What did they do about this for the past 2 weeks?
At least update us with the progress once in a while, Symantec. Really, how difficult is that?
