Hi Dean!

[..]
 DR> There is another way to easily effectively 'lock up' OS/2, which
 DR> is to hang the PM queue. It know this all to well. But a partial
 DR> fix for that is supposedly in the works.
Hihi, I know that you know that this doesn't _hang_ OS/2. It just blocks
the input queue - all tasks are running but you can't send input to the
system.
I'm very curious about this upcoming 'fix' ... perhaps a second thread will
be generated which 'simulates' multiple message queues as it will only
serve the remaining msq-clients and not the blocking msq. But the
management of such a "fix" seems to be quite difficult.
The EXE-loader is multithreaded in Warp II - so you can start multiple
programs simultaneously and nothings blocks the input queue. Not bad !

I'm little sad about IBM not wanting to _really_ improve our current OS/2's
technology. They say they're targeting the small-office and home-office
market and are shooting OS/2 at the users. So it has to be small and handy
- and "never change a running system". I'd like to see multiple
message queues, all 16-bit interfaces replaced by 32-bit ones and (last but
not least) HPFS32 with improved features. Just dreaming ...
But for my best guess IBM will introduce such technology in OS2PowerPC.
BTW: the PPC630 was already designed for frequencies up to 400MHz.

        __      2:246/2320.18{at}Fidonet 14:75/1010.18{at}NFDN
        |_)     7:7000/7998{at}ZebraNet  81:449/8810.18{at}OS2Net
cu/2.99 |atrick Haller{at}ti-nov1.fbe.fh-weingarten.de

--- FleetStreet 0.95.3wb