Originally Posted by Jason
Actually, that just proves my correctness even more. In case you weren't aware, a char holds a value from 0-255....OMG SO DOES A BYTE. If you learned how memory was actually stored and interpreted you might have understood the connection. My code works fine on my 64-bit computer lol.
Take a look at the proper PINVOKE declaration:
pinvoke.net: writeProcessMemory (kernel32)
I please you to learn how memory works, how it's stored and the relationship between bytes an any variable lol, you're really just embarrassing the fuck out of yourself haha. I don't know what's proving so hard to understand, but that's really not my problem any more.
Now, just before you refer me to the C++ declaration of WPM from Windows.h, look at this -.-
Code:
BOOL WINAPI WriteProcessMemory( __in HANDLE hProcess, __in LPVOID lpBaseAddress, __in LPVOID lpBuffer, __in SIZE_T nSize, __out SIZE_T *lpNumberOfBytesWritten );
PLEASE FUCKING LEARN HOW MEMORY WORKS. An int is really 4 bytes in memory, do you thing that any function that takes an int is wrong because you're passing an array of 4 bytes to it? NO! Jesus christ use your brain.
OMG, i know what bytes are and I know how memory works, might even know it better than you. int is 4 bytes DWORD is unsigned int, The Bytes for those are backwords in memory Bla Bla BLA, Bytes are Opcodes for Assembly Language and memory just reads those bytes and stuffy stuff.I have to know those things when making Detours and stuff in hacks. Thats not the point i was trying to make.
Since your going so wrong and strong I will let you go. I am working on new ways of injection
