AOB scan doesn't seem to work well on 64 bit address. about memory.dll HOT 4 CLOSED

Hi, I was actually doing a little bit of research on ReadProcessMemory, 64 bit Windows, 64 bit apps, etc.

Now what I did was besides uncheck "Prefer 32-bit", and given my scope and expectations for my current work, is set the target platform to be 64 bit in the dropdown menu above the checkbox you've indicated.

Then, I followed this solution
and this information.

Now, the answer in the first link is provided by bogza.anton and I would like to note that rather than replacing int lpBaseAddress with Int64 lpBaseAddress, it might be reasonable to actually use a UInt64 instead (since memory addresses shouldn't go negative).

Basically, if you're using 64 bit Windows, importing from kernel32 will give you functions that should be compatible with 64 bit programs. You just need to change the imported function's signature.

In this way, I was able to get a dll import to work properly with my 64 bit app to read a 64 bit game's memory.

I predict that this solution would also be extendible to this project as whole, such that if you modified the source from int address parameters to UInt64 address parameters and recompiled the library, there would be little to no issue. Haven't tried it myself quite yet, but my excitement for this solution and initial results prompts me to post before I forget.

from memory.dll.

Fork the source, make changes, and send me a push request.

from memory.dll.

Just merged hollow87's aobscan improvements. Try them out.

from memory.dll.

Closing issue because errorc0de404 isn't responding.

from memory.dll.