Ward in Houston said:
Let me see...how about to make sure that something Microsoft updates
or changes doesn't keep the 3rd Party from operating correctly? How
is Symantec going to test something before you release it?
I'm fairly confident that Microsoft partners get prerelease notification and
access to the software so they can mave their changes in place when the
product is released. I don't know who "you" refers to in the above, but I'm
not Microsoft and I don't work for them, either.
With the
importance of interent security wouldn't it make sense to include the
most popular security providers in your testing?
Nope. It's still the responsibility of the people who sell a product that
purports to work with another to test before they sell. Symantec is
notorious for producing products that don't quite do the jobs claimed for
them.
Especial since
their software is bundled with your software?
If you get Symantec products bundled with Microsoft products, it has nothing
to do with Microsoft. It has everything to do with the PC manufacturer.
They're the ones bundling, not Microsoft.
What type of
verification testing do you do today? Seems like Alpha and Beta are
treated as obsolete thinking today. Where's the proof of reliability?
Ask Microsoft these questions.
Ever wonder what the reaction would be if Microsoft ever relased an
update or change and no one noticed?
What would the point of that be? A difference that makes no difference IS
no difference.
Then perhaps someone notices
that those annoying error messages stopped showing up or performance
seemed to greatly improve. How cool would it be to impliment an
upgrade and not receive any complaints?
Human nature being what it is, this will never happen. Even if everything
worked properly, _someone_ would complain.
That's why you test for ALL
obvious potential problems and as many not so obious or down right
ridiculous problems that you can think of because believe me, users
will think of several that you had no idea could or would pop up.
One tests ALL that one can control and one vendor has no control over
products of the other.
I may be mistaken, but didn't you offer the fix in another thread that
unchecking the option in Norton to monitor Outlook, close and reboot
Norton, then recheck the box and reboot again would fix this? I
tried that and it didn't work!
I think the biggest problem in all of this is the assumption that if you
install a major piece of software like Office that the products that
integrated with the prior version will still work. That's plain naive.
When one upgrades a PC, one waits until one has commitments from the various
vendors that all the apps will play together before making any changes - at
least, if one values ones data, of course.