Xref: utzoo comp.unix.xenix:7150 comp.unix.questions:15720 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!apple!vsi1!wyse!bob From: bob@wyse.wyse.com (Bob McGowen Wyse Technology Training) Newsgroups: comp.unix.xenix,comp.unix.questions Subject: Re: Looking for a xfer protocol (source preferred) usable with cu. Message-ID: <2373@wyse.wyse.com> Date: 16 Aug 89 20:41:04 GMT References: <951@lakesys.UUCP> <17@.UUCP> Sender: news@wyse.wyse.com Reply-To: bob@wyse.UUCP (Bob McGowen Wyse Technology Training) Followup-To: comp.unix.xenix Organization: Wyse Technology Lines: 27 In article <17@.UUCP> root@.UUCP (Larry Snyder) writes: >In article <951@lakesys.UUCP>, davek@lakesys.UUCP (Dave Kraft) writes: > >> I'm looiking for a transfer protocol (x/y/z/whatever-modem ) > > > Have you looked at procomm? ^^^^^^^ Shouldn't this be pcomm, since procomm is DOS specific and code is not available for it, that I know of? A note on using cu with ANY file transfer program--cu forks a second copy of itself. The two cu's separate IO duties, one taking incoming data and displaying it on the terminal. If you try to run a file transfer program such as x/y/z modem this cu process and the file transfer will compete for incoming characters and transfer will fail. I have source for both pcomm and the xyzmodem programs. email me and I will get you copies. I will need a bang path route, through uunet preferred. This should also be available from alphacm BBS in Southern CA, if you are interested I also have phone number for it. Bob McGowan (standard disclaimer, these are my own ...) Customer Education, Wyse Technology, San Jose, CA ..!uunet!wyse!bob bob@wyse.com