Re: Enumerating 32-bit modules from 32-bit processes in WOW64

"Jochen Kalmbach [MVP]" <nospam-Jochen.Kalmbach@xxxxxxxxx> wrote in message
news:OxMdiXKcFHA.3504@xxxxxxxxxxxxxxxxxxxxxxx
>
> Maybe the the fact that some names have the sysWow64 path inside the
> names is becuase of the way the DLL is loaded (maybe is it is inidrectly
> loaded, the OS will have to find the correct one... and then it will use
> the sywow64-directory). But this is just a assumption.

Hi Jochen,

I think that's a good assumption that this has to do with compatibility.
This is one of those cases where I didn't find the "backwards compatibility
directive" to be an intuitive thing. And looking at a list of loaded
modules for a couple of apps, the DLLs that point to "system32" do seem to
be ones that tend to be loaded explicitly rather than implicitly. The core
Win32 libraries point to syswow64 (KERNEL, USER, GDI), as do a few others.
NTDLL points to system32, but then that library is probably a special case.
The libraries that I'm loading explicitly (wtsapi32, iphlpapi,
ws2_32/wsock32) point to system32.

I'll probably invest a little time to check this out in more detail, but
this behavior may prove to be useful if it provides an indication (even it's
not a guarantee) of how a 32-bit DLL was loaded.

Thanks,

Philip Sloss


.

Relevant Pages

  • Re: How to get imagebase after a DLL gets loaded
    ... The main difference between DLL and static library in this context is ... so that it is not meant to be integrated with the client code ... SPEAKING ABOUT STATIC LIBRARIES HERE, AND I *EXPLICITLY* SAID IT THIS ...
    (microsoft.public.win32.programmer.kernel)
  • Re: How to get a .lib from .dll
    ... Using the Borland tools, you should first run "IMPDEF" on the DLL file ... information in it to create ".LIB" import libraries with;)... ... from Windows version to Windows version...so, ...
    (comp.lang.asm.x86)
  • Re: How to get a .lib from .dll
    ... Using the Borland tools, you should first run "IMPDEF" on the DLL file ... information in it to create ".LIB" import libraries with;)... ... from Windows version to Windows version...so, ...
    (alt.lang.asm)
  • Re: How to get imagebase after a DLL gets loaded
    ... During the process of building the DLL, ... Implementing a library that requires users of the library to instantiate ... predict what variable name you will use at initialization time. ... Some third-party libraries DO require that you instantiate a pre-defined ...
    (microsoft.public.win32.programmer.kernel)
  • Re: DLL and external references
    ... On Windows a DLL is not its own ... > other static libraries. ... > involved and intricate and creates a huge DLL (the original EXE, ... you need to create all those libraries ...
    (microsoft.public.vc.language)
Loading