Sorry to ask about a topic that I'm sure was hashed over many many times in the past on the forum but since some prepubescent jerkoff hacked the forum the links I found are mostly dead on the subject.

I was wondering how we accomplish memreads and writes to running processes in C++. I do them in ACTools np but have not found the command/function in C++ that would allow it. I know how to set a pointer but couldn't find out if there was a way to assign the pointer to a specific mem address rather then saying "heres what I want it to point to ___" and having it point to that item. Ideally I would like to write a mem read/write dll to call from several different projects/applications.

Part of my problem I know is that I do not yet have a C++ book so am working from the help file, online references, and a intro to C++ teachers class lectures. I haven't needed a book for class since I have worked with at least of half dozen languages and variants of them in the past but it's biting me now on private projects. If anyone knows a particularly good reference for C++, preferably with info on mem and writing/accessing dll's, please let me know as I am shopping for one now.

If it makes a difference or helps the compiler I am using at the moment is the bloodshed Dev-C++ compiler from sourceforge.

Any information or links that are not dead to where I can get the information would be greatly appreciated.

They're WIN32 API calls so, best place to find them is on MSDN

WriteProcessMemory
ReadProcessMemory

Hope that helps

http://www.daniweb.com/techtalkforums/thread4909.html

This is how to prevent you from doing what it is you are trying to do, I think, but it went over my level of i86 competency that is for sure.

HEHE Thank you so much guys, looks like I'm in for a crash course of windows API. I wasn't planning anything as ambitious as hooking whole sections of code but it might be usefull down the road if the hooking uses less resources then running a seperate application which just calls occassionally for mem reads/writes. Also not sure whether it is worth hooking sometimes because of the issues with multiple hooks into the same program interfering with each others operation.

Thanks again for the info.

No problem.