Re: System-wide hooking, VB+ASM
- From: "Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx>
- Date: Wed, 1 Jun 2005 09:44:49 -0600
Paul,
> You may be able to find any number common attributes, in particular
because we're talking about a
> type of Windows PE, specifically a DLL.
Exactly.
> However, for whatever reason, you seem to want to
> marginalize the differences in the implementation between a COM and
non-COM DLL.
No, I just know that adding COM functionality to a DLL does not change the
underlying architecture. It only adds something more.
> I think it's rather obvious that an ActiveX DLL doesn't implement the same
standard Windows DLL
> calling convention.
Well, the underlying architecture implements exactly that when exporting COM
functionality. Only by using a high-level language such as VB is that hidden
from us.
At any rate, I think this dead horse has been beat enough.
For this thread, it was stated (not by you) that VB DLLs could not be used
for system-wide hooks because they were not regular DLLs. Certainly, in that
context, the statement is false.
--
Jonathan Wood
SoftCircuits
http://www.softcircuits.com
Available for consulting: http://www.softcircuits.com/jwood/resume.htm
.
- Follow-Ups:
- Re: System-wide hooking, VB+ASM
- From: Sam Hobbs
- Re: System-wide hooking, VB+ASM
- From: Paul Clement
- Re: System-wide hooking, VB+ASM
- References:
- Re: System-wide hooking, VB+ASM
- From: Paul Clement
- Re: System-wide hooking, VB+ASM
- Prev by Date: Re: System-wide hooking, VB+ASM
- Next by Date: Re: Can VB Create a Regular DLL?
- Previous by thread: Re: System-wide hooking, VB+ASM
- Next by thread: Re: System-wide hooking, VB+ASM
- Index(es):
Relevant Pages
|
Loading