> If it can, then it is a simple matter to create 32-bit 
 > versions of all the required functions (e.g. VioGetBuf), 
 > simply by creating a Vio32GetBuf which declares a variable as 
 > _far16. In fact, I am surprised if that is the case, that in 
 > the above example it didn't automatically do the conversion 
 > in the case of VioGetBuf.  Why didn't it?

 dn> VioGetBuf() just returns two words (into a 'LONG') - no 
 dn> automatic conversion from anything to anything else - it 
 dn> returns the raw address as determined by "$SCREEN".

I'm getting a bit confused here.  Here is the code:

static USHORT   *lvb;  /* logical video buffer */

VioGetBuf(&lvb, &lvbLen, 0);

Now I had to actually change the above to "USHORT _far16" to get
it to work.  Here is what Borland's header files have:

APIRET16  APIENTRY16        
    VioGetBuf (PULONG16 pLVB, PUSHORT16 pcbLVB, HVIO hvio);

I still don't see why it doesn't automatically thunk for me???  Thanks for
your time in explanation.  BFN.

Paul

---