Jonathan de Boyne Pollard wrote in a message to Mike Bilow:

  > Note that the 16-bit OS/2 API and the 32-bit OS/2 API are 
  > different, and have differently sized arguments in many 
  > functions.  Watcom C++ 10.0 only ships with the 32-bit OS/2 
  > header files, and so trying to build a 16-bit OS/2 app which 
  > calls the OS/2 API directly will only work if you obtain the 
  > 16-bit OS/2 header files elsewhere.  The 16-bit OS/2 header 
  > files in the OS/2 1.3 Toolkit are available from a number of
  > sources, including the IBM DevCon, and are shipped with the
  > newer Watcom C++ 10.5.

 JdBP>   Just to make it crystal clear for newbies (such as Glenn)
 JdBP> you should   add the caveat that you shouldn't be writing
 JdBP> new 16-bit OS/2 programs   except in the very specific cases
 JdBP> that you are writing device drivers   or writing for
 JdBP> Microsoft OS/2 1.x.  There is absolutely no need to   write
 JdBP> anything other than 32-bit OS/2 applications programs these
 JdBP> days. 

 JdBP>   ( I'm not disagreeing with you, just making sure that the
 JdBP> obvious is pointed out.  (-: )

Yes, I agree with you on this.  The only additional exception I can think
of is that OS/2 16-bit programs can also run on NT, but that is pretty
arcane.
 
-- Mike


---