[13298] in Athena Bugs
sun4 7.7Q: talk
daemon@ATHENA.MIT.EDU (Mike Barker)
Mon Mar 6 17:41:48 1995
To: Michael J Shurpik <mshurpik@MIT.EDU>
Cc: bugs@MIT.EDU
Date: Mon, 06 Mar 1995 17:41:45 EST
From: Mike Barker <mbarker@MIT.EDU>
Hi, Michael.
the current version of talk on Solaris corrects the problem with
visible ^M display.
the timing characteristics of talk depend on the socket layer
communications of the network. if network traffic is high,
communications are slow. I am afraid that your objection to irregular
display speeds cannot be solved technically using current
implementations of talk and networking protocols.
thank you for using Athena.
mike
------- Forwarded Message
Received: from SOUTH-STATION-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA27884; Mon, 6 Mar 95 17:14:42 EST
Received: from GULCH.MIT.EDU by MIT.EDU with SMTP
id AA00774; Mon, 6 Mar 95 17:14:40 EST
From: mbarker@MIT.EDU
Received: by gulch.MIT.EDU (5.0/4.7) id AA03647; Mon, 6 Mar 1995 17:14:41 -0500
Date: Mon, 6 Mar 1995 17:14:41 -0500
Message-Id: <9503062214.AA03647@gulch.MIT.EDU>
To: mbarker@MIT.EDU
Subject: NetProb ticket #3093, sun4 7.7Q: talk
Cc:
Content-Length: 1291
>From mshurpik@MIT.EDU Thu Feb 16 22:20:32 1995
>Received: by gregor.MIT.EDU (5.57/4.7) id AA01511; Thu, 16 Feb 95 22:20:28 -05>00
>Received: from W20-575-128.MIT.EDU by MIT.EDU with SMTP
> id AA28471; Thu, 16 Feb 95 22:20:18 EST
>Received: by w20-575-128.MIT.EDU (5.0/4.7) id AA26231; Thu, 16 Feb 1995 22:20:>22 -0500
>Message-Id: <9502170320.AA26231@w20-575-128.MIT.EDU>
>To: bugs@MIT.EDU
>Subject: sun4 7.7Q: talk
>Date: Thu, 16 Feb 1995 22:20:21 EST
>From: Michael J Shurpik <mshurpik@MIT.EDU>
>Content-Length: 746
>
>System name: w20-575-128
>Type and version: SPARC/Classic 7.7Q
>Display type: cgthree
>
>What were you trying to do?
> use talk
>
>What's wrong:
> a) On my side of the xterm, I see all the control characters. i.e.
>carriage returns are replaced by ^M's.
> b) When the person I'm talking to types, it takes forever (meaning
>sometimes minutes) for his characters to show up on my screen).
>
>What should have happened:
> a) Perfect representation of what I type.
> b) His characters, one by one, as he types
>
>Please describe any relevant documentation references:
> Please fix this. My experience is that most of these bugs go unfixed.
>I have sent several bug reports about programs that were rendered completely
>unusable, and none of them were attended to.
>
>
------- End of Forwarded Message
