Within Windows

That’s an awesome tool. I’m sure now using 3rd party themes would be a lot easier for people.

Awesome.

thanks Rafael :)

An Awesome, Quick and Simple tool. Great work :)

SV33T!!!
Worked great on a copy of Xp that uses only 40mb of ram, next to test it on FLP and beta releases too =P

I like the logo.

@ASF: Because a patched file has to be repatched every time you update windows, whereas a kernel driver “patches” while starting
I found another great use for this: Windows 7′s XPM, skin your XP to look _kinda_ like your current install, you don’t get glass, but it will still be an improvement over the ugly XP theme.

Rafael,
Your name is all over the web because of this. Its a great tool and I really enjoy it. Thanks for sharing with the world. Also I was able to go back to Hawaii for a couple weeks. Good times, went back to Schofield and saw how much it has changed.

Why does this app try to make internet contact ?

@pizzaboy192: You should probably know what you’re talking about before you correct someone. If you patch in memory you don’t have to redo anything if you patch in memory. Only when you replace the uxtheme.dll physically do you have issues. We’ve patched in memory and installed 2 Service Packs and made sure all updates were downloaded and never once had to fix the patch we use which was created by Andreas of AVEDESK. So get your facts straight first.

@jeff: And I quote myself
“pizzaboy192 June 22, 2009 at 12:27 pm

@ASF: Because a patched file has to be repatched every time you update windows, whereas a kernel driver “patches” while starting”
what you said is basically a lengthier version of the same comment I made, but yet making it sound like I’m an idiot… I congratulate yourself for that amazing effort on your part for reading and comprehending someone else’s comment.

No. What you’re saying is wrong pizzaboy. You do not have to repatch every time you update Windows when you do it in memory. I have never come across a single update that broke the patch we’re using. Not one. And i’ve installed plenty of Windows updates where i didn’t have to reboot and nothing broke.

First, do you have a name other than pizzaboy?

I’ve never seen our patch get killed. It’s been over a year since we’ve been doing this. Now when i hear of someone saying you have to repatch i’m reminded of the days of StyleXP where every single time there was a SP, StyleXP died a sudden death. Just not that way with our stuff.

@jeff: I do have another name, but I don’t use it for security purposes…
As for the patches, any program, weather it be your’s, Rafaels, StyleXP (yes, it is a kernel driver), TuneUp utilities, or “Uber 1337 Patch” (as an example) are all programs that instead of physically patching a file, they modify Windows’ memory to allow it to load unsigned themes. (That is my guess, I don’t code, and am too lazy to ask for a real answer, so correct me if I’m wrong)
The person who asked why Rafael’s program is so much better than his patches gets the simple answer: Because the patched file (Uxtheme.dll) is replaced in every startup. A program, wether Rafael’s or not, that “patches” for you, does not apply to those rules, since it doesn’t physically modify the system files. Rafael’s files are\were there for those who didn’t mind re-copying the files, but it is just easier for Rafael to write a program that does all the dirty work for him, and that way he isn’t bugged with emails every Patch Tuesday saying “OMG TEH PATHC BROK! FIX IT NAO” (lame attempt at humor there).
Your program is (in theory) the same as Rafael’s, but is nowhere near what Rafael’s patches did.

So… just to clarify, Rafael’s program is not a patched system file, but a kernel driver, used to “trick” windows into letting you load custom themes. His program does the same thing (in theory) as any of those programs you pay for to allow you to run your favorite theme on XP, Vista, 7, FLP and many others (I’m just guessing again, haven’t had a chance to see if they work on whistlers or longhorns yet)

In the end, seriously who cares how its patching as long as its safe and it works? Like i’ve said the patch process we use for XP has performed flawlessly. That’s all i care about. I don’t sell software, i sell the themes we create. The software is made so that i have my own distribution platform to release them on.. theme, icons, etc. If Rafael’s works great, then awesome. But i don’t want people saying his way is the only really good way since its not. It may be good but its certainly not the only way that works. That’s all i’m saying. In the end, to me, its all about the themes not what makes them run.

I personally like the disk-file patches since they don’t require extra constantly-running services or drivers. I try to trim as much as I can (although I tend to avoid trimming drivers since that’s asking for trouble if I trim the wrong thing) and I have my XP system down to 3 svchosts and a few other service processes.

Not sure if I agree with your cons about disk patches Rafael. As long as proper hashing is done before and after a patch, and the original file is backed up, I wouldn’t see a problem since any patching errors would be caught before the system file is replaced. Only con I can see is that if MS releases a Windows Update that overwrites the file then a new patch has to be created. Uxtheme on XP isn’t updated all that often though, I think it was just every SP for the most part. But yeah the big con is that a patch has to created for every individual DLL build… quite tedious, as I’m sure you know. :)

Is this the Win7 Starter bg image workaround you spoke about before?

Nevermind.

Now using 3rd party theme is not painfull, thanks for this.

Installed it on 7 6.1.7600 cannot find any trace of it. dunno how to even find where to open the thing

haha Jeff is a retard. He keeps saying the *same thing* as Pizzaboy only he’s right and pizzaboy’s wrong somehow.

LOLd from the future

hai,.. i try to uninstall uxstyle core but i can’t.
the following message appear when i try to uninstalling it!
“your theme subsystem (e.g. uxtheme.dll, themeui.dll) has been tampered with.uxStyle requires this…..”
what i should do!
regards! :)

had no problems whatsoever