| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: the PM message queue |
Hi Mads!
(Mon Nov 16 1998) Mads Orbesen Troest wrote to Andrew Belov...
MOT> Actually, I don't really see why it should be impossible to implement
MOT> "real" multiple input queues, as PM programs have
always, since day 1,
MOT> allocated/deallocated a "message queue" through a
standard API. It should
MOT> be very possible - but demanding a major rewrite of some central PM DLLs
MOT> - to fix this;
...and, again, some software will refuse to work. We've learned it with
Warp Fixpak 17. Some people were still using PMWord by then and a lot of
noise was made.
MOT> I fear the problem is that no-one knowing anything about
MOT> the old design of OS/2 remains at IBM and they are simply afraid to
MOT> touch something that's not /really/ broke.
However, they reworked the kernel in OS/2 4.5. So, they still know the OS/2
internals.
I think it's IBM's policy not to implement something its corporate clients
won't need. IBM's infamous "patches" (PM_ASYNC_FOCUS_CHANGE,
CMPXCHG8.SYS, and a CONFIG.SYS switch in OS/2 4.5 to specify the memory per
process limitation) exactly reflect their policy.
MOT> Unfortunately, I find it increasingly hard to live with a system
MOT> with the lame SIQ problems OS/2 present from time to time... :-\
The problem is also that OS/2 usually will survive after an interface lock.
If it would trap, or compromise system integrity in any other way, the SIQ
problem might be fixed.
Bye.
---
* Origin: Conea Software Mail system - Moscow, Russia (2:5020/81)SEEN-BY: 396/1 632/0 371 633/260 267 270 371 635/506 728 639/252 670/218 @PATH: 5020/81 2604/104 270/101 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.