MB> This has significance only in 16-bit programs and is set in the startup 
MB> code by a call to DosGetMachineMode(), which exists only in the 16-bit OS/2 
MB> API. Obviously, if your 32-bit OS/2 program is running, you are in 
MB> protected mode.

MB> The only real purpose for _osmode is in bound programs written mostly to 
MB> the Family API.  By checking _osmode, you can use certain features only 
MB> accessible in one mode or the other, or which have to be done differently 
MB> depending upon mode.  For example, if you wanted a FAPI program to be 

Thanks for this info, that was what I was after - osmode is only
relevant for 16-bit.  So I have now #ifdef'd my way around that 
code so that when I'm in 32-bit I don't do it.  BFN.  Paul.
@EOT:

---