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

 PW> Beleive it or not, 20.40, which translates to 2.40

that's what i was "missing"... i've updated my routines again to
slice using DOSSLEEP(2) for WARP3 and DOSSLEEP(0) for WARP4 with all others
reporting v2.xx using the DPMI slice call... in fact, at this time, only
plain dos will cause the use of INT28h in my DOS library...

)\/(ark