[dencorso]

The problem with version numbers is MS starts their numbering from arbitrary points... So, while one keeps *only* to files *they* intended for a given OS, version numbers work OK (sort of...). But when we started including files they intended should be used in NT6, Win2K and now WinXP, some numbering lines began to cross. This explanation holds for most cases, but, maybe, not all.

[PROBLEMCHYLD]

dencorso, on 16 July 2012 - 03:16 PM, said:

The problem with version numbers is MS starts their numbering from arbitrary points... So, while one keeps *only* to files *they* intended for a given OS, version numbers work OK (sort of...). But when we started including files they intended should be used in NT6, Win2K and now WinXP, some numbering lines began to cross. This explanation holds for most cases, but, maybe, not all.

I guess that's why HFSLIP goes by date and not by version.
I don't know if I missed any, but I think I have all the latest working updates as of now for SP3.
I'm sure if I continue working on it, I will find more ways to improve it. Thanks again

This post has been edited by PROBLEMCHYLD: 16 July 2012 - 03:23 PM

[erpdude8]

PROBLEMCHYLD, on 23 June 2012 - 08:39 AM, said:

Found 2 more versions. I haven't tested them yet.

OLEAUT32.DLL 2.40.4527.0 (Windows2000-KB886766-v2-x86-ENU.EXE) +V3
OLEAUT32.DLL 2.40.4528.0 (Windows2000-KB139071-x86-ENU.EXE)

those 4527 and 4528 builds of oleaut32.dll file will break some apps on your 98se machine, PROBLEMCHYLD.
just like with what build 4532 from win2k did.

I use the NT4 version of oleaut32.dll file 2.40.4520.0 dated 12/21/2007 which is actually newer than 2.40.4522 dated 6/20/2003.

and here's a shocker about v2.40.4520 of oleaut32.dll! (pay close attention dencorso and PROBLEMCHYLD!)
it's also listed in MS KB article 327177.
BUT version 2.40.4520 of oleaut32.dll in KB327177 is dated 5/31/2002 with a size of 929,792 bytes
while version 2.40.4520 of oleaut32.dll in MS08-008 (946235) is dated 12/21/2007 with a size of 939,144 bytes.

SO, those two oleaut32.dll files that are version 2.40.4520 are NOT binarily identical (hmm, did Microsoft loose track of version numbers there?) confusing, isn't it?

I have the newest working oleaut32.dll file (build 4520) from the MS08-008 security bulletin for Win9x.

This post has been edited by erpdude8: 26 July 2012 - 06:47 PM

[tomasz86]

@erpdude8

Unfortunately this seems to be a standard M$ practice... A lot of Win2k udpates (especially HBRs) have got files with same version number as the other ones but the file itself may be different / have different date, etc. A good way to determine which one is really newer is to compare version number first, and then, if they are identical, use xcopy/d to use the newer one (by date). HFSLIP uses xcopy/d only which in my opinion is a very bad method because there are sometimes newer files with older date. That's why I use both - first version compare and then xcopy/d only if the version is identical.

[dencorso]

And that's why I recommend the PETimestamp, which is difficult to change, as the control date, instead of either of the three dates from the directory entry. Here I described two different oleaut32.dll V. 2.40.4519.0, while here is my tool for reading the PETimestamps.

[PROBLEMCHYLD]

erpdude8, on 26 July 2012 - 06:41 PM, said:

I have the newest working oleaut32.dll file (build 4520) from the MS08-008 security bulletin for Win9x.

This version is already included in the SP. Thanks for being aware, but I believe I have all the latest files included.

dencorso, on 26 July 2012 - 09:31 PM, said:

And that's why I recommend the PETimestamp, which is difficult to change, as the control date, instead of either of the three dates from the directory entry. Here I described two different oleaut32.dll V. 2.40.4519.0, while here is my tool for reading the PETimestamps.

And this is why I said thank you. If I'm not aware of a new file, then I can't check the PETimestamp.
Thanks again for your tool. I notice it doesn't handle VXD files on WinXP.

This post has been edited by PROBLEMCHYLD: 27 July 2012 - 09:42 AM

[dencorso]

PROBLEMCHYLD, on 27 July 2012 - 09:42 AM, said:

I notice it doesn't handle VXD files on WinXP.

Well, VxDs are LE not PE files. I wrote VxDVer to help handle them under XP, I'm sure you'll find it useful.

[PROBLEMCHYLD]

Windows ME version of
Windows Management Instrumentation + Web-Based Enterprise Management works on Win98SE.
I wanted to add this version to the SP, but I didn't want people to think it was becoming a replica of 98SE2ME.
dencorso, gave some advice about using newer files because of the newer code.

[PROBLEMCHYLD]

Does anyone know where I can get the file DGBHELP.DLL 6.0.17.0/6.0.0017.0?

[tomasz86]

PROBLEMCHYLD, on 05 October 2012 - 10:00 AM, said:

Does anyone know where I can get the file DGBHELP.DLL 6.0.17.0/6.0.0017.0?

Here you go

http://www.microsoft...s.aspx?id=17155

Download "sql2ksp3.exe".

[jaclaz]

PROBLEMCHYLD, on 05 October 2012 - 10:00 AM, said:

Does anyone know where I can get the file DGBHELP.DLL 6.0.17.0/6.0.0017.0?

Get it from SQL 2000 SP3 (sql2ksp3.exe):
http://www.microsoft...s.aspx?id=17155

jaclaz
EDIT: I am getting old , tomasz86 was faster than me....

This post has been edited by jaclaz: 05 October 2012 - 10:53 AM

[PROBLEMCHYLD]

Thanks guys
@ jaclaz - You'll have to eventually retire sooner or later

[jaclaz]

PROBLEMCHYLD, on 05 October 2012 - 11:04 AM, said:

Thanks guys
@ jaclaz - You'll have to eventually retire sooner or later

Not really (or not any soon ), but is good to see how the young padawans can feel the force....
I have still at least 850 years before me :

Yoda said:

When nine hundred years old you reach, look as good, you will not.

jaclaz