Hacked theme dll


Recommended Posts

Windows XP doesn't have DOS, and if you boot by a win9x floppy, you won't be able to see your drives unless for some reason you're still using the god forsaken FAT32 system. If you boot into safe mode, you can rename uxtheme.dll to something else, then simply rename the hacked one as uxtheme.dll. Worked fine for me.

AJ

Link to comment
Share on other sites

Patcher for UXTHEME.DLL.

WARNING: User assumes all responsibility for running the patch program

and patching the uxtheme.dll file. User agress to hold harmless TGT Soft

LLC. If you do not agree to these terms, please do not patch the file.

To patch UXTHEME.DLL you must follow these directions. If it does not

work, please do not email us. We tried.

First, you must have administrator privileges.

Second, you must understand how to rename and copy files.

Third, you must understand where your system directory is and how to

navigate there (although the patcher will tell you where it is).

If you update your Windows® XP operating system, the patch may become

invalid.

Ready? Here are the instructions.

1) Run the uxthemepatcher.exe. This program will produce a "uxtheme.pat"

file in your system32 directory. If this program fails, DO NOT

CONTINUE.

2) After you have successfully run uxthemepatcher.exe, a message box

will tell you where the uxtheme.pat file is. If your system directory

is c:windowssystem32 -- the uxtheme.pat file will be there. If it is

c:winntsystem32 -- the uxtheme.pat file will be there. And so on.

Make a mental note of where the .pat file is.

3) Assuming your system directory is c:windowssystem32 go into the

directory c:windowssystem32dllcache. This directory may be hidden.

If it is, you need to unhide it to see it, or use the command prompt.

4) Rename the uxtheme.dll file in dllcache to uxtheme.bak (or some other

name).

5) Rename any uxtheme.dl_ or uxtheme.dll that might be found in other

locations on your system such as c:i386 or the place where you

installed Windows® XP from.

6) Make sure you have NO CDs in your system (especially the Windows® XP

install CD!).

7) Assuming your system directory is c:windowssystem32 go into the

directory c:windowssystem32. Rename uxtheme.dll to uxtheme.bak or

some other name. Copy uxtheme.pat to uxtheme.dll.

8) You might get a warning from Windows System File Protection. You need

to answer the two questions properly, and on your own volition to

ensure that the uxtheme.dll file is not replaced with the original.

9) If all goes well, the uxtheme.dll will be the same DATE and TIME as

the uxtheme.pat. If this is the case, REBOOT. Do not logoff, you need

a full reboot.

Hope this works. If it does not, you can always try the Style XP trial

for 30 days.

http://www.tgtsoft.com

Lmao...too many if's in here for me, but the choice is all yours.;)

Link to comment
Share on other sites

Odd how the earlier betas of stylexp were nothing more than this patched UXTheme.dll, and it did all this for you, only requiring a reboot. Looks to me like they're just trying to make it look as complicated as possible (in reality it's extremely simple) to convince people to buy the non-free version.

I also like where it implies that this may cause problems if you update windows. If uxtheme.dll was changed in any future version of windows, the file would simply be replaced, and if you really made a pig's ear of it, you could quite easily fix it with a quick sfc /scannow. I'd be much more worried about the implications of a program which patches something in memory, and if the dll changes, chances are that so will the memory address that needs to be patched. Of course, StyleXP will continue trying to patch the same address, and could lead to all manner of randomness from windows simply refusing to work with their program loaded, to swarms of angry monkies flying out of your case.

Link to comment
Share on other sites

The tgtsoft instructions seem a bit misleading.

I just copied dclanz suggestions, too lazy to type:

Grab the uxtheme.dll from vinh's website

Once in the CommandPrompt Module type the following:

cd C:WindowsSystem32

ren C:WindowsSystem32uxtheme.dll uxtheme.bak

copy C:WindowsTempuxtheme.dll C:WindowsSystem32

More info from this thread

Only for the curious minds:

Anyhow in an earlier thread here I found a few poeple talking about inuse.exe, very interesting file.

download file

http://download.microsoft.com/download/win...EN-US/inuse.exe

Info on file

http://support.osisoft.com/SupportFiles&He.../NTinuseexe.htm

MS Info on the file

http://www.microsoft.com/windows2000/techi...ing/inuse-o.asp

Basically, it offers the power to overwrite a file in use ....

I'll give it a go in a 2-3days

I'm flying overseas going to usa .. passing thru uk ;-) ....

If I do manage to get it to work.. I might even try to automate it.

If anyone else wants to give it a try, please feel free to, and make sure to post your file here for future reference.

Link to comment
Share on other sites

My prefence is for the hacked DLL, which was what TGT's was before they changed it so they'd have something a little more justifiable to sell. The fact is that with StyleXP, you'll always have a process running in the background, it may be extremely small on resource usage, but it's still there, I already have enough crap in my systray. As to how they work functionally, there is no difference, they are both a way to allow Microsoft's Visual Styles Engine to load themes which are not digitally signed by Microsoft, nothing more.

AJ

Link to comment
Share on other sites

In my opinion the hacked version is better than the patch and it's really quite simple to do. I may sound a bit biased, but I'd rather screw up my system myself than to let Tgt do it for me.:p

Link to comment
Share on other sites

Originally posted by comet

still no one anwsers, which is better hacked or tgt's

If you're comparing to tgt's uxtheme.dll patcher, they're exactly the same, but for fairly obvious legal reasons tgt can't distribute a modified version of an MS dll, so they supply a program that applies the appropriate changes to the dll for you.
Link to comment
Share on other sites

LOL...that's right they both do the same thing, that is....enable XP to use other visual styles. Some may prefer the hacked version and some may prefer the patch. It's totally up to the user. It would be nice if M$ would implement a feature in future versions of XP to let people create/use their own visualstyles. That would be really cool.:bandit:

Link to comment
Share on other sites

Originally posted by AJCrowley Esq

Windows XP doesn't have DOS, and if you boot by a win9x floppy, you won't be able to see your drives unless for some reason you're still using the god forsaken FAT32 system. If you boot into safe mode, you can rename uxtheme.dll to something else, then simply rename the hacked one as uxtheme.dll. Worked fine for me.

AJ

Windows XP does have DOS, lol! Press F8 before boot screen.

Link to comment
Share on other sites

Originally posted by l77Il7H

Windows XP does have DOS, lol! Press F8 before boot screen.

The funny thing about this is, THAT'S NOT DOS. That's a command prompt, and part of the recovery system built into XP.

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.