Excerpted from message dated 12-11-96, David Noon to mark lewis:

ml> hummm... ok... when i type VER in a dos window and have 
ml> 2.30 returned, i _have_ to set AX >= 2 or i get 100% CPU 
ml> usage with the DOSSLEEP call... using 2 gives me 0% CPU 
ml> usage in a "repeat killtime until keypressed" loop... there 
ml> are NO fixpacks installed here...

DN>I can only presume you are running the red spine version of Warp. I
  >use the blue spine version and it reports in as 3.0 in a VDM window.
  >However. the "get version" interrupt for VDM support returns 20.30
  >for Warp 3.0. Since the first part should be divided by 10, this
  >gives 2.30 for Warp 3.0.
 Hi David--

    Just to confuse the record further, I am using red Warp 3 GA + FixPak 5. 
I get "3.00" when I type VER from either an OS/2 or DOS text-mode session. 
However, REXX SysOs2Ver gives 2.30, so it must use the API call
DosQuerySysInfo to get the version number.  The version-return values for this
API under OS/2 versions 2.0 through 3.0 are shown in a note to the API
description in my early edition of the Warp 3 Control Program Programming
Reference manual (G25H-7102-00). 

    As I remember, the discrepancy was an advertised idiosyncrasy of Warp 3,
supposedly for the benefit of those application programs that would not run if
they didn't get a "20" as the major version type.  It was
discussed at length
in the OS2 echo at the time.  I haven't the slightest idea what Warp 4 might
return for a call to this API, since I don't expect to install it.

    DevCon 12 seems to assure us that Warp 3 will continue to be updated to
cover the enhancements in Warp 4 that are important for those of us who aren't
interested in speech recognition and aren't connected to anything except by
modem (I'm not considering the cosmetic changes.)  Of course, this leaves
commercial developers with the problem of what they might use to determine if
their latest efforts will run on a particular system.  For example, if the app
requires OpenDoc, the problem is no different if I am running the add-on
provided in DevCon 12 for Warp 3, or the optionally installable capability of
Warp 4.  If I were writing programs for anything other than my own amusement
on my own system that used OpenDoc, checking for a version number won't do it. 
There has to be a better way.

    Regards,

          --Murray  ___
 * MR/2 2.25 #120 * Watching for speed bumps on the Information Highwy

--- Maximus/2 2.02