16-bit DLLs usable from CallDll?

[dsavitsk]

i found calldll really unstable for old stuff like this.  i think the best
plan is to write an activex wrapper in vc++ or delphi ... or even in vb.
then just use win32com.client.Dispatch('') ... hey, wait, this is what neil
said below isn't it?

-d


"Aaron Freeman" <afreeman.newsgroups at emprise.net> wrote in message
news:3hb74u8rt61c2klrf9tpkut963531s1bdh at 4ax.com...
> I spent an hour or so on MSDN, and it seems that 'voodoo' might be
> putting it lightly.
>
> Unfortunately, the DLLs that I have date back to about '91 (wrappered
> DOS libs, I think), and are part of a very closed and very dead
> system.
>
> I was able to use quickview and exehdr to get a function listing, and
> I was planning on forcing my way through the rest with some time and a
> hex editor...
>
> A long shot, I know, but any advice would be much appreciated.
>
> -Aaron
>
>
> On Tue, 15 Jan 2002 04:07:25 GMT, "Neil Hodgson"
> <nhodgson at bigpond.net.au> wrote:
>
> >Aaron Freeman:
> >> 1) After some experimentation, and purusing of this and other groups,
> >> it appears that CallDll doesn't support 16-bit DLLs.  Am I missing
> >> something?
> >
> >   Thunking from a 32 bit process down to 16 bit functions is deep voodoo
> >and there are major differences between Windows 95 + descendents and
Windows
> >NT.
>
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win32/tc_0
c
> >z6.asp
> >
> >   For most situations, I'd recommend instead creating a separate 16 bit
> >program that does the calls and communicate through COM or a pipe or
> >similar.
> >
> >   Neil
> >
> >
>