
I may be wrong, but this is the biggest response, in so short a period of time, as I have seen on these Boards. Also, many new faces have joined us to express their displeasure. Surely, that is a plus item to come out of an error on Norton's part.
Many posts have complained that Norton didn't test sufficiently, or at all, before releasing this patch to a limited number of clients. Everyone appears to be assuming that anyone using Firefox will have a problem and maybe this is, or is not, true. However, before we jump to conclusions, we should also assume that Norton test their new patches against a standard range of possibilities and this was done in this case. This time Firefox produced an unexpected response. Our answer is fix it quick and send out the result. If Norton do this, is this not exactly what we are now complaining about? A quick fix, which has not been thoroughly tested.
Please give the Norton team time to allow them to test comprehensively, the whole issue and to release the result when they are confident that all is well. Predicting when that will be is for gamblers and should be no part of the solution. On the other hand, as soon as the solution is available, I am sure, as we all should be, that Norton will very promptly let us know and the patch will be made available.
A temporary remedy has been suggested in earlier postings, so no one should have to continue with this problem, but will be able to revert to version 17.0.0.136, whilst waiting for the improved patch.
My own suggestion for a temporary fix, which I haven't tried, because I'm using IE version 8 with Windows 7 version 7100 and NIS 2010, is to go to an earlier restore Point. Perhaps someone who has tried this can tell us if it does help.
I think those of us who have been involved in testing NIS beta versions will agree that the Norton team are 100% dedicated to producing the best product available anywhere and fixing even minor issues, which this present issue obviously is not, as quickly and as effectively as is humanly possible. That this problem was not seen during their testing is a very unhappy event for all those on the Norton team and a blow to their prestige which, I am sure, they will try very try very hard to avoid in the future. We all know how difficult it is to continuously get things 100% right, especially when dealing with software, and, when a glitch appears, I think it is a little unfair for us to complain that we don't wish to be Beta testers etc. We haven't seen our security compromised; we've seen a loss of some facilities which we were enjoying. We have a way to restore these temporarily and I hope that we can be patient, knowing that the team are working day and night to come back with the perfect solution for us.
drshlomo.