🚀 go-pugleaf

In <4aeof0$v8t@quandong.itd.adelaide.edu.au>, joswig@achilles.cs.adelaide.edu.au (Paul Joswig) writes:
>I haven't yet used any compilers under OS/2 except gcc/emx.  I wrote a
>program to help solve a puzzle in a game, invloving moving some
>bishops on a chess like board.  Anyway, it was a CPU intensive program
>that ran for say 30 seconds on my machine.  Now, the weird thing is
>this...  normally I find that when I move focus away from a running
>program that it's priority drops and hence it slows a little; well, at
>least if something else is running at the same time.  Now, with my
>program running in a window, it ran MUCH faster when I moved the focus
>from the window.  I mean the output scrolled at least twice as fast.
>Also, the WPS shell became unusable because, I assume, the program was
>stealing all the CPU.  This was weird!  Can anyone enlighten me?

This could be whats happening. (?)

OS/2 definitly slows foreground tasks right down when you
move to another task however, except repaints of windows
are deemed to be lower in priority than the running of the 
program. The result is that the program might be running
fast, but the updating of the display happens at a more
leisurely rate (a different concept than windows which
slows everything down, so that it can "appear" fast)

If a window is partially covered, then the updating or
repainting can happen faster, so the program looks like
it is working faster, even if it's not.

This is particularly apparent where you run 256color
display, as there is a lot of graphics work to do.

Regards

David Lyon
Hotwire Business Systems