Re: System-wide hooking, VB+ASM

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Sun, 5 Jun 2005 19:05:25 -0600, "Jonathan Wood"
<jwood@xxxxxxxxxxxxxxxx> wrote:

>J French,
>
>> Absolutely - although I doubt that COM is responsible for loading the
>> run time library

>I suspect the runtimes have their own initialization code which, among other
>things, initialized COM.

I suspect that COM is little more than an embellishment of SendMessage

That darn runtime has to be initialized by something, I can't believe
that it is not triggered by the DLL loading

>> >Based on some testing and some discussions, I'm finding that this appears
>> >not to work in VB6. I can install the hook, but as soon as keys are typed
>in
>> >another process, the hook appears to stop working even for the original
>> >process.
>>
>> Misunderstanding - that is what happens to me too
>> - with some spectacular crashes

>These don't sound like the same things to me. For me, the hook simply
>doesn't do anything any more, even if I activate the original application.
>If you activate another application and it crashes when you start typing,
>that tells me that your hook is indeed being called.

My suspicion also - I suspect that you are using a later OS
- for obscure reasons I use my old W95 box and only test on W2k and XP
(I can't stand my later machines)

>Again, try the same thing with VB6 if you can, I suspect the crashes will
>not occur if you do.

I suspect that depends on the version of the OS rather than the
version of VB - but I'll consider that approach
.

Quantcast