I recently noticed that when bypassing the moment of saving the changes the executable detected it as a Trojan of type "Wacatac.H!ml" it worked on the original SRO_CLIENT without modifying the test client and it is not manipulated in any way since it It gives the error only after applying the patch through ollydb
I use these parameters:
I use these parameters:
My question is if there is any other method or some other type of patch to avoid this problem.;)Quote:
Xtrap 1st Check = 00831B20 (Replace With RETN)
Xtrap 2nd Check = 00B7AEF0 (NOP Untill Address) 00B7C3EF