SP3 and HP/AMD Computers

Check your inbox.

TaurArian wrote:
> And where have you been the last 2 days????????
>
>> We shall alert the media.
>>
>> sasha gottfried wrote:
>>> As I mentioned........I have chosen not to install SP3
>>>
>>> "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
>>> news:OC9I%23WGwIHA.576@TK2MSFTNGP05.phx.gbl...
>>>> Continual reboots or can only boot into Safe Mode after installing
>>>> WinXP
>>>> SP3?
>>>>
>>>> See
>>>> http://msinfluentials.com/blogs/jesp...ng-xp-sp3.aspx
>>>> [NB: The above has been updated many times and now includes "a small
>>>> tool
>>>> that will detect the IntelPPM problem and mitigate it before installing
>>>> (WinXP SP3)."]
>>>>
>>>> Some other possible workarounds:
>>>>
>>>> • Boot into Safe Mode and rename INTELPMM.SYS to INTELPMM.OLD.
>>>>
>>>> • After booting into Safe Mode:
>>>>
>>>> Start | Run | (copy/paste) sc config intelppm start= disabled | OK |
>>>> Reboot into normal (Windows) mode.
>>>>
>>>> Other references:
>>>>
>>>> • http://aumha.net/viewtopic.php?p=187790#p187790
>>>>
>>>> •
>>>> http://www.theregister.co.uk/2008/05...boots_crashes/
>>>>
>>>> •
>>>> http://www.computerworld.com/action/...leId=9084 418
>>>>
>>>> • You receive a “Stop 0x0000007E” error message after you upgrade to
>>>> Windows XP Service Pack 2 or Service Pack 3 on a
>>>> non-Intel-processor-based
>>>> computer (Revised 06 May-08)
>>>> http://support.microsoft.com/kb/888372
>>>>
>>>> • Unsupported Sysprep scenarios:
>>>> http://support.microsoft.com/kb/828287
>>>>
>>>> • HP and Compaq Desktop PCs: Computer Restarts after Displaying Stop
>>>> Error
>>>> 0x0000007E [after installing WinXP SP3]
>>>> http://h10025.www1.hp.com/ewfrf/wc/g...&lc=en&cc= us
>>>>
>>>> • Microsoft Windows XP SP3 Upgrade Utility for systems with AMD
>>>> processors
>>>> http://h10025.www1.hp.com/ewfrf/wc/g...reg_R1002_USEN
>>>> --
>>>> ~Robear Dyer (PA Bear)
>>>> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
>>>> AumHa VSOP & Admin http://aumha.net
>>>> DTS-L http://dts-l.net/
>>>>
>>>> sasha gottfried wrote:
>>>>> I've recently learned, via this newsgroup, that SP3 will cause
>>>>> incessant
>>>>> boot problems when installed in an HP computer with an AMD processor.
>>>>> I
>>>>> see
>>>>> that there is a patch for this via the HP website. Of course, one
>>>>> wonders
>>>>> how to install a patch on a computer that just keeps rebooting? Why
>>>>> didn't
>>>>> Microsoft figure this problem out before releasing the update? There
>>>>> must
>>>>> be
>>>>> thousands of HP computers with AMD processors! Why didn't HP send out
>>>>> a
>>>>> special alert to customers with AMD processors?
>>>>>
>>>>> These are the kinds of issues that infuriate customers, and lead to
>>>>> all
>>>>> kinds of lawsuits. Thankfully, I read through this newsgroup and
>>>>> avoided
>>>>> messing with this SP3 debacle for now. I am grateful to the
>>>>> contributors
>>>>> to
>>>>> this discussion who have saved me the headache of indulging in another
>>>>> irresponsible, reckless, corporate abuse of its customers. Please
>>>>> correct
>>>>> any misapprehensions I have expressed here about this. But it would
>>>>> appear
>>>>> that, once again, the home computer industry is inducing unneeded
>>>>> stress,
>>>>> and sacrificing the time of its end-users, for the public relations
>>>>> illusion
>>>>> of 'upgrading' our experience and enhancing our 'security.'
>>>>>
>>>>> MT

Put the shoe on the other foot: Beta testing of WinXP SP3 started over a
year ago. Are you telling me that OEMs weren't aware of it and didn't test
it on their machines running WinXP SP2?

We saw nearly identical behavior on machines were Sysprep was used when SP2
was released. Are you telling me that OEMs don't learn from history?
--
~PA Bear

sasha gottfried wrote:
> Doesn't Microsoft confer with major computer manufacturers before putting
> out a major OS upgrade? As you say, HP manufactures many AMD based
> computers. Are you telling me Microsoft isn't aware of this, or doesn't
> bother testing their SP3 on such systems using this 'image' applied? You'd
> think that between HP and Microsoft they would 'expose' the mistake before
> allowing it to be foisted on customers. But hell, our time is not THEIR
> money, is it?
>
> MT
>
>
> "Shenan Stanley" <newshelper@gmail.com> wrote in message
> news:%23idGSaIwIHA.3564@TK2MSFTNGP03.phx.gbl...
>> sasha gottfried wrote:
>>> I've recently learned, via this newsgroup, that SP3 will cause
>>> incessant boot problems when installed in an HP computer with an
>>> AMD processor. I see that there is a patch for this via the HP
>>> website. Of course, one wonders how to install a patch on a
>>> computer that just keeps rebooting? Why didn't Microsoft figure
>>> this problem out before releasing the update? There must be
>>> thousands of HP computers with AMD processors! Why didn't HP send
>>> out a special alert to customers with AMD processors?
>>> These are the kinds of issues that infuriate customers, and lead to
>>> all kinds of lawsuits. Thankfully, I read through this newsgroup
>>> and avoided messing with this SP3 debacle for now. I am grateful to
>>> the contributors to this discussion who have saved me the headache
>>> of indulging in another irresponsible, reckless, corporate abuse of
>>> its customers. Please correct any misapprehensions I have expressed
>>> here about this. But it would appear that, once again, the home
>>> computer industry is inducing unneeded stress, and sacrificing the
>>> time of its end-users, for the public relations illusion of 'upgrading'
>>> our experience and enhancing our 'security.'
>>
>> The problem was not *any* computer with an AMD processor or any HP system
>> with an AMD processor - but those computers (any OEM) that had an 'image'
>> applied to it that was created and intended for a computer with an Intel
>> processor. Some of the HP computers were done this way - thus the reboot
>> situation in many of the cases - and HP is a large distributor/pusher of
>> AMD systems...
>>
>> In other words - it was not something that could have been known
>> beforehand by Microsoft. Your accusations should fly towards the OEM
>> that
>> decided to make a single installation image and apply it to all
>> machines -
>> AMD and Intel alike... SP3 just 'exposed' the mistake of applying such
>> an
>> image (one based on Intel procesors) onto such a machine (an AMD
>> processor
>> based machine) without fixing it afterwards...
>>
>> --
>> Shenan Stanley
>> MS-MVP
>> --
>> How To Ask Questions The Smart Way
>> http://www.catb.org/~esr/faqs/smart-questions.html

sasha gottfried wrote:
> Doesn't Microsoft confer with major computer manufacturers before
> putting out a major OS upgrade? As you say, HP manufactures many
> AMD based computers. Are you telling me Microsoft isn't aware of
> this, or doesn't bother testing their SP3 on such systems using
> this 'image' applied? You'd think that between HP and Microsoft
> they would 'expose' the mistake before allowing it to be foisted on
> customers. But hell, our time is not THEIR money, is it?

The OEMs pay less to Microsoft for the licenses of Windows XP (OEM License
agreements) so they can make more profit selling to the end-consumer and for
that they provide the end-consumer support for the machine - including the
installed OS. That is a choice they made.

Given that choice and the fact that SP3 has been available in some form
(beta and otherwise) to the OEMs for over a year - they should have taken
the responsibility and tested it. Not to mention - any OEM that decided an
AMD processor was the same as an Intel processor (thus making one image)
likely should have thought that out better. I am having trouble seeing it
from your point of view that Microsoft (SP3) is to blame when it was not
Microsoft that made the image being used by said OEMs nor were they the ones
responsible for testing things on the OEMs own equipment.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Don't tell me Microsoft wasn't aware of this! Or was it just a set-up to
blame the OEM's? Either way.......the customer loses!


"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
> sasha gottfried wrote:
>> Doesn't Microsoft confer with major computer manufacturers before
>> putting out a major OS upgrade? As you say, HP manufactures many
>> AMD based computers. Are you telling me Microsoft isn't aware of
>> this, or doesn't bother testing their SP3 on such systems using
>> this 'image' applied? You'd think that between HP and Microsoft
>> they would 'expose' the mistake before allowing it to be foisted on
>> customers. But hell, our time is not THEIR money, is it?
>
> The OEMs pay less to Microsoft for the licenses of Windows XP (OEM License
> agreements) so they can make more profit selling to the end-consumer and
> for that they provide the end-consumer support for the machine - including
> the installed OS. That is a choice they made.
>
> Given that choice and the fact that SP3 has been available in some form
> (beta and otherwise) to the OEMs for over a year - they should have taken
> the responsibility and tested it. Not to mention - any OEM that decided
> an AMD processor was the same as an Intel processor (thus making one
> image) likely should have thought that out better. I am having trouble
> seeing it from your point of view that Microsoft (SP3) is to blame when it
> was not Microsoft that made the image being used by said OEMs nor were
> they the ones responsible for testing things on the OEMs own equipment.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>

sasha gottfried wrote:
> Don't tell me Microsoft wasn't aware of this! Or was it just a
> set-up to blame the OEM's? Either way.......the customer loses!

Why would Microsoft be aware that __some__ OEMs decided to make a single
disk image on an Intel processor machine and apply it to all of the machines
that they sold (intel and AMD based)?

Please explain the connection to me. I truly do not understand how you are
making that connection.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

I agree that the customer loses, sasha. BUT, HP has been well aware of
Unsupported Sysprep Scenarios for quite some time now:
http://support.microsoft.com/kb/828287

Read the ' Different processor vendors ' section.
There is definitely something amiss with how MS tests updates|SPs and
with their lack of communication skills.

However, this issue is directly attributable to HP, plain and simple.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============




sasha gottfried wrote:

> Don't tell me Microsoft wasn't aware of this! Or was it just a set-up to
> blame the OEM's? Either way.......the customer loses!
>
>
> "Shenan Stanley" <newshelper@gmail.com> wrote in message
> news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
>
>>sasha gottfried wrote:
>>
>>>Doesn't Microsoft confer with major computer manufacturers before
>>>putting out a major OS upgrade? As you say, HP manufactures many
>>>AMD based computers. Are you telling me Microsoft isn't aware of
>>>this, or doesn't bother testing their SP3 on such systems using
>>>this 'image' applied? You'd think that between HP and Microsoft
>>>they would 'expose' the mistake before allowing it to be foisted on
>>>customers. But hell, our time is not THEIR money, is it?
>>
>>The OEMs pay less to Microsoft for the licenses of Windows XP (OEM License
>>agreements) so they can make more profit selling to the end-consumer and
>>for that they provide the end-consumer support for the machine - including
>>the installed OS. That is a choice they made.
>>
>>Given that choice and the fact that SP3 has been available in some form
>>(beta and otherwise) to the OEMs for over a year - they should have taken
>>the responsibility and tested it. Not to mention - any OEM that decided
>>an AMD processor was the same as an Intel processor (thus making one
>>image) likely should have thought that out better. I am having trouble
>>seeing it from your point of view that Microsoft (SP3) is to blame when it
>>was not Microsoft that made the image being used by said OEMs nor were
>>they the ones responsible for testing things on the OEMs own equipment.
>>
>>--
>>Shenan Stanley
>> MS-MVP
>>--
>>How To Ask Questions The Smart Way
>>http://www.catb.org/~esr/faqs/smart-questions.html
>>
>
>
>

The blame game can go on and on. The arrogance, and lack of communication
between these mega-bux, computer comrades is criminal. Who expects John Q
Customer to know what the hell "Sysrep Scenarios" are anyway!

Pathetic!

But thanks to this newsgroup for the heads up on these corporate clowns.

MT



"MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
news:OFCUI$PwIHA.548@TK2MSFTNGP06.phx.gbl...
>I agree that the customer loses, sasha. BUT, HP has been well aware of
>Unsupported Sysprep Scenarios for quite some time now:
> http://support.microsoft.com/kb/828287
>
> Read the ' Different processor vendors ' section.
> There is definitely something amiss with how MS tests updates|SPs and with
> their lack of communication skills.
>
> However, this issue is directly attributable to HP, plain and simple.
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
>
> sasha gottfried wrote:
>
>> Don't tell me Microsoft wasn't aware of this! Or was it just a set-up to
>> blame the OEM's? Either way.......the customer loses!
>>
>>
>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>> news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
>>
>>>sasha gottfried wrote:
>>>
>>>>Doesn't Microsoft confer with major computer manufacturers before
>>>>putting out a major OS upgrade? As you say, HP manufactures many
>>>>AMD based computers. Are you telling me Microsoft isn't aware of
>>>>this, or doesn't bother testing their SP3 on such systems using
>>>>this 'image' applied? You'd think that between HP and Microsoft
>>>>they would 'expose' the mistake before allowing it to be foisted on
>>>>customers. But hell, our time is not THEIR money, is it?
>>>
>>>The OEMs pay less to Microsoft for the licenses of Windows XP (OEM
>>>License agreements) so they can make more profit selling to the
>>>end-consumer and for that they provide the end-consumer support for the
>>>machine - including the installed OS. That is a choice they made.
>>>
>>>Given that choice and the fact that SP3 has been available in some form
>>>(beta and otherwise) to the OEMs for over a year - they should have taken
>>>the responsibility and tested it. Not to mention - any OEM that decided
>>>an AMD processor was the same as an Intel processor (thus making one
>>>image) likely should have thought that out better. I am having trouble
>>>seeing it from your point of view that Microsoft (SP3) is to blame when
>>>it was not Microsoft that made the image being used by said OEMs nor were
>>>they the ones responsible for testing things on the OEMs own equipment.
>>>
>>>--
>>>Shenan Stanley
>>> MS-MVP
>>>--
>>>How To Ask Questions The Smart Way
>>>http://www.catb.org/~esr/faqs/smart-questions.html
>>>
>>
>>

Get yourself an abacus, Sasha.

sasha gottfried wrote:
> The blame game can go on and on. The arrogance, and lack of communication
> between these mega-bux, computer comrades is criminal. Who expects John Q
> Customer to know what the hell "Sysrep Scenarios" are anyway!
>
> Pathetic!
>
> But thanks to this newsgroup for the heads up on these corporate clowns.
>
> MT
>
>
>
> "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
> news:OFCUI$PwIHA.548@TK2MSFTNGP06.phx.gbl...
>> I agree that the customer loses, sasha. BUT, HP has been well aware of
>> Unsupported Sysprep Scenarios for quite some time now:
>> http://support.microsoft.com/kb/828287
>>
>> Read the ' Different processor vendors ' section.
>> There is definitely something amiss with how MS tests updates|SPs and
>> with
>> their lack of communication skills.
>>
>> However, this issue is directly attributable to HP, plain and simple.
>>
>> MowGreen [MVP 2003-2008]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>>
>> sasha gottfried wrote:
>>
>>> Don't tell me Microsoft wasn't aware of this! Or was it just a set-up to
>>> blame the OEM's? Either way.......the customer loses!
>>>
>>>
>>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>>> news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
>>>
>>>> sasha gottfried wrote:
>>>>
>>>>> Doesn't Microsoft confer with major computer manufacturers before
>>>>> putting out a major OS upgrade? As you say, HP manufactures many
>>>>> AMD based computers. Are you telling me Microsoft isn't aware of
>>>>> this, or doesn't bother testing their SP3 on such systems using
>>>>> this 'image' applied? You'd think that between HP and Microsoft
>>>>> they would 'expose' the mistake before allowing it to be foisted on
>>>>> customers. But hell, our time is not THEIR money, is it?
>>>>
>>>> The OEMs pay less to Microsoft for the licenses of Windows XP (OEM
>>>> License agreements) so they can make more profit selling to the
>>>> end-consumer and for that they provide the end-consumer support for the
>>>> machine - including the installed OS. That is a choice they made.
>>>>
>>>> Given that choice and the fact that SP3 has been available in some form
>>>> (beta and otherwise) to the OEMs for over a year - they should have
>>>> taken
>>>> the responsibility and tested it. Not to mention - any OEM that
>>>> decided
>>>> an AMD processor was the same as an Intel processor (thus making one
>>>> image) likely should have thought that out better. I am having trouble
>>>> seeing it from your point of view that Microsoft (SP3) is to blame when
>>>> it was not Microsoft that made the image being used by said OEMs nor
>>>> were
>>>> they the ones responsible for testing things on the OEMs own equipment.
>>>>
>>>> --
>>>> Shenan Stanley
>>>> MS-MVP
>>>> --
>>>> How To Ask Questions The Smart Way
>>>> http://www.catb.org/~esr/faqs/smart-questions.html

Yo'

I can count...... Frankly, from a customer's standpoint, it doesn't matter
who screwed up here. HP uses Microsoft and Microsoft uses HP. Meanwhile, in
situations like this, they both USE the USER. Who are these prgrammers
anyway? 25 year old hyped up ego-maniacal geeks playing inter-corporate
competetive games with themselves?

Like I say: OUR time...THEIR money.



"PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
news:uaoIyWVwIHA.5892@TK2MSFTNGP02.phx.gbl...
> Get yourself an abacus, Sasha.
>
> sasha gottfried wrote:
>> The blame game can go on and on. The arrogance, and lack of communication
>> between these mega-bux, computer comrades is criminal. Who expects John Q
>> Customer to know what the hell "Sysrep Scenarios" are anyway!
>>
>> Pathetic!
>>
>> But thanks to this newsgroup for the heads up on these corporate clowns.
>>
>> MT
>>
>>
>>
>> "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
>> news:OFCUI$PwIHA.548@TK2MSFTNGP06.phx.gbl...
>>> I agree that the customer loses, sasha. BUT, HP has been well aware of
>>> Unsupported Sysprep Scenarios for quite some time now:
>>> http://support.microsoft.com/kb/828287
>>>
>>> Read the ' Different processor vendors ' section.
>>> There is definitely something amiss with how MS tests updates|SPs and
>>> with
>>> their lack of communication skills.
>>>
>>> However, this issue is directly attributable to HP, plain and simple.
>>>
>>> MowGreen [MVP 2003-2008]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>>
>>>
>>> sasha gottfried wrote:
>>>
>>>> Don't tell me Microsoft wasn't aware of this! Or was it just a set-up
>>>> to
>>>> blame the OEM's? Either way.......the customer loses!
>>>>
>>>>
>>>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>>>> news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
>>>>
>>>>> sasha gottfried wrote:
>>>>>
>>>>>> Doesn't Microsoft confer with major computer manufacturers before
>>>>>> putting out a major OS upgrade? As you say, HP manufactures many
>>>>>> AMD based computers. Are you telling me Microsoft isn't aware of
>>>>>> this, or doesn't bother testing their SP3 on such systems using
>>>>>> this 'image' applied? You'd think that between HP and Microsoft
>>>>>> they would 'expose' the mistake before allowing it to be foisted on
>>>>>> customers. But hell, our time is not THEIR money, is it?
>>>>>
>>>>> The OEMs pay less to Microsoft for the licenses of Windows XP (OEM
>>>>> License agreements) so they can make more profit selling to the
>>>>> end-consumer and for that they provide the end-consumer support for
>>>>> the
>>>>> machine - including the installed OS. That is a choice they made.
>>>>>
>>>>> Given that choice and the fact that SP3 has been available in some
>>>>> form
>>>>> (beta and otherwise) to the OEMs for over a year - they should have
>>>>> taken
>>>>> the responsibility and tested it. Not to mention - any OEM that
>>>>> decided
>>>>> an AMD processor was the same as an Intel processor (thus making one
>>>>> image) likely should have thought that out better. I am having
>>>>> trouble
>>>>> seeing it from your point of view that Microsoft (SP3) is to blame
>>>>> when
>>>>> it was not Microsoft that made the image being used by said OEMs nor
>>>>> were
>>>>> they the ones responsible for testing things on the OEMs own
>>>>> equipment.
>>>>>
>>>>> --
>>>>> Shenan Stanley
>>>>> MS-MVP
>>>>> --
>>>>> How To Ask Questions The Smart Way
>>>>> http://www.catb.org/~esr/faqs/smart-questions.html
>

sasha gottfried wrote:
> Yo'
>
> I can count...... Frankly, from a customer's standpoint, it doesn't matter
> who screwed up here. HP uses Microsoft and Microsoft uses HP. Meanwhile, in
> situations like this, they both USE the USER. Who are these prgrammers
> anyway? 25 year old hyped up ego-maniacal geeks playing inter-corporate
> competetive games with themselves?
>
> Like I say: OUR time...THEIR money.

You'll never convince the MS fanboys that MS *ever* makes a mistake.
They're acting like HP is some small mom and pop outfit that MS has
never heard of. The TRUTH is that MS throws out software for the paying
customer to test and then, and only then, they will put out a fix. For
instance, Vista was NOT ready for the public and won't be until there's
an SP2. Meanwhile, MS gets millions to test it for free and to top it
off, they PAY MS to test it.

You're right; it's criminal.

Fed up? Check out Ubuntu at www.ubuntu.com/. It's free and comes with
access to over 23,000 free programs.

What can be done with Ubuntu?

This:

Email
Surf the web
Burn CDs.
Rip CDs.
Listen to music.
Watch vidoes/DVDs.
Scan and print.
Spreadsheets.
Presentations
Newsgroups.
HTML editing.
Games like Chess, Tetris, all kinds of solitaire, etc.
Make videos.
Download photos from a camera and organize them.
Translations.
Use a dictionary
Learn how to touch type.
Edit images.
Send and receive a fax.
Take screenshots.
Create .PDF files.
Create and use a data base.
Instant messaging with over 10 different programs in one including
Windows Live Messenger.
IRC.
Bluetooth.

and much more!

What you can't do with Ubuntu:

Worry about:
The next update hosing your system,
WPA and WGA raising their ugly heads,
DRM,
Viruses,
Root kits,
Spyware,
and
Malware.

Alias
>
>
>
> "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
> news:uaoIyWVwIHA.5892@TK2MSFTNGP02.phx.gbl...
>> Get yourself an abacus, Sasha.
>>
>> sasha gottfried wrote:
>>> The blame game can go on and on. The arrogance, and lack of communication
>>> between these mega-bux, computer comrades is criminal. Who expects John Q
>>> Customer to know what the hell "Sysrep Scenarios" are anyway!
>>>
>>> Pathetic!
>>>
>>> But thanks to this newsgroup for the heads up on these corporate clowns.
>>>
>>> MT
>>>
>>>
>>>
>>> "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
>>> news:OFCUI$PwIHA.548@TK2MSFTNGP06.phx.gbl...
>>>> I agree that the customer loses, sasha. BUT, HP has been well aware of
>>>> Unsupported Sysprep Scenarios for quite some time now:
>>>> http://support.microsoft.com/kb/828287
>>>>
>>>> Read the ' Different processor vendors ' section.
>>>> There is definitely something amiss with how MS tests updates|SPs and
>>>> with
>>>> their lack of communication skills.
>>>>
>>>> However, this issue is directly attributable to HP, plain and simple.
>>>>
>>>> MowGreen [MVP 2003-2008]
>>>> ===============
>>>> *-343-* FDNY
>>>> Never Forgotten
>>>> ===============
>>>>
>>>>
>>>>
>>>>
>>>> sasha gottfried wrote:
>>>>
>>>>> Don't tell me Microsoft wasn't aware of this! Or was it just a set-up
>>>>> to
>>>>> blame the OEM's? Either way.......the customer loses!
>>>>>
>>>>>
>>>>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>>>>> news:%23tNEvWPwIHA.2188@TK2MSFTNGP04.phx.gbl...
>>>>>
>>>>>> sasha gottfried wrote:
>>>>>>
>>>>>>> Doesn't Microsoft confer with major computer manufacturers before
>>>>>>> putting out a major OS upgrade? As you say, HP manufactures many
>>>>>>> AMD based computers. Are you telling me Microsoft isn't aware of
>>>>>>> this, or doesn't bother testing their SP3 on such systems using
>>>>>>> this 'image' applied? You'd think that between HP and Microsoft
>>>>>>> they would 'expose' the mistake before allowing it to be foisted on
>>>>>>> customers. But hell, our time is not THEIR money, is it?
>>>>>> The OEMs pay less to Microsoft for the licenses of Windows XP (OEM
>>>>>> License agreements) so they can make more profit selling to the
>>>>>> end-consumer and for that they provide the end-consumer support for
>>>>>> the
>>>>>> machine - including the installed OS. That is a choice they made.
>>>>>>
>>>>>> Given that choice and the fact that SP3 has been available in some
>>>>>> form
>>>>>> (beta and otherwise) to the OEMs for over a year - they should have
>>>>>> taken
>>>>>> the responsibility and tested it. Not to mention - any OEM that
>>>>>> decided
>>>>>> an AMD processor was the same as an Intel processor (thus making one
>>>>>> image) likely should have thought that out better. I am having
>>>>>> trouble
>>>>>> seeing it from your point of view that Microsoft (SP3) is to blame
>>>>>> when
>>>>>> it was not Microsoft that made the image being used by said OEMs nor
>>>>>> were
>>>>>> they the ones responsible for testing things on the OEMs own
>>>>>> equipment.
>>>>>>
>>>>>> --
>>>>>> Shenan Stanley
>>>>>> MS-MVP
>>>>>> --
>>>>>> How To Ask Questions The Smart Way
>>>>>> http://www.catb.org/~esr/faqs/smart-questions.html
>
>