Quote:
|
Originally Posted by Annibal
. . .
There is something i'm not taking in consideration? Since the dll is mapped into memory along with the exe that load it the address should not be correct?
Sorry i was a little long but some time problems are from little details :P
Thanks you
|
Hi. I think you are having trouble with the idiosyncracies of the memory patcher.
Apparently your test.dll is not loaded into memory by the time the patcher has frozen the main exe module (Before the winmain call) and when it looks looks for the dll is not mapped yet. Alternatively, the .dll gets loaded at a non-constant area in memory each time (does happen every now and again) so the dll patch lands in the wrong module.
A first approach would be to try different loader-patcher(s), hoping they are more forgiving about dll load timing and relocation mechanisms.
The fool proof solution is to code your own loader/patcher. IT IS NOT THAT DIFFICULT. Search around and you will find plenty of tutorials and theads about it.