Excerpted from a message dated 10-12-98, Rob Basler to Murray Lesser:

ML>    The Keyboard, Mouse, and Video (16-bit) Control Program functions
ML>are now described in the on-line "Control Program Guide and
Reference"
ML>manual furnished with the Warp 4 Developers Toolkit.  (If you are
ML>downloading from somewhere, these are in CP1.INF (1296373 bytes). Unlike
ML>the OS/2 1.x toolkit manual, this version uses current nomenclature.

ML>    I guess IBM has finally decided that text-mode programs are here to
ML>stay!

RB>Actually, the VIO calls are in CP2.INF and that version OMITS a
  >number of important function calls including VioGetPhysBuf which is
  >REQUIRED if you want to use fullscreen graphics. Use the original
  >PRCP.INF.

Hi Rob--

    I don't know what version of the Warp 4 toolkit you have, but mine
has all three sets (KBD, MOU, and VIO) of 16-bit API function calls in
CP1.  The file is dated 9-16-97.  But, you are right: there is no
VioGetPhysBuf in there, even though it is still in bsesub.h.  However,
there are other Vio calls in the toolkit INF that aren't in PRCPl.INF. A
little checking showed that some of those were not in bsesub.h, either
(?).

    The only time I ever wrote anything in C using VIO calls [including
VioGetBuf] was in 1994.  It was purely text mode, and contained windows
with colored "character" borders surrounding scrolling text.  I didn't
use VioGetPhysBuf as I don't do graphics.

    VioGetPhysBuf is defined in the 1993 book by Dorfman and Neuberger:
OS/2 Extra (ISBN 0-8306-4567-5).  That book also uses current
nomenclature to define the 16-bit API functions.  I have heard
conflicting reports as to whether or not the book is out of print.

    Regards,

        --Murray

___
 * MR/2 2.25 #120 * Never send a PM program to do a text-mode job

--- Maximus/2 2.02