#: 20258 S12/OS9/68000 (OSK)
    27-Aug-94  17:32:03
Sb: #20253-screen
Fm: Steve Wegert 76703,4255
To: Bob van der Poel 76510,2203 (X)

 > One could set things up to set PORT to something...but I don't see that
 > helping anything. I guess the one question which goes unanswered is this:
 > If you did know that a particular program was running on virtual screen 3,
 > what would you do with the information?
 >
 >

Bob,

I get bit without this info in a couple different scenarios ...

As good as it is ... screen still sometimes locks up, and the only way I've
been able to 'fix' it is to kill the current window. If I have a program
running, I can trace the owning shell by way of the ID and PID, but this can be
a bit tedious.

Also ... I have other users logged in from time to time. We have a habit of
using the send command to communicate back and forth. Send requires a path ..
again, a bit tedious tracking it back with the ID and PID.

Same thing with redirecting output to a particular window from time to time.

Not big issues, but if it was easily addressed, it would make screen more user
friendly.

By the way ... testing is looking good. I did have similar problems with a beta
release of Mark's Sterm Pro. It would fire up fine, but once I was logged into
CompuServe, I lost proper line endings. When I switched back to his current
release of 1.5 things were back to normal.

I'm not sure what he's doing differently ... and don't know if he's even
willing to discuss the code any longer given his "departure" from OS9, but I'll
try calling him at the office to see if he has any ideas.

*- Steve -*