Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Call Watcom 32 bit DLL from Delphi 16 bit

Posted on 1997-04-08
Medium Priority
Last Modified: 2013-12-03
I have a 16-bit Dephi Main program and I want to call a 32-bit DLL written in Watcom C.  The provider of the DLL used special Watcom Compiler feature to generate a Thunk DLL to handle the environment crossing, but it does not appear to work with Delphi.  The DLL writer doesn't have a clue since 'it works with other C main programs'.  They or I need help in getting this to work since they say it will take to long to recode their 32-bit DLL to 16-bit code, and will be less efficient.
Question by:jeffg2
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 15

Expert Comment

ID: 1334479
If you provide more information, may be...

1. How you call thunk DLL - at run time using LoadLibrary & GetProcAddress or at link time using LIB file?
2. How many functions exported by DLL?
3. What kind of work DLL does?
4. Is there any manuals for thunk DLL?

Writting your own thunk DLL is not simple, but possible.
May be better try to use provider's thunk DLL.

Author Comment

ID: 1334480
1. I use the standard Delphi method of calling the DLL which
creates a link at compile time, not LoadLibrary

2. 4 functions open, close, encode, decode

3. Voice compression/decompression

4. For now I cannot release info due to Non Disclosure Agreement.

Other info:

The DLL uses calloc() to create a block of storage upon
opening, and stores 32-bits of info (the flat address?)
in a Long whose address I provide in the open call.

The THUNK was written by the developer of the 32-bit DLL
using a special tool provided by Watcom.

Expert Comment

ID: 1334481
Please post headers for the C functions, and the 'external' declarations you use in Delphi.

If it works with 16-bit C, it also works with the Delphi. The only exception are functions taking variable number of parameters, which is a bit more tricky.


Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal


Expert Comment

ID: 1334482
Please post headers for the C functions, and the 'external' declarations you use in Delphi.

If it works with 16-bit C, it also works with the Delphi. The only exception are functions taking variable number of parameters, which is a bit more tricky.



Expert Comment

ID: 1334483
There are different thunking mechanisms, for the
different platforms 3.1, 95 and NT.  You need to know
which platform he created it for, and make sure that it
is the same as the one that you are using.  The different
mechanisms are mutually exclusive.

Author Comment

ID: 1334484
The Problem is solved.  Thanks for trying. For all of your info the problem was related to floating point traps.  Delphi enables them, most other languages apparently do not.  The DLL caused floating underflows which normally had no affect, but with a Delphi Main, caused a trap.

Case Closed.


Accepted Solution

Shrif earned 400 total points
ID: 1334485
You don't want to use the thunk compiler that's been so far discussed.  Here's why.  There are three types of thunking that has to do with 32-bit to 16-bit and vice versa calls: Generic thunking, Flat thunking and Universal thunking.  Universal thunking is for Win32s so we won't even go into that.  Generic thunking is a clean interface, first introduced with Windows NT 3.1.  It allows 16-bit EXE's to call 32-bit DLL's.  It does not, however, allow 32-bit EXE's to call 16-bit DLL's.  Generic thunking is available on all Win32 platforms (NT 3.1, 3.5, 3.51, 40 and Windows 95).  Thus, if you are attempting to call 32-bit DLL's from 16-bit EXE's, generic thunking is the best choice because: It is easier and the program will work with NT and Windows 95.  The third thunking method, flat thunking, is Windows 95 only.  It does not work under NT.  Flat thunking lets 32-bit EXE's call 16-bit DLL's AND 16-bit EXE to call 32-bit DLL's.  Flat thunking requires that you use the MIDL compiler to create proxy DLL's on both sides -- Assemlby code is created for you.  It takes a bit of doing to get right and requires that you be be able to link in objs and compile assembly.  So, for your application, it is best to Generic thunk.  I've done this to call 32-bit DLL's from VB3(which is 16-bit only).  Here's some sample code.  The following code was written to call the 32-bit DLL "kernel32.dll", function GetShortPathName so that I could convert a long pathname that the user entered into something a 16-bit program can use.  extern "C" {
      BOOL FAR PASCAL FreeLibrary32W( DWORD );
      DWORD FAR CallProcEx32W(DWORD nParams, DWORD fAddressConvert,
            LPVOID lpProcAddress, ...);

// GetShortPathName
extern "C" void WINAPI BezDeek( LPSTR lpszLongName, LPSTR lpszShortName )
      DWORD      ghLib = NULL;
      LPVOID      hProc;
      DWORD      dw;

      if( NULL == (ghLib = LoadLibraryEx32W( "kernel32.dll", NULL, 0 )) )
            MessageBox( NULL, "Cannot load Kernel32", 0, MB_OK );
            goto leave;

      if( NULL == (hProc = GetProcAddress32W( ghLib, "GetShortPathNameA" )))
            MessageBox( 0, "Cannot get procedure address", "GetShortPathNameA", MB_OK );
            goto leave;

      *lpszShortName = 0;
      dw = CallProcEx32W( 3, 3, hProc, lpszLongName, lpszShortName, 256L );

      if ( ghLib )
            FreeLibrary32W( ghLib );

} // BezDeek

See how much easier this is than flat thunks.  No extra files needed.  You just do it all in source code!Let me know if you have any more questions about this.  You should be able to get far with this.  If you don't, I can explain further.Shrif

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article surveys and compares options for encoding and decoding base64 data.  It includes source code in C++ as well as examples of how to use standard Windows API functions for these tasks. We'll look at the algorithms — how encoding and decodi…
A theme is a collection of property settings that allow you to define the look of pages and controls, and then apply the look consistently across pages in an application. Themes can be made up of a set of elements: skins, style sheets, images, and o…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question