adric wrote:... Don't know why Ms did not use the newer file for XP do you?

Al

I don't know either, but I have checked installation of that KB for MSO2007, (the version in this runtime pack), and it doesn't replace the usp10.dll in system32. It gets placed in the MSO directory in programfiles--which is probably why it doesn't come with a cat.

For anyone who wants to update their version of zlib1.dll in their runtime packs I have uploaded 1.2.7 here. It contains both x86 and x64 versions.
I grabbed them from software that can be downloaded here, as the main zlib site no longer seems interested in posting a compiled dll for Windows.
I have only done limited testing with this dll, but it seems to work fine for me.

Actually, Kels, are you certain that the Vista usp10.dll (1.626.6002.22384) with a CAT offers features or improvements in text display on an XP system when compared to the last XP one (1.420.2600.5969)?

I searched briefly a few weeks ago and found that the last ones with CATs that work on XP, issued on the same date, (the XP and Vista versions,) were issued for security reasons. (So superiority of the Vista dll would most likely predate that last release with a CAT.)

If anyone can a post a link giving evidence or even a strong hint at the superiority of the Vista usp10.dll over the XP one for CTF unicode text display on an XP system please post here soon for everyone. A sample doc would be even better. I couldn't find anything when I searched a few weeks ago.

Edit:
It seems the practice now, is to copy any newer usp10.dll into the application directory of any app that can take advantage of the new one, rather than replacing the system one.

Last edited by shiner on Sat Sep 22, 2012 5:45 pm, edited 1 time in total.

ricktendo64 wrote:There is no need to mention them because usp10.dll is already in your XP disk and the cat is added automatically

Please be a little more specific about usp10.dll. Without integrating this addon, the XP disk contains an older version of the file, or the exact same version? It is also automatically replaced by the newer version from this addon?

That's why I was asking for any references in Entries_Runtimes.ini or Runtimes.ini. I understood that *.cat files are added automatically, but does this happen also with *.dll files?

To simplify my questions, let's say I want to make an addon with just usp10.dll and its *.cat file. I only have to place the *.cat into SVCPACK folder and include the dll next to SVCPACK folder (out of it), but what should I write in Entries_Runtimes.ini ?

XPSP3_QFE_UpdatePack_20130709.7z has a newer comdlg.ocx (6.1.98.36) than what's in this addon (6.1.98.16). I only noticed because I got a message during the XP install asking if the newer version of the file should be replaced.

I wanted to update the runtimes.cab file, so I went looking for a tool to create a cab file. As a test, I used the unpacked runtimes directory as input. I was able to create a cab file, but it is larger in size than the original cab. What is the recommended tool for creating smaller cab files?

adric wrote:I wanted to update the runtimes.cab file, so I went looking for a tool to create a cab file. As a test, I used the unpacked runtimes directory as input. I was able to create a cab file, but it is larger in size than the original cab. What is the recommended tool for creating smaller cab files?

No idea. I used cabdir.exe (old flight simulator dev kit tool) whose default was compress. I also tried IExpress and the
compression was no better. I don't know what Kel used when cabbing his runtimes. I'll fiddle with your suggestions.

Also I have a question regarding USP10.dll. An interesting official for xp update is out - KB2850869 - that updates USP10.dll.

So the new official version for xp is 1.420.2600.6421, and the one from your pack I think it's 1.0626.6002.22402. I installed it on a live system, that had your addon pack pre-installed, and while your (vista) version of USP10.dll is still in C:\Windows\system32, the one from the update went to C:\Windows\system32\dllcache.

So, the one from your pack is from 2010's KB2028505 (LDR), the latest official one for vista is from 2010's KB981322 (GDR), and the latest one for xp only is from 2013's KB2850869.

Do you think any changes for your pack regarding USP10.dll are required?