Quote:
Originally Posted by Tykakasane
lawl i was messing with it but meh, can't even find a Error code, problem is that while Olly is running i won't get any Error code due to Mabi not even launching :X
and the Error code provided by running mabi without olly doesn't help me much ._. guess i'm REALLY too stupid for that kind of stuff
|
First thing is that error codes are implimented into the program,
it is when you do something bad that it will show you the message.
With that said, since the code is already written, you can find it using the refference string function from ollydbg without having mabi running
Second thing is, goto your mng.ini and see this setting
KillIsDebug = 0
I never use it before, but you can try it,
appearently it will allow olly to attach to mabi while it runs.
Quote:
Originally Posted by eluminx
Hm, that 0x3000ffff is nasty. Guessing I have to do something to that whole function that shows it somewhat being linked in the reference column. Tried several things, but ended in the same way.
|
There are few ways that hackshield message can appear,
If then else statement:
If <you are hacking> then
hackshield
else
you may procees
in that case, the jump is the "then", in this case, you would want to jump from checking to directly "you may proceed"
Another case:
If <no hacking find> then
you may proceed
else
hackshield
in this case, you want the first conditional jump to be always jumping so patch over JZ, JE or anything by JMP, which is always jump no matter what.
Have fun...