> Is this lotus application also a cpu monitor?   I didn't 
 > realize that. 

Yeah, it's got the same kind of graph that pulse has.

 > The only way to truly know how busy OS/2 is is with the 
 > cooperation of the kernel's scheduler.  I think there may 
 > be undocumented api's to enable this (with added system 
 > overhead).   Ask Frank C. (of Pegasus). I think Pegasus and 
 > SPM/2 use them.

Pegasus certainly uses something... I had a demo version of that that
was apparently meant for OS/2 2.1, and running it under Warp locked the
system up good. "hmmm", I said, "Look at that... The system's not busy
at all!"

 > As someone mentioned here,  a simple solution would be to write a
 > Pulse for  each priority class -- but this would adversely effect the
 >  performance of the programs that really need the cycles.

True. I think I'll just stick with the more realistic "Wow, this thing
is crawling, it must be busy" method.

Kelly

___
 X KWQ/2 1.2g NR X "640K ought to be enough for anybody." - Bill
Gates, 1981

--- Maximus/2 2.02