-
These are debug strings that can be shown with an active kernel debugger, for example.
-
It's not legal although they don't really care enough to take any legal action.
-
Safe mode and disabling WFP is not required. Just delete Uxtheme.dll in \windows\servicepackfiles\i386 (if exists), then out of \system32\dllcache. After doing so, rename \system32\uxtheme.dll to uxtheme.old and drop in the patched DLL. A reboot is required.
-
The DLL isn't the problem here unless you installed it incorrectly. To ensure it's installed correctly, delete Uxtheme.dll in \windows\servicepackfiles\i386, then \windows\system32\dllcache, then rename \windows\system32\Uxtheme.dll to Uxtheme.old and drop in the patched Uxtheme.dll (and reboot)
-
Just wanted to give heads up I finally got thru with looking at AMD64 disassembly and patched up the 64-bit XP uxtheme.dll file(s)! As always, you can grab em from http://www.vortex-scratchpad.info
-
So you found the previous edits for previous builds of uxtheme and applied them to current builds. How could you claim this to be your own work then? In the words of a to-remain-anonymous board member that so pleasantly (sarcasm) PMed me:"And once it's been done once, the subsequent versions are tit." Keep in mind the credit you gave me wasn't given until *after* I had to publicly remind you in that thread. Obviously not, as publicly available information keeps ending up on the forums and labeled as 'your work'. Great work sonny!
-
It's not my work either - It was originally TGTsoft's work when they gave users the ability to manually patch their uxtheme.dll files - I merely keep the patches up-to-date (and stored in a repository) as it's not in TGTsoft's best interest to keep the patch updated (lose money).
-
There are a bunch of ways to skip over the CryptVerifySignature function thats called within' uxtheme and yet you use the exact same patched bytes as StyleXP/I use. Gimme a break - This is the second time you'd be improperly using other people's work (TGTSoft's in this case) and calling it your own.
-
No you didn't, you simply compared the original Uxtheme.dll to a patched Uxtheme.dll
-
The autopatchers amongst the internet search for a pre-determined group of bytes - This is unsafe and not guaranteed to be 100% successful. Instead, you should grab a copy of the DLL modified (correctly) @ http://vReality.net
-
After repairing, core system files are replaced with their originals from the CD. You need to reinstall your patched uxtheme.dll file.
-
Using in-line assembly: http://msdn.microsoft.com/library/default.....29_.topics.asp Int16h (int86 pointer?) documentation: http://www.shipbrook.com/jeff/zoomer/int16.html Hope that helps.
-
Here's a great tutorial: http://www.codeproject.com/csharp/dotnetbandobjects.asp