Getting info from Game Process Memory

[RagnaBaby]

Any of you coders here could help me out?

From my program, I'm trying to retrieve/get the SERVER_NAME of the memory of the game. Ex, Conquer-online's Conquer.exe

ReadProcessMemory() could help, but still it confuses me.

Anybody can share detailed info about this?

[neji]

u could use a sniffer to intercept the "connect" packets...there you will see the ip adress or hostname of the server the packets shall arrive

[Maybe It's Maybelline]

Originally posted by neji@Apr 11 2006, 08:44
u could use a sniffer to intercept the "connect" packets...there you will see the ip adress or hostname of the server the packets shall arrive

But to minimize the useage of not needed resources I wouldn't
use winsock, since It's probably not needed for his further actions.
I also would like to find a solution for this, since I have not much expirience
with memory editing.

[neji]

@Ragna: what do you plan to do with this information?

[Maybe It's Maybelline]

Probably if you go ingame there will be an offset showing the server's name, so perhaps he want to echo now the name in his programm or change it.

[RagnaBaby]

I'm just trying to retrieve the SERVER_NAME of which the game is connected. Sniffing doesnt work, all servers were connected on one ip address/port.

Finding the offset could be. But I still need more information in the whole process. Specially I'm trying to read a string of memory. I'm a lil bit experienced on C++. But not on this field yet.

More likely, on some tutorials, Injecting is what's done. Or even the others need that I'm the one who CreateProcess(). But I'm trying to do these from an already running app.

@neji: simply retrieve the servername, nothing else. More on learning stuffs.

Tnx

[neji]

then ReadProcessMemory will do what you want

The ReadProcessMemory function reads memory in a specified process. The entire area to be read must be accessible, or the operation fails.

BOOL ReadProcessMemory(

HANDLE hProcess, // handle of the process whose memory is read
LPCVOID lpBaseAddress, // address to start reading
LPVOID lpBuffer, // address of buffer to place read data
DWORD nSize, // number of bytes to read
LPDWORD lpNumberOfBytesRead // address of number of bytes read
);


Parameters

hProcess

Identifies an open handle of a process whose memory is read. The handle must have PROCESS_VM_READ access to the process.

lpBaseAddress

Points to the base address in the specified process to be read. Before any data transfer occurs, the system verifies that all data in the base address and memory of the specified size is accessible for read access. If this is the case, the function proceeds; otherwise, the function fails.

lpBuffer

Points to a buffer that receives the contents from the address space of the specified process.

nSize

Specifies the requested number of bytes to read from the specified process.

lpNumberOfBytesRead

Points to the actual number of bytes transferred into the specified buffer. If lpNumberOfBytesRead is NULL, the parameter is ignored.



Return Values

If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
The function fails if the requested read operation crosses into an area of the process that is inaccessible.

Remarks

ReadProcessMemory copies the data in the specified address range from the address space of the specified process into the specified buffer of the current process. Any process that has a handle with PROCESS_VM_READ access can call the function. The process whose address space is read is typically, but not necessarily, being debugged.
The entire area to be read must be accessible. If it is not, the function fails as noted previously.

msdn down , so I post the whole text instead of a link

[RagnaBaby]

Ehe. As I said, I know about the ReadProcessMemory thing. Anyway, I've got it going already, thanks for your time.

I'm now more focused on getting the offsets, still trying to get used to this.

Again, Thanks alot

[neji]

you can loop through memory using VirtualQueryEx. Then you can read out the allocated pages by using ReadProcessMemory and retrieve the adresses.