WinXP KB319740 future SP3 uxtheme.dll...


Recommended Posts

Hello,

I have searched the forums for any WinXP SP3 hotfix threads, but did not turn up anything related to this, however apologies if this has been discussed...

I understand that these future WinXP SP3

hotfixes are still under 'testing stages' from Microsoft, but when I

see any leakage reports especially since I do utilize other msstyles,

rather then the default WinXP Classic and Luna msstyles, I like to

explore them...

Now I do use a patched WinXP SP2 uxtheme.dll:

uxtheme.dll 6.0.2900.2180 (xpsp_sp2_rtm.040803-2158) --->this allows

me to use other VS...

The WindowsXP-KB319740-v5-x86-ENU.exe (reported kindly above by

olmari) has a new uxtheme.dll:

uxtheme.dll 6.0.2900.2523 (xpsp.040919-1030)--->of course this is not

patched so that one can run other msstyles...

Now I realize that WinXP SP3 may not be out prior to Vista, which I

will upgrade to immediately...lol, but would one of our knowledgeable

coding members be able to patch this future(hopefully) SP3 uxtheme.dll

so that I could apply the KB319740 hotfix, and be able to run other

msstyles?

I do know that the uxtheme.dll are 213kb, so there is probably another

'file' within this patch to, but if possible I would like to try out

this GDI-Object leak patch (still under testing from MS)...

Thanks

Links to MS KB319740 Article and actual WinXP-KB319740-v5-x86-ENU.exe:

http://support.microsoft.com/default.aspx?...kb;en-us;319740

Here you can actually download this fix for few languages:

http://www.cakewalk.com/Support/kb/kb2005243.asp

Source of info: http://www.thehotfix.net/sp3.html

Link to comment
Share on other sites

Wonder what's in the new uxtheme.. maybe just a security update or something. I hope/ think it might support a new official theme or more likely add support for some of Vista's effects and such.

Link to comment
Share on other sites

Use a hex editor to do it yourself. it's quite easy.

At offset 0001BB8C change

CODE

81 EC 88 00 00 00 A1 18

to

CODE

33 F6 8B C6 C9 C2 08 00

Don't forget to replace all instances of uxtheme.dll or this will not work.

C:\Windows\System32

C:\Windows\System32\dllcache

C:\Windows\System32\LastGood (may not exist)

C:\Windows\ServicePackFiles\i386

Good luck!

Link to comment
Share on other sites

Use a hex editor to do it yourself.  it's quite easy.

At offset 0001BB8C change

CODE

81 EC 88 00 00 00 A1 18

to

CODE

33 F6 8B C6 C9 C2 08 00

Don't forget to replace all instances of uxtheme.dll or this will not work.

C:\Windows\System32

C:\Windows\System32\dllcache

C:\Windows\System32\LastGood (may not exist)

C:\Windows\ServicePackFiles\i386

Good luck!

gadean,

Good deal, and I will give-it-go! Thanks...

:yes:

Link to comment
Share on other sites

Dam missed the edit time, and I know why you stated, "Good Luck!"...lol

Using HexWorkshop 4.2 (shareware)...I have tried to locate:

Offset: 0001BB8C--->where HexWorkshop reports there are no instances in this new uxtheme.dll So then went to find: Code 81 EC 88 00 00 00 A1 18, as I know that I may try another 'freeware hex editor' that may be a little easier for me to use...n0000b...lol

Please see 'ss'...and please not questioning your knowledge, but my lack-of-it, with any hex editor related matter... :)

Offset: 00019A78--->has this Code 81 EC 88 00 00 00 A1 18

http://img65.imageshack.us/img65/4422/hex3ti.jpg

Link to comment
Share on other sites

Looks like the offset has changed.

Typically, with each release of uxtheme.dll, the proper hex string has not changed much. Try doing a search for "81 EC 88 00 00 00" (leaving out the last 2 bit sets, which tends to vary). If there's only one instance you can bet it's what you need to change.

Replace the match (plus the next 2 bit sets, whichever those may be) with "33 F6 8B C6 C9 C2 08 00" and you should be good to go.

If you are not comfortable with doing this backup uxtheme.dll before patching it. It's not a critical file (well, your pc will still boot but it will show the classic theme) so it can be restored with ease.

And once again, good luck! :p

(Who knows, with practice this could become your new hobby!)

Link to comment
Share on other sites

Funny stuff........lol!

Please kindly see my PM...

:laugh: :rofl:

I may have gotten it...as that was the new Offset string...will backup SP2 uxtheme.dll, and let you know how it goes...

:yes:

Edited by gahbmwM5
Link to comment
Share on other sites

Looks like the offset has changed.

Typically, with each release of uxtheme.dll, the proper hex string has not changed much.? Try doing a search for "81 EC 88 00 00 00" (leaving out the last 2 bit sets, which tends to vary).? If there's only one instance you can bet it's what you need to change.

Replace the match (plus the next 2 bit sets, whichever those may be) with "33 F6 8B C6 C9 C2 08 00" and you should be good to go.

If you are not comfortable with doing this backup uxtheme.dll before patching it.? It's not a critical file (well, your pc will still boot but it will show the classic theme) so it can be restored with ease.

And once again, good luck!:p? :p

(Who knows, with practice this could become your new hobby!)

[/quotExcellent gadean...thanks for your patience and great sense of humour!

Got it!...the key (as you stated, was actually finding this:

CODE: 81 EC 88 00 00 00 A1 18--->although it was located in a different offset, but you know your stuff! Now I no longer (hopefully have the nasty GDI-Object leak), and a newer uxtheme.dll that is properly patched and allows me to run other msstyles!

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.