Xref: utzoo comp.sources.bugs:1746 comp.unix.ultrix:999
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!amdahl!nsc!pyramid!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.sources.bugs,comp.unix.ultrix
Subject: Re: Oliver's screen and tip(1) on Ultrix 3.0 problem
Message-ID: <7017@cbmvax.UUCP>
Date: 31 May 89 03:50:02 GMT
References: <22460@prls.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <22460@prls.UUCP> gordon@prls.UUCP (Gordon Vickers) writes:
> 
>       I've been having difficulty with Oliver's Screen program ever
>   since I installed Ultrix 3.0 .
>       If I start up a tip(1) process (I even tried it with tip from Ultrix
>   2.2 under Ultrix 3.0) in one of the screens, a large percentage of the
>   charectors sent to the screen don't get displayed.
> 
>   UltirxV.0-(r1
>               loi: oro                    /* login:gordon  */
>                       Pwor:               /* Passwd:       */

Smells like a parity problem to me!  Somebody is checking parity on
input and discarding characters with "bad" parity.  I switched over 
to Ultrix 3.0 last nite and have already had some complaints about
kermit/xmodem/ymodem being broken, though uucp seems to be working
just fine.  One might suspect that something has been "improved"
in "raw" or "cbreak" mode input processing.

Did you get to the bottom of this?  What is Olivers Screen program?



-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)