Some senseless babbling from Jonathan De Boyne Pollard to Mike Ruskai
on 11-29-99  10:32 about DETACH...

 JDBP>> Indeed, I explicitly made the point that the OS/2 kernel itself 
 JDBP>> makes *no* distinction whatsoever between "text mode" and 
 JDBP>> "graphical" processes.  This was the whole point that I was making. 
 
 MR> Part of the priority table is something called "window boost", which
 MR> near as I can tell, serves no purpose other than to give a priority
 MR> boost to a graphical program.
 MR> [...]
 MR> So, in that limited respect, the kernel may be considered "aware" of a
 MR> difference between text-mode and graphical programs, though it's an
 MR> awareness that can be removed with a hex editor.

 JDBP> Actually, that doesn't mean that the kernel is aware of the difference
 JDBP> between textual and graphical programs.  The "foreground priority
 JDBP> boost" was in the very first 16-bit version of OS/2, well before
 JDBP> Presentation Manager was introduced and thus well before there even
 JDBP> were such things as graphical OS/2 programs.

 JDBP> This boost gives an increase in priority to "the foreground process". 
 JDBP> But the kernel does not determine what "the foreground process"
 JDBP> actually is.  It leaves that decision up to others.  All that the
 JDBP> kernel knows is that one process is singled out as being the process
 JDBP> that is "in the foreground" and is as a result to be given preferential
 JDBP> treatment when it comes to doling out CPU time. 
 JDBP> I suspect that it is the session manager that determines what the
 JDBP> foreground process is.  The 16-bit OS/2 CP reference describes the
 JDBP> foreground process as the process that "has the input focus", so I
 JDBP> suspect some collusion by the KBD subsystem in the making of this
 JDBP> decision as well.  Unfortunately, that is pretty much all that is said
 JDBP> anywhere on the subject. 

I'm not talking about the foreground boost.  The window boost is completely
separate from the foreground boost.  It apparently applies to any program
which has a graphical window, and is applied independently of the
foreground boost.  It might be dependent on whether or not the window is
visible, but I doubt it, given the extra work required to determine that
(since as little as possible should be done determining which thread gets
the CPU next).

Mike Ruskai
thannymeister@yahoo.com


... But how do we know your the REAL Angel of Death?

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr2