Path: utzoo!attcan!uunet!maverick.ksu.ksu.edu!hoss!hoss.unl.edu!ho From: ho@hoss.unl.edu (Tiny Bubbles...) Newsgroups: comp.sys.mac.misc Subject: Re: Zterm woes Message-ID: <1990Oct15.154813.14258@hoss.unl.edu> Date: 15 Oct 90 15:48:13 GMT References: <1380@fornax.UUCP> <1990Oct15.092858.28019@hoss.unl.edu> Sender: news@hoss.unl.edu (Network News Administer) Distribution: na Organization: Daily Nebraskan, University of Nebraska-Lincoln Lines: 26 In <1990Oct15.092858.28019@hoss.unl.edu> 252u3129@fergvax.unl.edu (Mike Gleason) writes: >What I have to do to get it to work, is tell my unix host to turn on >escape control characters. Of course that will bog down your speed a >little, but it sure beats sending text dumps of .hqx files like I used >to. Try something like this: sz -eo . As an aside, this often is caused not by the communications packages, but by flaky network protocols. Zmodem expects a full 8-bit path, and many telnet daemons routinely translate CR+NUL pairs into plain CR's, regardless of the settings of any network parameters, including XmitBinary and Transparent. Sometimes the network is at fault, other times the host telnet daemon is at fault. Some versions of Zmodem allow you to quote specified characters rather than all control codes, which would allow nearly-optimum transfer rates (for this special case, you'd just quote NULs and CR's.) Most Unix versions of Zmodem do NOT offer this, because Chuck Forsberg, Zmodem author, decided to make that part of his protocol proprietary. -- ... Michael Ho, University of Nebraska Internet: ho@hoss.unl.edu | "Mine... is the last voice that you will ever hear." -- ... Michael Ho, University of Nebraska Internet: ho@hoss.unl.edu | "Mine... is the last voice that you will ever hear."