Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!kd4nc!n4hgf!wht
From: wht@n4hgf.Mt-Park.GA.US (Warren Tucker)
Newsgroups: comp.unix.xenix.misc
Subject: Re: Need help with two Xenix Problems
Message-ID: <266@n4hgf.Mt-Park.GA.US>
Date: 6 Dec 90 20:59:19 GMT
References: <12181@milton.u.washington.edu> <75@gdx.UUCP>
Reply-To: wht@n4hgf.Mt-Park.GA.US (Warren Tucker)
Distribution: comp.unix.msdos,comp.unix.misc,comp.unix.programmer,comp.unix.xenix.misc,comp.unix.xenix.misc
Organization: Amateur Radio Station N4HGF
Lines: 25

In article <75@gdx.UUCP> jay@gdx.UUCP (Jay A. Snyder) writes:
>Stephen Milton (smm@milton.u.washington.edu) writes:
>
>->First problem:
>->  So far the only comm utility that I can get  to work on my Xenix/286 machine
>->is cu.

Tru ECU :-) available from comp.sources.misc archives
(new version Real Soon Now).

>type at host prompt:
>rz
>then type:
>~$ sz foo.bar </dev/ttyxx

The problem with standard cu is that it does not kill it's
receiver process when it forks with ~$, thus cu's rcvr swallows
some/much of the protocol traffic from the remote host.

Indeed, as the man page says, ~$ sends the OUTPUT of the forked
process to the line, but it, er, forks up your INPUT.
 
----------------------------------------------------------------------------
Warren Tucker                     emory!n4hgf!wht or wht@n4hgf.Mt-Park.GA.US
"I was 35 years old before I knew a pie was meant to be eaten." - Moe Howard