[Release] Siginet's MultiTheme AddonsPack v2.1
Did you apply the UXTHEME patch, jun_ph26?
Give Siginet time to transition to his new host. It should be back up soon.
I love the Luna 4a theme, but the "minimize, restore, close" buttons are a little weird. They are spaced apart and not together like in the regular Luna 4 theme. Is there a way to modify it? At first I thought it was the metrics section of the theme file, but I don't think that did the trick... Any thoughts?
The link seems to be working now. Let me know if you still can't get it.Kev_83 wrote:"Internet Explorer cannot display the webpage"
I used to have a backup of this but i must've deleted it
Anyone got a download for this as my PC is dying & i'm wanting to do a new install today
I think I'll upload a new Multi-Theme pack sometime soon.

- litemirrors
- Posts: 40
- Joined: Fri Jan 02, 2009 10:23 pm
- Location: Burbank, CA
Can't download
Kel's link ==> 404
Siginet's link ==> error:
Gosh... I need my theme fix 

Kel's link ==> 404
Siginet's link ==> error:
Code: Select all
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home2/aplusma1/public_html/integrator.professorcpu.net/data/downloadaddon.php on line 13
Warning: Cannot modify header information - headers already sent by (output started at /home2/aplusma1/public_html/integrator.professorcpu.net/data/downloadaddon.php:13) in /home2/aplusma1/public_html/integrator.professorcpu.net/data/downloadaddon.php on line 43

Nobody is perfect.
I am nobody.
I am nobody.
Do these themes work with XP x64? If not, can they be made to work with XP x64?
And last but not least, can these be made into a switchless installer similar to what 5eraph has done with his MS Signed Themes?
I must thank for these themes, at least for my 32 bit machines. Keep up the wonderful work.
And last but not least, can these be made into a switchless installer similar to what 5eraph has done with his MS Signed Themes?
I must thank for these themes, at least for my 32 bit machines. Keep up the wonderful work.
A mind is like a parachute, it only functions when it is open.
--Anonymous
How to Ask Questions the Smart Way
--Anonymous
How to Ask Questions the Smart Way
Siginet, I have found that if you remove the ".x86" from your "SourceDisksNames" in the inf files, these themes will be installable on an x86-64 system (using the infs). I am not sure on the addon directly for a 64 bit source yet, but the themes do work.
Now, only if I could get you to consider making them into a silent installer.
Now, only if I could get you to consider making them into a silent installer.

A mind is like a parachute, it only functions when it is open.
--Anonymous
How to Ask Questions the Smart Way
--Anonymous
How to Ask Questions the Smart Way
I've had a couple thoughts concerning on-the-fly patched file replacement. It's not as efficient as prepatching the file in the source, but a switchless installer does not have that luxury if we expect it to work on a running system that does not have the patched file.Siginet wrote:I don't mind if anyone else wants to update this addon [...]crashfly wrote:Now, only if I could get you to consider making them into a silent installer.
One thing I can't do yet is check a file's version so we know what file it should be replaced with. An MD5 check should work instead if we know the MD5s of the unpatched file versions, which would double as a check to see if the file ie still unpatched. But...
Keeping one to six patched UXTheme.dll file versions (depending on if we choose to support x86 SP2 and/or x64, not just the most common x86 SP3) will bloat the installer unless we can patch files in place upon execution, which I also don't know how to do.
BTW, the UXTheme.dll patch code needs updating for x64.

