CompuServe Messages

Nope. And CoComm multitasks just fine, Vic. Remember, those signal bits are limited to 16 for a single task – not 16 for the machine. Once you click on CoComm, it gets 16 it can use…. and I use a fair number of them. I even have some to spare. But I can't afford for the spares (4 or 5) to be eaten and never returned by CoComm itself, which is what was happening. You know, things are _much_ easier to manage when each window gets it's own IDCMP port. Likewise, the consoles. That's why CoComm uses alla them ports, and that's why it's so powerful, too – because the resources that I have are extremely easy to manage. You bring up something that's been bothering me, though – why 16 signal bits? Seems to be pretty darn shortsighted to me! I think that if you start something from a CLI as a task (either with run or if it forks itself via cback.o or whatever) then the CLI is sitting there with sigbits-forked sigbits available. Seems awfully stupid – that limits the number of tasks you can have in a CLI – something I thought wasn't supposed to happen. If it doesn't work that way, then I suppose it's not so bad. I did see a comment to the effect that it did work that way just recently, tho. Why not 32 signal bits? I could use em. <grin> –Ben–