Visual Styles In Longhorn...


Recommended Posts

:no: Sorry, your gonna have to code this one yourself.

Here are the basic instructions anyway. c/o AlphaAlien.

The files are

just associated files

that're called by uxdesksb.exe the hex number's are

line numbers. Edit using

an asm decompiler/debugger like OllyDbg. The only thing

that you really need

is the SBWatchdog

SBServer

ntdll.dll

%windir%\system32\ntsd.exe

--> change to kill styling in current builds

01001804-01001848 change 0 to 1

to disable watchdog true

mscorsn.dll

mscorjit.dll

mscorlib.dll

mscorsrv.dll

mscorwks.dll

mscoree.dll

serwvdrv.dll

umdmxfrm.dll

usp10.dll

lpk.dll

uxtheme.dll

winmm.dll

version.dll

d3d8thk.dll

d3d9.dll

dce.dll

gdi32.dll

user32.dll

rpcrt4.dll

advapi32.dll

msvcrt.dll

kernel32.dll

uxdesksb.exe

uxdesksb.pdb

01001ABF

01001C6E

01001CA6

01001D04

ntsd.exe=debugger

01002FD6 ADVAPI32.dll=non-watchdog security?

010030D6-01003106

0100333A-01003348

"SBDisableWatchDog",1

Link to comment
Share on other sites

o.O ................. can you like make that a little easier to understand, like saying what to do where. to me this looks jumbled

Link to comment
Share on other sites

It would've been nicer if this'd leaked when I wanted it to. When the new styling engine was fully in place. If it'd been released then MS wouldn't have really cared to spend the time to block it. On the HWGeeks thread of this last night there were lot's of MS employee's out of redmond reading it so it'll be blocked. Now we'll all have to wait till october when the new engine is in place plus all the time it'll take to redo a crack from scratch. 5/6months would've been much sooner for a permanent crack than the time it'll take now.

He got the info by saying he wanted to skin longhorn, I'd been sending the crack info out to interested skinners so their'd be skins in place by the time everything was ready to release this.

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.