Hi Jack!
Saturday December 21 1996 11:19, Jack Stein wrote to Matthew Laird:
 JS>  Session_Priority, as I understand it,  sets all sessions to 1 by
 JS> default. Setting a session to 2 will make it the LAST session
 JS> serviced, when time permits.  Doesn't matter at all if you set it to 2
 JS> or 32, it's still last. In other words, I don't think session_priority
 JS> does what you think.  My feeling is it should be left alone unless
 JS> really needed for something.  I guess, for example, you might set
 JS> every session to 2 except your BBS, which you set to 1, making sure
 JS> that always gets first dibs, but I never had to here. Also if you have
 JS> a process that you absolutly don't care about speed, you could give it
 JS> a 2 priority and insure everything else gets serviced first.
 JS> Generally, OS/2 does fine without touching this setting, left to it's
 JS> own devices.  Again, this is how *I* understand it...
*My* understanding of Session_Priority is the exact opposite. The higher 
number gets priority first and the lower numbers are last on the service 
st.
Which of us is right?
         Harry the "Hairball"
--- GoldED/2 2.50 UNREG
---------------