For shame, For shame...
I've read all the posts concerning this problem not because it amuses me, but because I have to. I am in the same boat having both NSW2006 and NAV2009 om my system.
I have been running Norton products for years and years before Symantec had anything to do with them. I've come to trust Norton even though I've heard many tell me how intrusive Symantec products are or how they've slowed or corrupted their systems. I never had such a problem. I would expect an antivirus package to have deep roots into the OS in order to hook into every possible threat it can.
So when I received popup offer from Symantec to upgrade to NAV2009 as part of my existing subscription I did so - of course. Why shouldn't I ? Little did I know that I was entering a known trap by the very people I trust with my livelihood.
You see, I am "mature", self-employed software developer. My machine IS my company in that if dies I am out of work until I come up with, reload and configure another machine. That's no small feat considering I have over 500 mods for more than a dozen versions of a product containing 2.5 million lines of code. Being a developer I really don't understand why Symantec would allow such a situation to arise. Pushing NAV2009 out to installed sites isn't so bad. It's rather nice they offer their latest version as part of their subscription. However, allowing the NAV2009 installation to continue when it could easily detect that NSW is already installed is inexcusable. There is no way they can convince me they didn't know the products were incompatible and couldn't add 20 lines of code to prevent this problem and redirect the user to a web page that explains the problem.
Their solution is to upgrade then patch the upgrade. Here's an analogy. You drive your car into the dealership for an oil change. On the way out the Service Writer offers you a free can of oil treatment. You accept it gratefully and allow him to pour it in. Immediately the engine starts to run like crap and you look at him and say "What the @#$%". His reply ? "Oh ! You have the six cylinder. That oil treatment really buggers those things up. Too bad. Well you need to upgrade to an eight cylinder to fix that. Then after we put in the new engine we'll have to change the oil pump as well." Who would accept that answer ? Yet that's the situation.
Look. NSW is certainly cheaper than an engine, but it's the attitude that bugs me. Symantec knew installing NAV2009 on top of ANY existing version of NSW would cause problems and let it go out anyway. No, not "let it go out" they pushed it out via automatic popups. It's inexcusable !
Being a developer I know it's hard to code a product to integrate with other products that haven't been developed yet. But that's not what I'm talking about. I can certainly write an installation to look for, identify and handle older products even if handling the situation means aborting the installation completely. I have no special powers that a big company like Symantec doesn't also have. And their solution is laughable. Their patch removes the ability run LU from NSW. That's akin to removing your power window switch because your window is squeaky.
Reading these posts it sounds like they're trying to build a wall between NSW and NAV like they are completely separate products. Obviously that's not true or installing NAV2009 wouldn't affect NSW at all. NAV used to be part of NSW. And don't even get me going with that paraphraset "NSW is so good you don't even need updates". I'm a coder. I know better ! Nothing... Nothing goes out the door perfect every version. If I hear a coder telling me his software never needs any updating I think "liar" or "arrogant". I guess if you write your software so it dies each time you install an annually updated product you really can say your software doesn't require "updates". It requires "replacement" every year.
I wish my only problem was a silly little red "X" on my System Tray. Ever since I installed NAV2009 on top of NSW2006 it's a 50/50 crap-shoot if my machine will boot up on the first try. Typically NSW and NAV get into a fight and reboots my machine during boot-up. So I'm not real impressed anymore. Their solution ? Uninstall NSW2006, install a time-limited NSW2008, install a patch (and watch some functionality disappear) then pay for NSW2008 when the demo period ends. That's great ! Or I guess uninstall NAV2009 and reinstall an older NAV and deal with any issues that arise with that. Regardless it will take time and money.
So I'll go buy NSW2008 (on sale somewhere), install it, run LiveUpdate and install the patch. I'll continue using Norton, but I'll be very, very wary of any updates in the future. And I'll no longer have the luxury of being able to tell my cohorts that I've never had a problem with Norton like they have.
Have a great day everyone !
Ed, the grumpy dinosaur coder