🚀 go-pugleaf

I am trying to port an OS/2 1.3EE app. to OS/2 2.0 using C Set/2. I have
picked up a file called "acdi32.h" from IBM which contains the necessary
definitions to access ACDI from a 32-bit app. If I use load-time linking
to \cmlib\dll\acdi.dll, my requests work fine. However if I use run-time
linking (via DosLoadModule and DosQueryProcAddr) my requests fail. I have
used IPMD to step through test cases I wrote for both load-time and run-time
linking and have discovered a peculiar thing. I have found that if I use
run-time linking, the 16-bit address for ACDI gives an offset of 0x0000 but
if I use load-time linking, the offset is 0x003a. The two entry points
have similar prolog code except that the run-time link version does *not*
store the passed ACDI parameter block pointer into local storage (I believe).
After the prolog, the two entry points merge to the same address. As a
result, the parameter block that I pass (via a pointer) to ACDI does not
get affected when I use run-time linking to ACDI.DLL. From what I can
determine, DosQueryProcAddr() seems to be returning the entry point for
a routine called RAAMNGR rather than for the ACDI entry point I requested.

I am using the GA version of ACDI.DLL dated March 5/92. Has anyone been
able to successfully run-time link to this DLL in a 32-bit app? Is there
a later version of ACDI.DLL out there? Anyone know when IBM will finally
get around to a 32-bit version of ES?

Responses via E-mail are preferred. Thanks...
-- 

Craig Knelsen		craig@phenix.cc.uregina.ca
			Craig_Knelsen@f20.n140.z1.fidonet.org