Hello Jack!
 >  Session_Priority, as I understand it,  sets all sessions to 1 by
 > default. Setting a session to 2 will make it the LAST session
 > serviced, when time permits.  Doesn't matter at all if you set it
 > to 2 or 32, it's still last. In other words, I don't think
 > session_priority does what you think.  My feeling is it should be
 > left alone unless really needed for something.  I guess, for
 > example, you might set every session to 2 except your BBS, which
 > you set to 1, making sure that always gets first dibs, but I never
 > had to here. Also if you have a process that you absolutly don't
 > care about speed, you could give it a 2 priority and insure
 > everything else gets serviced first. Generally, OS/2 does fine
 > without touching this setting, left to it's own devices.
OS/2 allows 4 classes of priority: IDLE, REGULAR, SERVER and TIME
CRITICAL.  Within each class there are 32 levels with 32 being
the highest priority and 1 being the lowest.  Changing the
priority in in a DOS or Win-OS2 properties window just changes
what level within the REGULAR class.  While it is possible to
set VDM's to IDLE, SERVE or TIME CRITICAL class it would not be
desirable in most cases. NOTE: A change from 1 to 2 raises the
priority.
A good understanding of how this works is vital to getting the
most out of a OS/2 system.  Priority Master II is a good
product for helping one learn about OS/2 and priorities.  They
do have a web site although I don't have it handy right now...
you can get a link to their site from either Indelible Blue
or OS/2 e-Zine.
Cheers,
Nicky
Internet: nrmorrow@cybertron.com
--- FleetStreet 1.18+
---------------