Pete O'Hanlon wrote: Although I'd be really surprised if something got moved that quickly. Here you go, got chased into oblivion in no time, although it doesn't look too hard to solve. =/ I explained it thoroughly, gave my code, and it's a pretty specific question. Is it possible this topic has been assaulted by a... page-tsunami? (DUN DUN DUN...) http://www.codeproject.com/script/Forums/View.aspx?fid=1649&msg=2440450[^] I can see alot of other no-replies-topics at pages higher than 25 or so. Those are all victims of the Codeproject-Forums-don't-want-you-to-bump-dictatorship. ;)

Dave Kreskowiak wrote: You can't say I didn't warn you. My way works for any game I tried, except one little unknown game, and only when you choose OpenGL as its rendering. So actually it works very well. You were saying, "did you ever try it on an DirectX window", yes I did, with several games, and it all works perfect. You don't seem to be able to explain me why it doesn't work for that one certain game when I choose OpenGL, but still works when I choose DirectX 8 or DirectX 5, or that it works with every other game I tried. Anyone else knows what's the reason for this?

Alright, seems the GC isn't 100% perfect yet. Thanks for the reply.

Thanks, hehehe. I'll just try to make a monitoring program first then, that logs what changes in memory. Then I can see what action changes which addresses. Yes I will be making addons programmed in C#, applied to native code programs (as far as I know).

I tried the example you gave, and it gives exactly the same result as my code. Hehehe, it seems my code was just totally perfect. Apparently many processes in Windows have certain pieces of their allocated memory identically. Is it some Windows-header or so? Anyway, I tried some other more unusual processes, like winlogon.exe (some Windows process), and he just gives something else. And I also tried some other memory positions alot further than 0xFFFF, like 0x20083, and that gives results different from process to process. Just got unlucky to try the wrong processes at the wrong places. Edit: I suddenly notice I actually succeeded reading the memory of a windows process (winlogon.exe), it didn't work after I tried it again... :wtf:

Thanks alot for the information, looks very interesting indeed. I'll check it out. :)