Hi Tony,
TL>I've been a (very!) happy Warp user for about a year, and overall, I'm
TL>happy with it.  I'm running Warp 3 Connect (no fixpacks yet).
OK>
TL>One slightly annoying problem is that while DOS applications are easy to
TL>tweak, I'm having a few problems with Win-OS/2 sessions hogging the CPU.
TL>It doesn't seem to affect OS/2 applications at all, but once I have
TL>certain Windows applications (including something as mundane as a full
TL>screen Windows session), all other Windows and DOS apps slow to a crawl.
Proper full screen sessions, or maximised windowed sessions?
In windowed mode have you changed the offending programs to run in
separate sessions? By default windowed Windows applications run in a
single WinOS/2 session and suffer from all the problems of Windows
multi-tasking. Also, afaiaa, the session uses the parameters of the
application that initially opened the session and the settings of
subsequent applications opened that share the same session are stuck
with them.
TL>Is there anything that would help resolve this problem?  I've tried
TL>setting SESSION_PRIORITY to 1 and IDLE_SENSITIVITY as low as 10, but
TL>this has no effect. :-(
Running the windowed program(s) that hog the WinOS/2 subsystem on their
own (check the "separate session" box in the settings page) and not in a
shared WinOS/2 box. Then tweaking other session parameters for that
application as required.
George
 * SLMR 2.1a * Desk: A very large wastebasket with drawers.
--- Maximus/2 3.01
---------------