JP>
  > In fact, can you tell me where I can fin
  > any documentation on all the Vio functions
JP>

  ----------------------------------------------------------------------

Conference: Os2prog
  To: Mike Lindstedt            Date:  6/22/1994
From: YOU                       Time:  8:43 pm
Subj: Fast Video Writes in text

ML>
  >                                      I now how to do this
  > in dos with the BIOS calls and am looking for something
  > similar.  Any help would be great.
ML>

  You probably need to check out the VIO calls, which is what
  textcolor() and cprintf() (this is BC++OS2, yes ?) are using
  internally.

  The VIO calls are part of the old 16-bit OS/2 1.x API, one of three
  "subsystems", and are declared if you #define INCL_SUB before
.

  Since they are the old OS/2 1.x API, they were (originally) dropped
  from the OS/2 2.x API, which is why they aren't listed in the API
  reference.  However, ...

  |  BBS: DONOR           Conference: Os2prog
  |   To: Richard Hulme          Date: 12/12/1993
  | From: Martin Pollard         Time: 12:51 am
  | Subj: VIO functions
  |
  |  JdeBP> Failing that, get hold of PRCP.ZIP from your nearest BBS, which
  |  JdeBP> is the PRCP.INF Control Program Reference file from the old 16-bit
  |  JdeBP> compilers. That also details the VIO calls.
  |
  | Another alternative is the book "OS/2 EXTRA! KBD, MOU & VIO SPECIAL
  | FUNCTIONS REVEALED" by Len Dorfman and Marc J. Neuberger (ISBN
  | 0-8306-4567-5, US$19.95). It's basically the information in PRCP.INF,
  | but in printed form (and cleaned up a little).  It'll tell you just
  | about everything you need to know about the VIO, KBD, and MOU functions,
  | including which functions will and will not work in a windowed OS/2
  | session (as opposed to a full-screen OS/2 session).
  |
  | And no, I'm not related to Jonathan.  I *do* like his taste in last names,
  | though. :-)

  You will find that it's not a particularly large leap from BIOS video
  calls to VIO calls.  Although with VIO, since you are thunking to
  16-bit and possibly doing a ring transition into kernel mode for each
  call, it's best to double buffer your screen and use Vio16WrtCellStr
  to put out as much of the screen in one call as you can.

  Incidentally, IBM has plans to re-introduce 32-bit versions of the VIO
  calls in a future release of OS/2, due to popular demand, so you
  aren't tying yourself to 16-bits forever.

  > JdeBP <

   ------------------------------------------------------------------------

  Incidentally, I can now confirm the comment in the final paragraph.

  You can find the old OS/2 1.3 Developers' Toolkit on the Developer
  Connection CD-ROM.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 2.02