mstsc control is fail
Re: mstsc control is fail
Yeah, another madCodeHook user already told me that there can be problems when the 3.1.3 and 3.1.4 drivers are running on the same PC. I'll have to look at why this happens and hopefully make 3.1.5 be compatible with 3.1.3 and 3.1.2 again.
Re: mstsc control is fail
Hi. madshi?
Is new release version 3.1.5 support mstsc compatible?
Is new release version 3.1.5 support mstsc compatible?
Re: mstsc control is fail
I've tried hard to find a way to make 3.1.5 compatible with *all* older madCodeHook version. But it simply wasn't technically possible, so 3.1.5 is now compatible to 3.1.3 and all older versions, but 3.1.4 is the one version which is not compatible. So you can mix 3.1.5, 3.1.3, 3.1.2, ..., but as soon as one software uses 3.1.4, mtsc will stop working correctly. I'm sorry about this. I hope that it will not be such a big problem in real life, because most people who updated to 3.1.4 are probably those who update quickly and regularly, so they're likely to update to 3.1.5 quickly, too.
Re: mstsc control is fail
Hi. madshi?
I have one question...
If mstsc is fail, then I need to search which dll is used madCHook library, and that used madCHook version..
How can I get information of which file used madCHook? and that version?
I have one question...
If mstsc is fail, then I need to search which dll is used madCHook library, and that used madCHook version..
How can I get information of which file used madCHook? and that version?
Re: mstsc control is fail
That isn't really possible, I think. The version number isn't stored anywhere in the dll/exe/sys file. You could try to find different code patterns in different versions somehow, but that would be rather ugly, I guess...