--//--from--[ Christian Scarborough ]--//--
--//--to----[ All ]--//--

 CS> Why is this happening?  OS/2 isn't supposed to let one process hog
 CS> processor time like that, is it?  Is it something to do with the
 CS> message queues?

     Well it's probably happening because the thread is being repeated one
right after the other (or at least that's what it looks like you've made it
do) so once it finishes, it starts up again, there's is no idle time within
the thread nor is there any in between the threads.  This is common with
programs which are, as you put it, time intensive.  Graphics rendering, and
many system benchmarks similarly bog down the system even though it is mainly
just one process.  Notice how adding the DosSleep function freed up the
computer?  That's simply because you've given the program some lag/idle time.

Patrick


... Pardon Me, But Would You Have Any Blue Poupon?

___ Blue Wave/QWK v2.20
--- Renegade v10-05 Exp