Matthew Laird wrote in a message to Chris Knipe:
 ML> much like a broken record, it lasts for about 10-30 seconds, then the
 ML> game continues as usual.  I'm wondering if it might be OS/2 pausing
 ML> the game to do another task, and taking about the game's time slice?
 ML> If so, what are some settings that might solve 
 CK> this, I've tried a lot,
 ML> but none seem to be the right combination.  Thanks for any help!
 CK> Not sure but have you tried setting the session priority higher...
 ML> Yep, put it all the way up to 10 (I'm scared to put it any
 ML> higher, I don't know what that does to the rest of the
 ML> system =)  It seemed to lessen the problem, but I didn't
 ML> give it much of a test because I just got fustrated. 
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.  
Again, this is how *I* understand it...
                                                     Jack 
--- timEd/2-B11
---------------