by L. Spiro » Thu Jan 06, 2011 11:35 pm
Search the help file for “Hook Detection”.
It has been there all along.
ReadLocalMemory() and WriteLocalMemory() are all you need to modify any part of the kernel and undo any changes Game Guard may have made (ShowHooks() in the help file will show you plenty of hooks Game Guard has set).
Aside from removing existing hooks, you can add your own hooks.
This is necessary to defeat Game Guard because Game Guard checks its hooks and if it finds that you have removed them it will crash your PC.
You have to begin by inserting a hook on KiSwapThread() that puts the Game Guard hooks back when the Game Guard threads become active and removes them when any other thread becomes active.
This way Game Guard can’t see that you have modified its memory.
There are other ways also, such as tricking it to read a different copy of memory.
Although it seems advanced, many people are doing it, and MHS gives you all the tools you need to both study Game Guard and defeat it.
To be honest, I am a bit annoyed that no one has used these features after I spent so much time adding them for this purpose.
And the MHS source is available for download, so you can always make an undetected version if necessary.
L. Spiro
Our songs remind you of songs you’ve never heard.