Same problem here too with NIS 2003. Would be nice if Norton would fix this!!!
Quietleaf: Thanks SO MUCH for the post on how to revert back to an earlier set of virus defs!!! Before finding this forum I had uninstalled and reinstalled NIS in an attempt to fix this problem so I'd lost ALL previous virus definition folders ;-( But luckily I had a "20100505.004" folder on another machine and so was able to copy that folder over and revert back to the 5/5/2010 definitions. Thanks for saving me from spending even more wasted hours on this today!!!
Very useful discussion. I am also having these problems with NIS Professional 2002. I eagerly await a solution from Symantec. Does anyone have an idea how long that might take? Hope it is very soon!
I've been chasing my tail with this problem, exactly as described here, for several days now. ... Hope there is a solution soon. .... Dave, don't let this one slip. Keep us posted and let us know as soon as a fix is available.
Thank you for the update Dave....however, just to make a comment on LanaK's posting....this happens with the NAV/NIS versions even on modern versions of Windows (tested XP)....it doesn't seem to have anything to do with 'memory management in 9x' or anything related to the platform as that post seems to suggest.
Thank you for the update Dave....however, just to make a comment on LanaK's posting....this happens with the NAV/NIS versions even on modern versions of Windows (tested XP)....it doesn't seem to have anything to do with 'memory management in 9x' or anything related to the platform as that post seems to suggest.
The constraints of the older operating systems restricted the design of these older products. It doesn't matter which operating system the products are actually running on, only the minimum system that they were designed to work with.
It sounds like a load to me....a convenient way to move out the old products that dont require activation--so no revenue for Symatec unless we all upgrade to NIS 2010. But I already have active subscriptions to NIS 2007 and 2010. The older rig I have NAV 2003 installed on runs poorly with either of these products, which is why I have had to remove them and use the 2003 product. I know it is not state of the art, but it is MUCH better than nothing. The computer will not be upgraded just so I can use new norton products....but I guarantee Reese and LanaK that neither of my subscriptions will be renewed...I have purchased subscriptions from Symantec every year for the past 8 years but will not do so again. There are plenty of products out there that cater to the consumer and not the other way around. I believe this Norton strategy to increase revenue may actually cost them loyal customers.
You hit it on the head Nortoff...a deliberate action by Symantec? You betcha-thats why the link to fix the error takes us to the NIS 2010 upgrade page! Of course they can say whatever they want and scoff and deny it but we all know. So Reese and LanaK, is this the end of it or are you still "trying" to fix it??? Anybody got any good suggestions for non-norton AV programs?
I fully agree with your comment....due to the clumsiness of NAV 2006/7/8/9.... is why people sticking with 2002/3/4...
Norton - please remove those defective coding and free us from this trouble in your next LiveUpdate.
I am the first generation of I.T. professional since the early early 1980s. I have seen every AntiVirus software in my 30+ years in this industry (folks - remember Central Point AntiVirus??) but nothing like what Norton is doing to the I.T. community like this one!
All you LOOKIE LOOS need to register and sign in and reply to this NORTON "strategy"...there are hundreds of readers of these posts but only a couple dozen posters. It is easy to register and this might be your only chance to voice your opinion about this "incentive" to upgrade that Symantec has implemented. Maybe if enough voice their opinions things might change...Meanwhile, Ill be shopping for a new AV program...and it wont be made by Symantec.
I won't go so far as to say it was something intentional....however, that said....seeing as everything worked fine and then a routine definitions update broke everything, it just doesn't seem like it would be a huge feat of engineering to fix it. We all know what the support policy is. I don't think anyone is suggesting that the company begin offering any kind of support for these older products...but again...is this that difficult of a fix?
It seems to me that most of the folks posting here are either professionals who are using this software on older systems for a specific reason...or they are people who simply choose to use the older software. Either way, I doubt either of these folks will be persuaded by this to upgrade to the newest versions. They either can't due to old hardware, or just don't want to.
Again, I'm assuming based on what I said above that this would not be a huge fix. It just seems to me that it would be the right thing to do from a customer service and customer retention standpoint. I doubt Symantec will gain many customers by upgrading from these versions, but I see how they could lose customers (and in the case of the IT pros here, lose recommendations).
Just my two cents. And thank you to the Symantec employees who have taken the time to research this and give us some information.
Sorry, I have to call BS here. Starting May 11, NAV 2003 is throwing an exception on my box from an attempt to read a null pointer (and I'm a coder, I know what that means). My box is a dual-core laptop running 2k Pro, with 4G RAM. I was born at night, but not LAST night. Your software is accessing a null pointer somewhere. That's bad, period.
I agree with NORTOFF. ... Many, other than those who post, are reading this. And, you can bet your bottom dollar that they came here looking for a fix to the current problem. ... I'm sitting here looking at something I got today, NAV 2010. ... Will it get installed? ... Not until this problem is addressed appropriately with a fix, and customers are once again happy. .... We are expecting a resolution to this problem as soon as possible. .... If I don't see a post from a Symantec employee saying, "we are working on a fix" posted soon, I will be sending NAV 2010 back and looking elsewhere for security.
Seeing the post above, with the comment "I'm sitting here looking at something I got today, NAV 2010"
If you have 2010, you have no problem, then also it means your OS is new enough.
It's people with 9x ME etc as an operating system that will for one have fun trying to find a good enough AV or any AV for that matter that supports the older OS's, as even free AV's have stopped or starting to stop the likes of 98 compatibility.