Hallo IVAN!

Antwort auf eine Message von IVAN TODOROSKI an MARIO SEMO:

 IT>   Also, Process Commander does NOT do "who knows what".
The way it  
 IT> changes other process' priority is totaly documented and supported by  
 IT> the OS/2 API. It is a simple DosSetPriority() call. Don't see

wasn't it PC who added a second thread to EACH application in the system?
or something else added to the system with WARP4. at least every and each
app in the system has (under WARP4) one thread more then under WARP3. 
i name this "do who knowns what". 
( as i reember it was the application which was previously (under OS2 3.x)
called WatchCat. isnt this PC today?).

and WHAT threads are changed when PC calls DosSetPriority? my App has 16
threads. each with different priorities. some idle, some TC. 

 IT>     Take any DOS assembler (even DEBUG will do) and create a simple    
 IT> program (.COM or .EXE, no matter) with this piece of code in it:

 IT>      cli
 IT>      x:
 IT>      jmp x

 IT>     Execute this in a DOS window.

mh. at moment not the time to test it (just in case), but as i remember it
doesnt crash my system with WARP4 as i tested it long ago. But it DEFINITLY
crash any OS2 2.x system. (simple because cli was not virtualized and so
really clears the interrupt enable). 

Have you tested this with WARP4?

But anyhow, this is COMPLETLY unrelated to ThreadPriorities. even if it
kills the system, the one and only reason is, that cli is not virtualized.


Servus, Mario!

--- FleetStreet 1.21 PR#2