Wild

Microsoft supply XP OS as OEM on the basis that the vendor fully supports
it.. if the vendor does not, then why is that the responsibility of
Microsoft?.. the major name manufacturers and vendors commission
motherboards that are slightly off standard specification, a kind of company
signature.. they then add whatever to the OEM installation to make it work..
why is that the responsibility of Microsoft?

It seems to me that you could probably be using older programs that are
borderline in XP.. do you think that Microsoft are responsible for what you
choose to run?.. have you considered questioning the program authors re.
fixes such that the programs might work in XP SP2?..

Microsoft do their best to provide a stable and safe OS in the interests of
computing generally.. third party software authors are acutely aware of the
problems, yet in some cases choose to do NOTHING re. compatibility with the
latest and safest OS.. well, actually they do.. they produce new versions
for which they demand large amounts of money.. and this is the
responsibility of Microsoft?

--
Mike Hall
MVP - Windows Shell/user

http://dts-l.org/goodpost.htm





"Wildepad" wrote in message
...
On Sun, 13 Mar 2005 21:10:25 -0500, "Mike Hall \(MS-MVP\)"
wrote:

Wild

I saw your retraction post to Ron J.. your original remark was just
unfortunately placed..

Um, quibble, but it wasn't a retraction -- it was a clarification. If
you had looked at the attributes, you would have seen that there was a
regrettable misperception on Ron J's part.


Re. HP and SP2, Dell and Compaq also had issues with SP2 that required
patches from both manufacturers.. I really don't know what they do to an
OEM
install or any hardware that would require 'fixing' (shakes head)..

Oh? You mean that everything MS puts out never needs a fix?

I wish you well, and hope that HP can get their act together for you..

It's on MS's end to produce something that can cross-platform.

I find it perversely amusing that when talking to someone else about
this, they mentioned that they've been unable to e-mail MS about their
own problems with SP2 because their .NET passport, which MS requires,
failed, just as mine did, leaving us out in the cold.