My thinking is too divergent to desire becoming a coder. My intrinsic motivation is in optimizing the user experience, and discovering new, original solutions to existing use cases. My work is in innovation so I am really interested in the solutioning but less in the coding and debugging.Quote:
its actually not really worth trying to utilize but if u want to you can use the pattern given a few messages ago in olly or ida… and attach gw.exe to one of the debuggers and choose gw.exe's executable area and do a binary search for that pattern....
once its found go to the byte before it and offset -3 or 3 bytes before that and that is where the pattern leads ---
you can then move forward the toolboxes E hex or 14 decimal place forward from that spot and you will be at the byte before their pattern which will then follow "5d e9 -- 4 bytes that are unreliable and should not be used in patterns then 55 8B EC 53"
like I said nothing to utilize and that its useless -- plenty of youtube videos on how to use these debuggers and its worth watching them if you want to be a coder
ok yeah their scanner can scan past the unreliable bytes and still find the pattern - I know and it can easily be written - but its not needed and was most likely written like this to thwart the community.
I am upper grateful to everyone who does the API work, If anyone is interested in lending me their math, I have some ideas for new functions that I know would take me way too long to code but would be really neat and useful.