Bulldoggy wrote:So mijcar, you were there in the room with the Symantec developers, and you heard them say "Should we bother testing this patch? Nah - let's just release it anyway."
Boo-hoo-hoo.
This is not the kind of forum for that kind of sarcasm.
We help each other here.
If you have something to contribute, it would be great.
I've been volunteering my time for over a year. I have actually helped people. Perhaps you can join us in that?
Hello, is uninstall a reinstall a good idea? If so, anyody has a link to download NIS 2010? Thanks!
Bulldoggy wrote:So mijcar, you were there in the room with the Symantec developers, and you heard them say "Should we bother testing this patch? Nah - let's just release it anyway."
Boo-hoo-hoo.
I will respond to the content, but not the poster. This is for the other people here:
I have little doubt of what has happened. In another thread, there was constant beratement of the Symantec engineers for failing to deliver a solution to a certain kind of error message, one that has been besetting users for over a year. Likewise, there was also the equivalent of a cosmetic error when users tried to run msconfig.
It seems that the engineers put a lot of attention into resolving both those issues. I bet they believed that the code they modified and added only had impact within those two areas. Because they were responsive to user's needs, they rushed through the testing, noted that the issues were resolved, and sent the patch through.
Too soon.
It's understandable. So many people yelling at them to get the job done!
But it was wrong. The nature of the bug was not that it was hidden or unobvious. It was a blatent bug and would have been immediately evident to even a casual check. Does NIS continue still integrate with Firefox. All that was necessary to detect this bug was to launch Firefox and look at the screen and see if the Norton Toolbar appeared. It doesn't.
This kind of error in judgment is worth noting. Everyone is entitled to mistakes, but some mistakes are ... well ... more embarrassing than others. And you can bet that the Symantec team are pretty durn embarrassed.
As for the people affected by this mistake, they have the right to complain. It is easy for people to whom the mistake has no real impact to sneer at those for whom the mistake causes problems. In general, I try to ignore such people: they contribute nothing but discord. Sneering is a sign of emotional problems; I won't let it become a problem of my own.
Not sure it's that sort of problem really. I checked after this morning's update and I still have my Norton Toolbar in MSIE 8 but not in Firefox. Odd really as I cannot uninstall it from Firefox either. But but works in MSIE so........ I guess it works then, if only partially.
Lots of stuff going on lately, Install of Windows 7 ( Love it!) Now updated NIS and an updated Firefox. 3.5.4. So all this in a few days I think we should give the Norton team a little time to sort through all this. I doubt that everyone knows when some other company is going to release an update or a customer is going to install a new OS for that matter.
As always giv e them some time and it shall be resolved, if the past is any indication.
I haven't updated my laptop as yet so that should still be working as before. Time will tell.
chatham
pamaf2003 wrote:
Hello, is uninstall a reinstall a good idea? If so, anyody has a link to download NIS 2010? Thanks!
As related to this problem, the answer is probably "yes."
If the issue is really bothering you. Since Symantec has put the patch-delivery on hold, reinstalling would not get the patch again until it was fixed.
On the other hand, uninstalling/reinstalling always has the potential to introduce a new error (shudder!), so I would have to be sure in my own mind that the nature of the current problem outweighed the potential of a new one. Sigh. 
i think i found the Error . after this 17.1 Patch we have a Driverproblem with NIS2010 .
Open your Devicemanager , show non-PnP-Driver in the Devicemanager .
You all found now a yellow marked not working SymDS (Symantec Datastore) Driver.
“Dear Norton Community,
We are glad to announce that we have completed testing our first inline release of Norton AntiVirus 2010 and Norton Internet Security 2010 and we are ready to release the patch.” [The emphasis is mine.]
http://community.norton.com/norton/board/message?board.id=nis_feedback&thread.id=83394
So, not only are you accusing Symantec of not testing their patch - based on nothing more than your imagination - now you’re accusing Tim of lying!
Here’s what happened: Symantec screwed up, big time, which is something that humans sometimes do in spite of all their efforts and intentions. They accepted responsibility for their mistake, and they’re working to fix it.
I’d like to see you do that.
Voyager10 wrote:i think i found the Error . after this 17.1 Patch we have a Driverproblem with NIS2010 .
Open your Devicemanager , show non-PnP-Driver in the Devicemanager .
You all found now a yellow marked not working SymDS (Symantec Datastore) Driver.
I tried that, but all my non-PnP Drivers are functional, including all of the Symantec drivers, and in particular including the Symantec Datastore Driver.
Perhaps in trying to fix the problem yourself, you might have disabled that driver? Or perhaps there is a problem with the driver, but it isn't showing up in my XP3 system?
We'll see if the Symantec engineers note this post and use it somehow.
Moved to existing thread for better exposure
For the time being until there is a better solution I have ran NRT once, Installed NIS10 and ran live update (same patch) and the toolbar is back.
Uninstalled and reinstalled and finally back to normal…
pamaf2003 wrote:
Uninstalled and reinstalled and finally back to normal....
Good to hear. Thanks for the report.
By the way, what is showing as your NIS version now?
transient wrote:
For the time being until there is a better solution I have ran NRT once, Installed NIS10 and ran live update (same patch) and the toolbar is back.
So what is the exact version of NIS now being reported?
Sounds like something worth trying; perhaps Symantec fixed the patch.
17.0.0.136
For those with Firefox and had their extensions hosed by the NIS update:
Delete the files "xpti.dat" "compreg.dat" "extensions.ini" "extensions.cache" and "extensions.rdf" from your Firefox profile folder.
This got me back in business. A couple of extensions still showed as incompatible and I had to unistall and re-install them.
The only one left disabled and not compatible is Norton Toolbar (of course)
russws wrote:For those with Firefox and had their extensions hosed by the NIS update:
Delete the files "xpti.dat" "compreg.dat" "extensions.ini" "extensions.cache" and "extensions.rdf" from your Firefox profile folder.
This got me back in business. A couple of extensions still showed as incompatible and I had to unistall and re-install them.
The only one left disabled and not compatible is Norton Toolbar (of course)
That sounds a little too drastic, russws. Most of us got Firefox back to normal simply by disabling the two Norton Add-ons. Did you try that first?
pamaf2003 wrote:
17.0.0.136
Same here
mijcar wrote:
That sounds a little too drastic, russws. Most of us got Firefox back to normal simply by disabling the two Norton Add-ons. Did you try that first?
No, I fixed it before I found this thread. It's really not that 'drastic', it is a standard procedure when extensions fail. It normally does not require extensions to be re-installed, those deleted files are re-created automatically
http://kb.mozillazine.org/Standard_diagnostic_-_Firefox
However, next time it happens, I'll disable Norton first.....
russws wrote:... I fixed it before I found this thread. It's really not that 'drastic', it is a standard procedure when extensions fail. It normally does not require extensions to be re-installed, those deleted files are re-created automatically
http://kb.mozillazine.org/Standard_diagnostic_-_Firefox
Thanks for the info. I'm still a Firefox novice and enjoy learning all these things.
transient wrote:
pamaf2003 wrote:
17.0.0.136Same here
Okay, so that returns you to the previous build.
For the moment I am going to wait and see if the next patch fixes the current one. I am imagine that is something Symantec will need to know both for this situation and potential future ones. I can live without the FF integration. For now.
Thanks, again, for the info.