Fred Brucker wrote in a message to Bob Juge:
BJ} FB> IDLE_SENSITIVITY 100 Very Important!!
FB> BJ} This will defeat the purpose of running OS/2 as a
FB> multitasker, since it does not allow OS/2 to detect
FB> when the task is idle. Mine (Warp) works just fine
FB> with this set at the default value (75).
FB> {COMMO} is making calls to OS/2 to let it know when it's idle.
FB> So OS/2 doesn't (shouldn't) have to use keyboard calls for
FB> that. Have you verified that at the 100 setting there is no
FB> multi-tasking?
From the OS/2 master help index:
----------------------------------------
Use IDLE_SENSITIVITY if you want to specify a threshold for judging when a
program is doing nothing but waiting for input. The value in this field is a
percentage of the maximum frequency with which a program repeatedly checks,
or polls, for input. To change the threshold, drag the box, select a button,
or type into the entry field.
If a program polls at a rate greater than the percentage specified in this
field, the program is likely to be idle, so the operating system reduces the
amount of processor time allocated to the session. By selecting a value in
this field, you prevent the operating system from applying idle detection
until the program reaches a percentage of this predetermined maximum.
Increase the percentage if your program can receive input while running and
seems to run slower than you expect. If you select 100 in this field, you
turn idle detection off, and the program can poll as often as necessary
without operating system intervention.
The default value is 75 (percent).
----------------------------------------
The words "without operatying system intervention" above would certainly seem
to suggest OS/2 is allowing a DOS app with IDLE_SENSITIVITY set to 100 to run
"unmanaged" as to allocating processor time, which would also mean OS/2 is
ignoring your calls to let it know {COMMO}'s idle.
- Bob
Compuserve: 72662,3547
Internet : bob@juge.com
---
---------------
* Origin: COMM Port OS/2 (713) 980-9671 (1:106/2000)
|