[1.298][Client] Stopping it from launching a site on exit

[quote name='twostars' timestamp='1297205291' post='2733']
Easy one, not sure why it was never really posted officially but here goes (pretty much a straight copy from a post I made in the old Snoxd):


What we need to do here is NOP out the call to ShellExecuteA(). You could clear out the entry in Texts_us.tbl, but that'll load explorer instead (in your client's folder). You *may* be able to NULL it out completely, but I don't recommend it - ShellExecute() still gets called regardless.

So anyway - the function has 6 arguments, as you can see in its definition from MSDN:

Kod:

HINSTANCE ShellExecute(     
    HWND hwnd,
    LPCTSTR lpOperation,
    LPCTSTR lpFile,
    LPCTSTR lpParameters,
    LPCTSTR lpDirectory,
    INT nShowCmd
);

Which can be accounted for here:

Kod:

00646308  6A 01            PUSH 1
0064630A  53              PUSH EBX
0064630B  53              PUSH EBX
0064630C  50              PUSH EAX
0064630D  68 00646D00      PUSH 006D6400                  ; ASCII "open"
00646312  53              PUSH EBX
00646313  FF15 C4326A00    CALL DWORD PTR DS:[<&shell32.ShellExecut>; shell32.ShellExecuteA


So, if your client EXE is the same as mine (USKO 1.299), just NOP out all of those lines you see above so it looks like:

Kod:

00646308  90              NOP
00646309  90              NOP
0064630A  90              NOP
0064630B  90              NOP
0064630C  90              NOP
0064630D  90              NOP
0064630E  90              NOP
0064630F  90              NOP
00646310  90              NOP
00646311  90              NOP
00646312  90              NOP
00646313  90              NOP
00646314  90              NOP
00646315  90              NOP
00646316  90              NOP
00646317  90              NOP
00646318  90              NOP


Also remember that the client EXE needs to be unpacked, or you won't see any of this.

Done. Easy!
[/quote]