Apologies if my posting to this group is not considered appropriate, but....

Does anyone know if the Heap corruption issues that were found in Win2000
(SP2 or less), and fixed in SP 3 of Win2000, have also been rolled into any
of the versions of XP? (See Q305227)

We have some software that is showing symptoms similar to those we
experienced prior to upgrading to SP3 of W2K, that now seem to be showing up
on a vanilla version of XP Pro.

I wonder if there are any techos out there that can confirm that the issue
is definitely resolved in XP (or one of the service pack updates).

[Obviously, we dont discount that the problem lies within our own software,
rather than laying blame with the OS, but any feedback may be helpful]

Thanks,
Adrian.

Looks like it -=should=- be fixed in XP. If you use the DLL Help Database
(http://support.microsoft.com/default...fileversion/dl
linfo.asp), you'll see that Windows 2000 SP3 uses version 5.0.2195.5400 of
NTDLL.dll, and XP uses 5.1.2600.0. So, in theory...


--
John Phillips
MVP - Windows SDK



"Adrian Ugray" <(E-Mail Removed)> wrote in message
news:%232GgGz$(E-Mail Removed)...
> Apologies if my posting to this group is not considered appropriate,
but....
>
> Does anyone know if the Heap corruption issues that were found in Win2000
> (SP2 or less), and fixed in SP 3 of Win2000, have also been rolled into
any
> of the versions of XP? (See Q305227)
>
> We have some software that is showing symptoms similar to those we
> experienced prior to upgrading to SP3 of W2K, that now seem to be showing
up
> on a vanilla version of XP Pro.
>
> I wonder if there are any techos out there that can confirm that the issue
> is definitely resolved in XP (or one of the service pack updates).
>
> [Obviously, we dont discount that the problem lies within our own
software,
> rather than laying blame with the OS, but any feedback may be helpful]
>
> Thanks,
> Adrian.
>
>

Thanks John,

Yes, it would seem it should be fixed. However, further digging (using
Dll Help - thanks for that one!) reveals the following for ntdll.dll

2000 SP3 (5.0.2195.5400) has a mod date of 7/22/2002
XP Vanillla (5.1.2600.0) has a mod date of 8/23/2001

So presumably, it is very possible that the bug still existed in 1st
XP Release.

XP SP1 (5.1.2600.1106) has a mod date of 8/29/2002, which is after the
2000SP3 release, so maybe it was rolled into SP1, however release
notes do not appear to mention it.

Of course, maybe XP's ntdll version is very different to previous
versions, however I doubt it, as MS only had a minor version number
upgrade....I cant seem to find any more info on this bug other than
that it was fixed in 2000 SP3 and an issue with OSs before it...

Appreciate the comments.
Adrian.

"John Phillips" wrote
> Looks like it -=should=- be fixed in XP. If you use the DLL Help
Database
>
(http://support.microsoft.com/default...fileversion/dl
> linfo.asp), you'll see that Windows 2000 SP3 uses version 5.0.2195.5400 of
> NTDLL.dll, and XP uses 5.1.2600.0. So, in theory...

> "Adrian Ugray" wrote
> > Does anyone know if the Heap corruption issues that were found in
Win2000
> > (SP2 or less), and fixed in SP 3 of Win2000, have also been rolled into
> any
> > of the versions of XP? (See Q305227)
> >
> > We have some software that is showing symptoms similar to those we
> > experienced prior to upgrading to SP3 of W2K, that now seem to be
showing
> up
> > on a vanilla version of XP Pro.
> >
> > I wonder if there are any techos out there that can confirm that the
issue
> > is definitely resolved in XP (or one of the service pack updates).
> >
> > [Obviously, we dont discount that the problem lies within our own
> software,
> > rather than laying blame with the OS, but any feedback may be helpful]
> >