View Single Post
  #35    
Old January 9th, 2013 (04:08 PM).
thjenvuongxh thjenvuongxh is offline
 
Join Date: Mar 2012
Gender: Male
Posts: 23
I have a good and a bad notice:

First the good:
writebytetooffset 0x3F 0x4000048
writebytetooffset 0x1F 0x4000049
writebytetooffset 0x41 0x4000050
writebytetooffset 0x3F 0x4000051
writebytetooffset 0xF 0x4000052
writebytetooffset 0xA 0x4000053
writebytetooffset 0xFF 0x20377DC
writebytetooffset 0xFF 0x20377DD
writebytetooffset 0x0 0x20377DA
writebytetooffset 0x0 0x20377DB
writebytetooffset 0x0 0x20377DE
writebytetooffset 0x0 0x20377DF
writebytetooffset 0x0 0x20377EC
writebytetooffset 0x0 0x20377ED
writebytetooffset 0x0 0x20377EE
writebytetooffset 0x0 0x20377EF
writebytetooffset 0x0 0x20377F0
writebytetooffset 0x0 0x20377F1
writebytetooffset 0x0 0x20377F2
writebytetooffset 0x0 0x20377F3
writebytetooffset 0x0 0x20377F4
writebytetooffset 0x0 0x20377F5
writebytetooffset 0x0 0x20377F6
writebytetooffset 0x0 0x20377F7

But the bad is that there a scoundrel ASM ROUTINE that inserts
others bytes in this location after the script!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

This requires a ASM routine that check the offset in 0x8471DEC.


LETS GO!!!
Reply With Quote