🚀 go-pugleaf

We are developing a set of applications that make use of several different
DLL's to share common code.  We frequently encounter problems when one of
the applications or even a DLL itself has not been linked with the most 
current version of one of these DLL's.  When this happens the application
will terminate silently; no error message, just return to the command prompt.
You are faced with the problem of figuring our which piece out of all of
these components is out of sync.

We have even found that if you don't link with the right combination of
the IBM supplied DLL's, dde4mbs[i] and dde4mbm[i] you can get into
the same situation.

Can someone explain exactly what fails during image activation that causes
this "silent" failure?

Is there not some way that a developer can get more information about
what the incompatibility is?  Problems of these sort continually cost
developers significant amounts of time.  It's just one more of the things
that makes almost all the developers here loathe OS/2 as a development
environment.  

+------------------------------------------------------------------------+

   Paul Stevens                        {apple|decwrl}!metaphor!pstevens
   Metaphor Computer Systems           pstevens@metaphor.com
   Mountain View, CA