> So when this app is running,  the dive sample crawls?  
 > (and,  I would assume, pulse is locked at 50%)?

Yup. The titlebar on the DIVE sample says it's running at 0.18 fps,
and it slows my machine to a crawl. I have to type "Alt+O", wait until
the current frame is done redrawing (10+ seconds), then type "x", to
get out of the DIVE sample. The Lotus thing updates the little graph
about 3-4 times as often as the one in pulse, and the effect is a lot
more pronounced than with pulse.

I just started the Lotus app again, and I've got Pulse running. The
Pulse window didn't change when the Lotus app was started, but starting
Pulse while the Lotus app is  running causes its graph to run right at
50%, with no activity other than me staring at the screen. These little
system utilities are cool, aren't they?

 > If this is so,  get on the horn to Lotus and VERY LOUDLY 
 > tell them to stop letting their Windows programmers port 
 > any code to OS/2.

Will do. Incidentally, what's a better way to make a Pulse-type app? I
mean, the DosSleep() approach doesn't seem to work too well, so what
would be a better indicator? (IMO, the amount of disk grinding I hear
while using OS/2 seems like a lot more reliable indicator. :))

Kelly

___
 X KWQ/2 1.2g NR X I'm an OS/2 developer...I don't NEED a life!

--- Maximus/2 2.02