Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!sgiblab!news.kpc.com!amd!amdahl!netcomsv!netcom.com!netcom3!ceb From: ceb@netcom3.netcom.com (Buckley) Subject: Re: zmodem rzsz and seyon In-Reply-To: todd@flex.eng.mcmaster.ca's message of Tue, 26 Oct 1993 16:27:24 GMT Message-ID: <CEB.93Oct27210232@netcom3.netcom.com> Sender: ceb@netcom.com (Buckley) Organization: NETCOM On-line services References: <1993Oct26.162724.2496@mcshub.dcss.mcmaster.ca> Date: Thu, 28 Oct 1993 04:02:31 GMT Lines: 32 In article <1993Oct26.162724.2496@mcshub.dcss.mcmaster.ca> todd@flex.eng.mcmaster.ca (Todd Pfaff) writes: From: todd@flex.eng.mcmaster.ca (Todd Pfaff) Date: Tue, 26 Oct 1993 16:27:24 GMT I'm using seyon under 386BSD-0.1+pk0.2.4 and Zmodem 3.18 for Linux (rzsz9202.tar.Z) to transfer files between my local PC and a remote Sun. Sending files from the Sun to the PC works fine, using sz on the Sun and the Zmodem autodetect feature of Seyon to initiate the transfer. Sending files from the PC to the Sun doesn't work. I see some output in the Seyon terminal window to the effect that I should start rz at the remote end, and I can see some modem traffic happening every once in a while but no progress is made. I'm running Seyon 2.03, and it only comes configured to auto-receive. I have found Seyon 2.13, which may have changed, but I haven't even had a chance to unpack it yet. If you've gotten the most recent version, and it's still not configured (look in .seyon/protocols), let me know, and I can send you the files to set it up. The way I have it set up does type the rz for you to the remote host, but this may be suppressed if you like. Also, assuming you did set up the protocols file right, the other key thing is to turn RTS/CTS control on. The symptoms you describe suggest you did manage to set up protocols reasonably, but don't have the flow control turned on. Seyon 2.03 (ab)uses SIGHUP's in the extreme, and is prone to crash. Seyon 2.13 claims to have finally fixed this, but it looks as if it'll need some hacking still. But, other than that, it's a pretty nice utility. --