Search found 10755 matches

by madshi
Fri Jun 11, 2004 6:58 pm
Forum: madCodeHook
Topic: winsock hooking
Replies: 64
Views: 81399

I already told you why. :?
by madshi
Fri Jun 11, 2004 5:23 pm
Forum: madCodeHook
Topic: winsock hooking
Replies: 64
Views: 81399

Why don't you use the code I gave you? That one should work (if you use it right).
by madshi
Fri Jun 11, 2004 10:47 am
Forum: madCodeHook
Topic: Help About Winsock Hook
Replies: 2
Views: 7782

The hooking probably works. But your message sending will not work. Look, each running process loads a totally independent copy of your hook dll. When you call "GetParentHwnd" you tell the hook dll copy which is loaded in your own process where to send the message to. But all the other dll...
by madshi
Fri Jun 11, 2004 10:42 am
Forum: madKernel
Topic: Missing Constants in TPriorityClass
Replies: 1
Views: 4950

You're right, will add them, thanks for the suggestion!
by madshi
Thu Jun 10, 2004 7:58 am
Forum: madCodeHook
Topic: What all dlls to be included to main application for hooking
Replies: 20
Views: 23201

Which development system are you using? Delphi? BCB? MSVC?
by madshi
Thu Jun 10, 2004 6:24 am
Forum: madExcept
Topic: Is the option "pause all running threads" working?
Replies: 3
Views: 7398

The parameters of the exception handler callbacks have changed slightly: type TExceptActionEvent = procedure (action : TExceptAction; frozen : boolean; exceptObject : TObject; exceptAddr : pointer; crashedThreadId : dword; var bugReport : string; var screenShot : string; var handled : boolean );
by madshi
Wed Jun 09, 2004 8:58 am
Forum: madExcept
Topic: Is the option "pause all running threads" working?
Replies: 3
Views: 7398

If you're using VCL boxes (which you are seemingly doing) in an exception handler you must tell madExcept to synchronize your handler. You can do so by setting the second parameter to "true" when calling RegisterExceptionHandler. Have you set it to "false"?
by madshi
Wed Jun 09, 2004 8:56 am
Forum: madExcept
Topic: BUG in MadExcept
Replies: 2
Views: 6573

This might be a madExcept bug or not. It's hard to say. E.g. imagine that your program for some reason destroys the memory manager and then raise s an exception. madExcept can not work in that case anymore, because it needs a working memory manager. However, I recommend to download the latest beta b...
by madshi
Tue Jun 08, 2004 8:38 am
Forum: madCodeHook
Topic: WH_KEYBOARD
Replies: 1
Views: 5867

Well, keyboard input goes through the normal message APIs like GetMessage and PeekMessage. However, I really do recommend using SetWindowsHookEx for hooking these things. It's always recommended to use the official API - if there is one.
by madshi
Mon Jun 07, 2004 2:32 pm
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

Sounds really strange to me. I've no idea where the problem comes from.
by madshi
Mon Jun 07, 2004 1:59 pm
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

Hmmmm... Try this:

Code: Select all

PVOID testPtr;

testPtr = (PVOID) &GetForegroundWindowCallback;
HookAPI(..., testPtr, ...);
Do you then still get the warning?
by madshi
Mon Jun 07, 2004 1:28 pm
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

Try &GetForegroundWindowCallback. Don't know why MSVC should call your function instead of using the address, but who knows? The different might be that your function has no parameters, while in my demos all the functions have parameters. So maybe in my demos C++ knows that it isn't supposed to ...
by madshi
Mon Jun 07, 2004 11:36 am
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

First of all: There is no GetForegroundWindowA and GetForegroundWindowW, instead there's only a GetForegroundWindow. But that is most probably not the reason of the crash. HookAPI("user32.dll", "GetForegroundWindowA", GetForegroundWindowACallback, (PVOID*) &GetForegroundWindo...
by madshi
Mon Jun 07, 2004 10:50 am
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

Please post your full dll source code here.

The caller can be identified by using madCodeHook.GetCallingModule. That is, if you're interested in the module only. If you want to know more about the caller, you have to use inline assembler.
by madshi
Mon Jun 07, 2004 7:27 am
Forum: madCodeHook
Topic: unresolved external
Replies: 12
Views: 19468

In BCB when using madCodeHook.hpp you don't need InitializeMadCHook and FinalizeMadCHook.

BUT that's not the reason for the problem you're describing. Hmmm... Please try to add this to your project file:

#pragma link "madCodeHook"

Does that help?