Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!amos!hartung
From: hartung@amos.ling.ucsd.edu (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d,comp.sys.ibm.pc
Subject: Re: Telix and file transfers
Summary: using 8 data bits and -l 1024 did the trick
Keywords: Telix, file transfer, problems
Message-ID: <6310@sdcsvax.UCSD.Edu>
Date: 27 Apr 89 04:11:48 GMT
References: <8904252002.AA01622@decwrl.dec.com> <89Apr25.225050edt.19728@me.utoronto.ca>
Sender: nobody@sdcsvax.UCSD.Edu
Reply-To: hartung@amos.ucsd.edu (Jeff Hartung)
Followup-To: comp.binaries.ibm.pc.d
Distribution: usa
Organization: Univ. of Calif., San Diego
Lines: 27
Xref: utzoo comp.binaries.ibm.pc.d:2829 comp.sys.ibm.pc:27968

In article <89Apr25.225050edt.19728@me.utoronto.ca> rwh@me.utoronto.ca (Russell Herman) writes:
>I had similar problems, and the solution may be relevant to you as well.
>Use "-l 1024" in your SZ calls.  I suspect the problem relates to not
>doing flow-control in realtime when connected over a network (in my case,
>a T1 link).

Thanks, everyone, for all the help with Telix (which was version 3.11 from 
SIMTEL20, by the way).  What I had to do to get the Zmodem transfers to work 
correctly in both directions was:

	(1) Put 'stty pass8' in my .login to accept 8 bit data from the
	standard input on the VAX.

	(2) Use parity set to none with 8 data bits, one stop bit when I
	logged in from home.

	(3) Use the '-l' option with sz.  (Since it worked, I added the line:
		alias sz 'sz -l 1024 \!*'
	to my .cshrc file.)

Everything works great, now.  Thanks again.  I, too, highly recommend this
package.

 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 ARPA - hartung@amos.ucsd.edu          
 UUCP - ucsd!amos.ucsd.edu!hartung