>> 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 automatic
 dn> conversion from anything to anything else - it returns the raw address as
 dn> determined by "$SCREEN".

Of course.  You can't expect the function to have detailed knowledge that
the caller is an entirely different animal, nor can you expect the caller
to magically know that about the called function.  I understand now,
thanks.  BFN.

Paul

--- GoldED/2 2.42.G1114