Re: API-hooking question [SOLVED!] :)
Posted: Mon Sep 21, 2020 5:37 pm
chi, thank you for clarification. I just tried to follow a rule: if EjectDLL-procedure is provided, then it should be called before exit. Otherwise, it is unnecessary(pointless). There is no call this procedure from anywhere else in the program. But... just a moment... This is not a reserved/service name like DetachProcess, which is called automatically at the end. In other words if target process died, then everything else along with it. No need to care/worry about leak resources, random bugs in the future etc. Sorry for the tediousness. It's just haven't logic. Have a code which is just a ballast.
Your opinion is important for me because you fixed engine(this is stated in the header). And probably you know its mechanism well.
Also I don't want it to look like a conversation between two people(chat). Perhaps this is interesting only for me. It is also possible that other serious forum members receive a notification after each new message.
Therefore, if you don't want to reply, then I will understand it.
Thanks for everything anyway!
I already understood it, but now it contain nothing(only beep). If this can be called from the DetachProcess-procedure, then *func pointer must be sent to the DLL(result of calling InjectDll).The dll gets automatically detached when the program exit (DetachProcess).
Your opinion is important for me because you fixed engine(this is stated in the header). And probably you know its mechanism well.
Also I don't want it to look like a conversation between two people(chat). Perhaps this is interesting only for me. It is also possible that other serious forum members receive a notification after each new message.
Therefore, if you don't want to reply, then I will understand it.
Thanks for everything anyway!