-----Original Message-----
As long as you think "ALL of these problems have a single
source", you
will probably never see the whole picture.
No one said the fault is exclusively the 3rd party
application.
But it is also not exclusively Microsoft's.

People have been demanding more secure and better written
code of
Microsoft, well now it came.
Do you also go to the 3rd party manufacturers that have
problems and
demand the same from them?
If not why not?
Is your solution to break Windows XP and make all other
applications
work at all costs?

The manufacturers have had many months to see if they had
a problem.
Some worked it out and had information available for
their customers
when needed.
Others snubbed their customers, blaming Microsoft
ignoring the fact
they could have been working the issue and have a
solution or at least
near a solution at this time..
And still others no longer exist.

Microsoft and others listed applications known to have
issues to help
the customers have better information.

If we are to have secure computing, it is going to take
great effort
amongst the development community, not just Microsoft.
The users will also have to learn safe computing
practices.
If you expect Microsoft to accomplish secure computing
alone, prepare
for very unsafe computing.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/



As usual, you're completely avoiding the issue. Microsoft
has NEVER been concerned about secure computing until
things blow up. Remember--it was your "poorly written
code" statement in which you tried to shift blame to
developers who had commited the heinous crime of writing
programs that work on the target platform using the
specifications and architectuire they were given to work
with. You still haven't explained how it is that all of
this code was written to take advantage
of "vulnerabilities" in XP without Microsoft knowing about
the vulnerabilities, and without Microsoft closing the
holes before the miscreants could crawl through them.