XP SP1 Heap Algorithm Update

[Pete]

link to knowledgebase info:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;815411

link to the install:
http://www.iebeta.net/files/Q815411_WXP_SP2_x86_ENU.exe

Does microsoft have any official word on this update that
is floating around the internet?

[Rick \Nutcase\ Rogers]

Hi Pete,

The "official" word is the article you just posted a link to. What more were
you looking for?

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x - http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone -
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> link to the install:
> http://www.iebeta.net/files/Q815411_WXP_SP2_x86_ENU.exe
>
> Does microsoft have any official word on this update that
> is floating around the internet?
>

[Rick \Nutcase\ Rogers]

Hi Pete,

The "official" word is the article you just posted a link to. What more were
you looking for?

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x - http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone -
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> link to the install:
> http://www.iebeta.net/files/Q815411_WXP_SP2_x86_ENU.exe
>
> Does microsoft have any official word on this update that
> is floating around the internet?
>

[Mike Brannigan [MSFT]]

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> Does microsoft have any official word on this update that
> is floating around the internet?

Pete,

Do not post links to fixes that are not intended for public availability.

The resolution step in the Q article clearly states that this fix should
only be obtained from Microsoft Support.
There are specific reasons that this fix is not generally made available.

In response to your question - the fix is detailed in the Q article. Please
follow the instructions stated there.
--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> Does microsoft have any official word on this update that
> is floating around the internet?
>

[Mike Brannigan [MSFT]]

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> Does microsoft have any official word on this update that
> is floating around the internet?

Pete,

Do not post links to fixes that are not intended for public availability.

The resolution step in the Q article clearly states that this fix should
only be obtained from Microsoft Support.
There are specific reasons that this fix is not generally made available.

In response to your question - the fix is detailed in the Q article. Please
follow the instructions stated there.
--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions.
Please use these newsgroups

"Pete" > wrote in message
...
> link to knowledgebase info:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;815411
>
> Does microsoft have any official word on this update that
> is floating around the internet?
>

[JimC]

Mike,

Unofficial links to fixes, such as the 815411 issue for XP SP1, sprout
because of the way MS confronts such issues. Many users spend long periods
on hold waiting for interrogation by an MS support person (whose
communication skills and technical expertise may or may not be satisfactory)
in order to qualify as a candidate for a download fix.

When there are specific reasons why a fix should be approached with caution,
why is MS reluctant to describe these reasons in the same articles that
announce the fixes. Surely, one competent technical description should
provide users with a better understanding of an issue than a conversation
with a random support person after a frustrating wait in the hold pool.

If cautions cannot be adequately documented in the first place, it is absurd
to expect satisfactory problem resolutions over the phone.

Jim

"Mike Brannigan [MSFT]" > wrote in message
...
> "Pete" > wrote in message
> ...
> > link to knowledgebase info:
> > http://support.microsoft.com/default.aspx?scid=kb;en-
> > us;815411
> >
> > Does microsoft have any official word on this update that
> > is floating around the internet?
>
> Pete,
>
> Do not post links to fixes that are not intended for public availability.
>
> The resolution step in the Q article clearly states that this fix should
> only be obtained from Microsoft Support.
> There are specific reasons that this fix is not generally made available.
>
> In response to your question - the fix is detailed in the Q article.
Please
> follow the instructions stated there.
> --
> Regards,
>
> Mike
> --
> Mike Brannigan [Microsoft]
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights
>
> Please note I cannot respond to e-mailed questions.
> Please use these newsgroups
>
> "Pete" > wrote in message
> ...
> > link to knowledgebase info:
> > http://support.microsoft.com/default.aspx?scid=kb;en-
> > us;815411
> >
> > Does microsoft have any official word on this update that
> > is floating around the internet?
> >

[JimC]

Mike,

Unofficial links to fixes, such as the 815411 issue for XP SP1, sprout
because of the way MS confronts such issues. Many users spend long periods
on hold waiting for interrogation by an MS support person (whose
communication skills and technical expertise may or may not be satisfactory)
in order to qualify as a candidate for a download fix.

When there are specific reasons why a fix should be approached with caution,
why is MS reluctant to describe these reasons in the same articles that
announce the fixes. Surely, one competent technical description should
provide users with a better understanding of an issue than a conversation
with a random support person after a frustrating wait in the hold pool.

If cautions cannot be adequately documented in the first place, it is absurd
to expect satisfactory problem resolutions over the phone.

Jim

"Mike Brannigan [MSFT]" > wrote in message
...
> "Pete" > wrote in message
> ...
> > link to knowledgebase info:
> > http://support.microsoft.com/default.aspx?scid=kb;en-
> > us;815411
> >
> > Does microsoft have any official word on this update that
> > is floating around the internet?
>
> Pete,
>
> Do not post links to fixes that are not intended for public availability.
>
> The resolution step in the Q article clearly states that this fix should
> only be obtained from Microsoft Support.
> There are specific reasons that this fix is not generally made available.
>
> In response to your question - the fix is detailed in the Q article.
Please
> follow the instructions stated there.
> --
> Regards,
>
> Mike
> --
> Mike Brannigan [Microsoft]
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights
>
> Please note I cannot respond to e-mailed questions.
> Please use these newsgroups
>
> "Pete" > wrote in message
> ...
> > link to knowledgebase info:
> > http://support.microsoft.com/default.aspx?scid=kb;en-
> > us;815411
> >
> > Does microsoft have any official word on this update that
> > is floating around the internet?
> >