On 10/07/2017 09:18 PM, Michael C wrote:
> I am following some examples online such as this one:
> https://social.msdn.microsoft.com/Forums/vstudio/en-US/ce0cc398-2b96-4688-b8a4-b5f4c9ebc064/memory-searcher-with-virtualqueryex-and-readprocessmemory?forum=vclanguage
>
>
> i think I got most of it
update:
I should have put down buffer = ctypes.c_double() instead of buffer =
ctypes.c_double.
Sorry all
On Sat, Oct 7, 2017 at 8:18 PM, Michael C
wrote:
> I am following some examples online such as this one:
>
I am following some examples online such as this one:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/ce0cc398-2b96-4688-b8a4-b5f4c9ebc064/memory-searcher-with-virtualqueryex-and-readprocessmemory?forum=vclanguage
i think I got most of it right, so this following part is what I would like
Oh I am trying to write my own memory scanner, because I thought the Cheat
Engine is pretty neat and I am just trying make one for myself.
Onto the problem, I think what happens with Readprocessmemory is that
BOOL WINAPI ReadProcessMemory(
_In_ HANDLE hProcess,
_In_ LPCVOID lpBaseAddress,
it might help if you mention what you are trying to do. if it is forensics,
there a bunch of python tools in that area. your problem may already have
solutions you could use.
On October 7, 2017 3:00:25 PM MDT, Michael C
wrote:
>Hi all:
>
>I am working on a
Or to put it better, I think, it's
How do I set up ReadProcessMemory, so that it returns a double instead of
129819721.
On Sat, Oct 7, 2017 at 2:00 PM, Michael C
wrote:
> Hi all:
>
> I am working on a memory scanner, and the source code and output is as
>
Hi all:
I am working on a memory scanner, and the source code and output is as
following:
Now, I know why my buffer from read process memory looks like values such
as "67108864" ; it's because I read into the buffer entire chunk of memory
at a time, because I fed read process memory this: