Re: LoadLibraryEx (as datafile) and MorIcons.dll - extracting icons

"R.Wieser" <address@xxxxxxxxxxxxx> wrote in message
news:eVyYWBdYFHA.2588@xxxxxxxxxxxxxxxxxxxxxxx
>> LoadLibrary() has been a part of the Windows API since version
>> 2.something
>> of more than a dozen years ago.
>
> Yes, I (ofcourse) found that entry too. Alas, the function description
> starts with the lines :
> "<lpLibFileName>
> Points to a null-terminated string that names the Win32 module (either a
> .DLL or .EXE file)."
> And somehow that makes me think that this function does not like 16-bit
> modules either ... :-)

What? At the time the documentation for Windows 2.x was written there was no
publicly available Win32 API or SDK. In my copy of the 16 bit SDK that cam
with Visual C++ v1.5 circa 1994 or so the help entry for the function states
this:

<quote>
The LoadLibrary function loads the specified library module.
</quote>

Note the absence of the word Win32 to qualify the type of module.

>> I think you are missing the point make that there are multiple standards.
>> You can access those files as well as Windows can or anything else can.
>
> I beg to differ ...

That's certainly your option. However, it has_never_ been possible load 16
bit components in a 32 bit application that runs on NT/2K/XP/2K+3 (or
Longhorn when it arrives). On '9x it is possilble to use thunks but it is
not easy to do and if I remember correctly requires the thunk compiler (I'm
not sure if it is still available) and an assembler which for most
developers is a distant memory.

>> All you need to do is make the access in a 16 bit application that
>> makes use of the 16 bit API.
>
> ... that's what I call a(n unpractical) "work-around".

Such is life. This link provides some information on thunking (only an
option on '9x)

http://support.microsoft.com/kb/125710/EN-US/

> Furthermore, as mentioned in the above, there seems to be no 16-bit
> "LoadLibrary" available (Can't find it in any of my include-files, or
> other
> documents I have).

Right. You need the SIXTEEN BIT SDK. It is bigger than a breadbox and
TOTALLY separate from the 32 bit SDK which is totally separate from the 64
bit SDK.

> Thanks for your response though.

You are welcome.

Regards,
Will


.

Relevant Pages

  • Re: Is VS2008 a good environment?
    ... Windows provides you an API called Win32 for usermode applications. ... Making a shim between "static" function and a proper member function is very ...
    (microsoft.public.win32.programmer.ui)
  • Re: serielles Modem ansprechen ( AT Befehle )
    ... Falls das Modem korrekt bei Windows angemeldet ist, ... dann Verbindungsaufbau im Prinzip über das Win32 'TAPI' API (siehe MSDN) ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)
  • Re: Suggested base class additions
    ... If you think of Dolphin as primarily a Smalltalk-flavoured front-end to Win32, ... then it'd seem quite natural to have all the API wrapped/exposed. ... on Windows, then the less you see of the Win32 cesspit the better. ...
    (comp.lang.smalltalk.dolphin)
  • Re: May I introduce myself to cobol?...
    ... a clarification on what the win32 API ... meaning "Application Programming Interface", ... in the context of the OS Windows ...
    (comp.lang.cobol)
  • Re: Some questions; SHMenuBar, multilingual prog
    ... It's possible that any given API is specific to a given device or class ... > SHCommandBar, whatever that is, is not in our SDK or in the PocketPC SDK, so ... > it must be specific to some other device (or isn't a Windows CE API ... menu resource. ...
    (microsoft.public.windowsce.embedded.vc)