Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!mips!apple!rutgers!mit-eddie!uw-beaver!ubc-cs!alberta!dvinci!weyr!p3.f209.n141.z1.FIDONET.ORG!Jim.Gilliland
From: Jim.Gilliland@p3.f209.n141.z1.FIDONET.ORG (Jim Gilliland)
Newsgroups: comp.os.os2
Subject: OS/2 PROGRAMMER'S REFEREN
Message-ID: <449.25CC1EB5@weyr.FIDONET.ORG>
Date: 1 Feb 90 16:32:53 GMT
Sender: ufgate@weyr.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:141/209.3 - Fernwood, Branford CT
Lines: 27


 MR> re: priority deltas.
 MR>  
 MR> Yes, it's clearer now, but it doesn't seem very sensible.  Can you
 MR> query the kernel to find the current priority level?  If so, then
 MR> the scheme is more sensible.  Can you set the priority absolutely?
 MR> (rather than indirectly by finding the current setting and then
 MR> changing it the desired amount) -- again, I hope so, that would be
 MR> more sensible.

I'm not sure I'd call it sensible either, but nobody asked me :-)

Yes, you can query the current priority level using DosGetPrty.  And you can  
set it directly, if I read the docs correctly.  When you issue DosSetPrty, you  
can specify a 1 through 4 for the class (idle, regular, time-critical, and  
fixed-high) or you can provide a class of zero, which says leave the current  
class in effect.  When you do this (class=0), then the level field is treated  
as a delta.  But when you specify a class of 1-4, the base level is set to  
zero and the delta is applied to that.  That lets you set it to an absolute  
value without knowing its current value.
 

--  
Jim Gilliland - via FidoNet node 1:140/22
UUCP: alberta!dvinci!weyr!141!209.3!Jim.Gilliland
Internet: Jim.Gilliland@p3.f209.n141.z1.FIDONET.ORG
Standard Disclaimers Apply...