knudsen@ihlpl.ATT.COM (Knudsen) (12/02/88)
Quoting from the Coco Mailing List: >All you have to do for 3 serial ports is create 3 descriptors and >either 1 sharable driver or 3 separete drivers. I did this on the >screen so that I could have a user dialog in a bottom window and >a continuous process status display on an upper window. The 2 drivers >solved a nasty I/O suspend problem when the dialog task was waiting for >input. ^^^^^^^^^^^^^^^^^^^^^^^^^ I'm having a similar problem under L2. I had to break a large program into two sections piped together, proc1 ! proc2 . Works fine, except that the 2nd process can't output to the window until I type at least ENTER to satisfy the 1st proc's I/O Wait. Somehow I don't think that a 2nd copy of CC3IO would get along with the first one. So I'm looking for anyone else's theories for how to get around this problem. Be nice if there were some xmode parameter you could set on one or both of the paths, that would override the I/O interlocking. Would using stderror instead of stdout in the 2nd process help any? Note that all keyboard reads are by the 1st process, and all screen output is from the 2nd. The pipe connects 1st's stdout to the 2nd's stdin. TIA, mike k -- Mike Knudsen Bell Labs(AT&T) att!ihlpl!knudsen "Lawyers are like nuclear bombs and PClones. Nobody likes them, but the other guy's got one, so I better get one too."