PF> Same as windows (ax=1680h,  int 2Fh).

 PF> My question to you is: why are you in a loop waiting 
 PF> for something to happen?  If you were to call one of 
 PF> the functions that does not return until a key is 
 PF> pressed,  you wouldn't have this problem.


Remember, this is a dos program, and to the best of my knoledge Borland
does not simply put a process to sleep and wait for a keyboard interrupt
(as there is only supposed to be one process). Any way you look at it
(unless you explain otherwise, I'm open minded) there is a loop.

here is basically what I was doing...(I allways welcome better code.)
while( Interested )
{  if( kbhit() )  {
     TakeApropriateAction()
   }else if ( the_window.SizeHit() )  {
      TakeDifferentAction()
   }
   ReleaseTimeSlice(); //added this  [ thanks Mike Bilow ]...
}

Only way I could think of to call a function that doesn't return until a
keystroke, or mouse message (under dos) would still have a loop.

BTW, why did you choose WATCOM C++ ? is it in you opinion supperior to
borland? If so, why? I just bought Borland's C++ for Os/2, but I'm not on a
budget so...

                Paul Rider.

--- Maximus/2 2.02