Re: System-wide hooking, VB+ASM

"J French" <erewhon@xxxxxxxxxx> wrote in message
news:42a416b7.91305276@xxxxxxxxxxxxxxxxxxx
>
> It looks as if you are saying that a DLL need not have an entry point.
>
> Somehow I doubt that, if an /explicit/ entry point is deleted then the
> compiler (or maybe the linker) would supply an implicit entry point.
>
> Or more likely the 'implicit' entry point looks for the 'explicit'
> entry point and calls it if it is not Null.
>
> Have a look at www.masm32.com
> and download their programming kit

Wrong. I avoid saying "Wrong" like that and I seldom do. In this situation,
you have said something incorrect and I have replied by stating what is
correct. You still insist I must be wrong, therefore I must escalate by
stating explicitly that you are wrong.

A DLL is just a bunch of functions. They don't have to have anything in
common except their existence in a linked file (DLL). The functions don't
need to make an application; usually they don't. A DLL is a lot like a BAS
file to the extent that the contained functions do not need to be related. A
BAS file can contain arbitrary functions (and subs) that can be called
independently of each other, and so can DLL functions be independent of each
other.

That is why it is important to have a term to refer to "Regular DLLs" and
why it is often difficult for VB programmers to undestand what they are.

> You'll find that the DLL example is actually an EXE and the last line
> is:
> End LibMain
>
> Which is the standard way in which one determines the entry point of
> an EXE or a COM

Yes, I am familiar with the "End" statement in assembly language. I have
also programmed using the assembler for IBM 360 style processors and I think
the assemblers for 808x style processors (including Pentiums) are using the
"End" statement in assembly language in the same way that the IBM 360
assembler did nearly a half century ago.

You probably don't realize that in that context "COM" has a meaning very
different from what you think. In that context, a COM file is totally not an
ActiveX think nor anything OLE. I hope someday you can laugh at how far off
you are.

You really are shooting from the hip, with poor aim. I am sorry for being
that extreme, but it seems important to emphasize that you need to be more
careful about saying things you are unfamiliar with.


.

Relevant Pages

  • Re: System-wide hooking, VB+ASM
    ... >> standard entry point. ... >DLL entry point. ... >without any source code generated, another is a project with a simple DLL, ... >generated for the simple DLL does have a skeleton DllMain and that is all ...
    (microsoft.public.vb.winapi)
  • RE: Web Part Unsafe
    ... DON'T strong name your assembly, remove the old dll from the GAC, ... I add an entry to the webconfig in the wwwroot. ... > on it so there may be configuration issues. ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: ie6sp1 : Repair Function Blocked - Anyone know of a fix?
    ... > - problem no entry point for DllRegisterServer ... Evidently those switches have an order dependency. ... Otherwise there should have been no mention of DllRegisterServer ... >>> the application and using it to register or unregister your COM DLL" ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Detect if a DLL is an MFC Extension DLL
    ... Your ANSI version has all the entry points that require strings suffixed with A. Your ... #define DoSomethingToThisString DoSomethingToThisStringW ... Then, at least, if they try to load the wrong DLL they won't be able to because the entry ... entry points with suffix-W or suffix-A names. ...
    (microsoft.public.vc.mfc)
  • Re: win32 or native NT windows API
    ... A Windows DLL call is an ... The call gate specified by this selector ... learning assembly programming than the DLL calls in Windows. ... But in a "normal" Windows assembler program the user never calls the OS, ...
    (alt.lang.asm)