[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::lnx_apo

Title:LinkWorks APO
Moderator:HLDE01::SYSTEM
Created:Tue Feb 22 1994
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:476
Total number of notes:1817

460.0. "Calling 16-bit DLL from 32-bit LNX client" by TAKEOF::STEIGER () Thu Feb 06 1997 14:19

The Problem is, I want to use an applet from the SDK (Drivemanager) which is
a 16-Bit Dll with the newest 3.08 32-Bit LNX Client.
(I tried this because I thought it will work with the new Call16.exe)
But the result is, when I activate the Drivemanager (Drag and Drop an object
over the drivemanagericon) the whole LNX-Client failed (not responding).
The Dll is running somewhere in the background, but the error-windows appear
not till I close the LNX-Client. 
The error messages are : one time ->General Error, two times ->Object not
found
and last ->No Drive Manager class defined for.
How can I use this 16-Bit SDK-applet with the 32-Bit LNX Client?

Thank you for your reply ....
Christoph

T.RTitleUserPersonal
Name
DateLines
460.1call16.exe should work for the SDKGENIE::16.184.48.153::genie::tschanzWed Feb 12 1997 11:1111
Hi

I don't believe that call16.exe is only for the 16bit TL Integration.
Read the Release Notes on page 39, please.

16-bit DLL calls from class programming now also works for the Intel client.
As a consequence you can now use the 16-bit LinkWorks SDK with the 32-bit client.

Let me know wy thas the drivemanager not works, please.

Toni