MB> Note that a function declared as "_far16" will 
 MB> automatically adjust the "int" back and forth between 
 MB> 32-bit and 16-but code as needed.

Seeing as none of these functions use 'int', but all use USHORT/LONG
directly, this shouldn't be a problem.  :-)

 MB> Your problem is in the function declarations.  You need 
 MB> to tell the compiler that the functions must be 
 MB> accessed by a thunk into 16-bit code, and the proper 
 MB> use of the "_far16" keyword is the best way to do that.

I believe the following line in OS2DEF.H should do that (since I use
APIENTRY16 in the prototype):

#define APIENTRY16  _Far16 _Pascal

So, what else could I be doing wrong?  :-/


 MB> Peter Fitzsimmons' suggestion about writing a 16-bit 
 MB> DLL to handle this is a good one, actually, although 
 MB> not really necessary.  If you goal is to get this done 
 MB> as simply and quickly as possible, then his approach 

Simple and quick?  I've know about SMSERIAL.DLL for a while, but I'm trying
to learn this, so I'm trying the 'hard way' for now.  If I get fed up, I'll
go to SMSERIAL.DLL.  :-)

 MB> should be used.  On the other hand, if you are trying 
 MB> to do this as a learning experience, you may as well 
 MB> keep plugging on getting the compiler to thunk.

Yup - gonna keep trying.  :-)


--- Maximus/2 3.01