Untested:
Code: Select all
;XP/2003 x64 SP2
AMD64\UXTHEME.DLL|6.0.3790.3959|77251|4883EC78|33C0C390
I think this would be the best approach for a somewhat universal uxtheme patch:
Code: Select all
[General]
Author = Zacam
Builddate = 05/11/2008
Title = Multi-Patch: UXTHEME.DLL
Description = Addon which allows unsigned Themes
Version = 1.4
Website = http://ryanvm.net/forum/viewtopic.php?t=2274
[HexEdit]
;XP SP2
I386\UXTHEME.DLL|*|113178|83EC1C568D4DE4|33C0C9C2040090
;KB319740 - RVM 1.2.0 - 2.0.4
I386\UXTHEME.DLL|*|104714|83EC1C568D4DE4|33C0C9C2040090
;KB936929 - SP3
I386\UXTHEME.DLL|*|104746|83EC1C568D4DE4|33C0C9C2040090
;2003 Server SP2
I386\UXTHEME.DLL|*|175801|81EC88000000A11C|33F68BC6C9C20800
;XP/2003 x64 SP2
AMD64\UXTHEME.DLL|*|77251|4883EC78|33C0C390
If we start using wildcards in the code then we should at least list the known file versions that the patch works for. Besides, for all versions listed so far, the offset for each file version is different. Why not keep the file version code in place so we know which version that particular code it is intended to patch?
And we can't call this a universal patch for file versions where the offset is unknown. It would be unsafe to use wildcards for the offsets since we don't know which instance of that pattern must be replaced if it occurs more than once, and we should not replace all instances in a file.
All of this is assuming, of course, that the relevant code to patch is unchanged from previous versions. If not, we're making a huge mistake by patching the wrong code. Version specific code is the safest method going forward.
And we can't call this a universal patch for file versions where the offset is unknown. It would be unsafe to use wildcards for the offsets since we don't know which instance of that pattern must be replaced if it occurs more than once, and we should not replace all instances in a file.
All of this is assuming, of course, that the relevant code to patch is unchanged from previous versions. If not, we're making a huge mistake by patching the wrong code. Version specific code is the safest method going forward.
most hexedit tools allow *pattern search replace* ( nothing new for all around good hexedit tool )
as there is no option to wildcard the offset in integrator currently it does seem pointless to have wildcards work for file versions using fixed offset address's that will mostly end up hitting the correct address for the correct file version where is! that address aims for..
I'm guessing that with a longer search pattern with the address offset *wildcarded* in use, can work. avoiding the patch spreading to other unwanted location offset's inside the file & that this -longer search pattern- would meet with most if not all other file versions..
I've noticed this in xpsp3 beta's:
* nlite always knew where to patch the UXTHEME.dll regardless to different offsets & file versions that changed with every new sp3 beta release I have tried ..
bottom line is: having the option to use wildcards for the offset address is onlyl trivial for any hex edit tool, it really depends on how a user chooses to handle the tool
only if & where it was first optional (in integrator)
as there is no option to wildcard the offset in integrator currently it does seem pointless to have wildcards work for file versions using fixed offset address's that will mostly end up hitting the correct address for the correct file version where is! that address aims for..
I'm guessing that with a longer search pattern with the address offset *wildcarded* in use, can work. avoiding the patch spreading to other unwanted location offset's inside the file & that this -longer search pattern- would meet with most if not all other file versions..
I've noticed this in xpsp3 beta's:
* nlite always knew where to patch the UXTHEME.dll regardless to different offsets & file versions that changed with every new sp3 beta release I have tried ..
bottom line is: having the option to use wildcards for the offset address is onlyl trivial for any hex edit tool, it really depends on how a user chooses to handle the tool
only if & where it was first optional (in integrator)
If you do make it into a silent installer, you might have to specify that the user use there own method of a Uxtheme patch. On already running systems, that is left to the user. On an Windows setup type install, one should just "pre-apply" a patch (such as Zacam's or even just using nlite). That would suite me just fine as I use nlite on a 64 bit system.
A mind is like a parachute, it only functions when it is open.
--Anonymous
How to Ask Questions the Smart Way
--Anonymous
How to Ask Questions the Smart Way
Thanks 5eraph for putting this together, and thanks to Kel, Siginet and all the others who did the work on the various theme packs.
I had been using the signed themes pack and Ricks Luna Royale with Zacam's patch for a while but decided to give this a try with UH 129 update pack, and everything went fine.
Some nice theme choices in this pack.
thanks again.
one question, aside from the uxtheme dll, does this patch any other system files?
I had been using the signed themes pack and Ricks Luna Royale with Zacam's patch for a while but decided to give this a try with UH 129 update pack, and everything went fine.
Some nice theme choices in this pack.
thanks again.
one question, aside from the uxtheme dll, does this patch any other system files?
"You can lead a horse to water, but you can't make it drink."