ProcMem reading data as 4 bytes as apposed to text.

I wasnt procmem's Read method to return text, instead it is returning 4 byte type.
In cheat engine, the 4 byte type is what Mem.Read returns. I want the cheat engine text type.

Originally Posted by Tezuni

I wasnt procmem's Read method to return text, instead it is returning 4 byte type.
In cheat engine, the 4 byte type is what Mem.Read returns. I want the cheat engine text type.

Maybe you should understand how stuff is stored in the memory.
The RAM doesn't give a shit if it is an integer or text, each bit is simply 0 or 1.

A normal string is stored as an array of characters so if you have your offset you first read 1 character, then you read the second one by reading address + sizeof(char), then the third etc... Or you just read the string into a buffer at once.

Originally Posted by Merccy2

Maybe you should understand how stuff is stored in the memory.
The RAM doesn't give a shit if it is an integer or text, each bit is simply 0 or 1.

A normal string is stored as an array of characters so if you have your offset you first read 1 character, then you read the second one by reading address + sizeof(char), then the third etc... Or you just read the string into a buffer at once.

So happy seeing you again in the forums . You are the true legend !

u need to compile first

Originally Posted by Merccy2

Maybe you should understand how stuff is stored in the memory.
The RAM doesn't give a shit if it is an integer or text, each bit is simply 0 or 1.

A normal string is stored as an array of characters so if you have your offset you first read 1 character, then you read the second one by reading address + sizeof(char), then the third etc... Or you just read the string into a buffer at once.

Thank you, proofreading the OP this morning made me cringe. You have seem to understand my question which was how I could take the raw data that ProcMem's Read function returns, and convert each charicter to its Ascii equivalent.

Originally Posted by Merccy2

The RAM doesn't give a shit if it is an integer or text, each bit is simply 0 or 1.

This is fundamentally incorrect. Ram has no shits to give, as it is a piece of plastic and wires.

- - - Updated - - -

Originally Posted by Kapataine

u need to compile first

ty, fixed my problem!

Originally Posted by Tezuni

Thank you, proofreading the OP this morning made me cringe. You have seem to understand my question which was how I could take the raw data that ProcMem's Read function returns, and convert each charicter to its Ascii equivalent.

This is fundamentally incorrect. Ram has no shits to give, as it is a piece of plastic and wires.

- - - Updated - - -

ty, fixed my problem!

Its fun how you ignore the point I make by trying to out smart me.

Data types are just convention, if you have 4 bytes it can be an integer, a float, a pointer or a character depending on the encoding, you chose.

Fun thing if you wan't to convert an ascii number to an integer you can do the following (which should also give you enough understanding about the solution for your problem).

Code:

char key = '8';
int keyDecimal = int(key - '0'); // or (int)(key - '0') which is syntactic sugar for the first.

Originally Posted by Merccy2

Its fun how you ignore the point I make by trying to out smart me.

Data types are just convention, if you have 4 bytes it can be an integer, a float, a pointer or a character depending on the encoding, you chose.

Fun thing if you wan't to convert an ascii number to an integer you can do the following (which should also give you enough understanding about the solution for your problem).

Code:

char key = '8';
int keyDecimal = int(key - '0'); // or (int)(key - '0') which is syntactic sugar for the first.

Im not trying to outsmart you, I accept the fact you are more skilled and intelligent than me. I simply thanked you for your help, then I made a joke. Again thank you for a more in depth explanation.

problem: procmem

solution: not using it

ProcMem reading data as 4 bytes as apposed to text.

Post a Reply

Similar Threads

Tags for this Thread