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
DN>>Warp. I use the blue spine version and it reports in as 3.0
DN>>in a VDM window. However. the "get version" interrupt for
DN>>VDM support returns 20.30 for Warp 3.0. Since the first part
DN>>should be divided by 10, this gives 2.30 for Warp 3.0.

 ML>     Just to confuse the record further, I am using red Warp 3 GA +
 ML> FixPak 5.  I get "3.00" when I type VER from either an OS/2 or DOS
 ML> text-mode session.  However, REXX SysOs2Ver gives 2.30, so it must

shoot... :(  i forgot to mention that i use 4DOS and 4OS2 as my command
interpreters...

11:36
Sun  Dec 15, 1996
4dos (0) | c:\fd\n1 >ver

4DOS 5.51   OS/2 2.30


11:36
Sun  Dec 15, 1996
4dos (0) | c:\fd\n1 >command
OS/2 Command Interpreter Version 3    - DOS mode


11:36:5
Sun 12-15-96
C:\FD\N1 >ver

The Operating System/2 Version is 3.00

)\/(ark