Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!comcon!roy From: roy@comcon.UUCP (Roy M. Silvernail) Newsgroups: comp.sys.ibm.pc Subject: Re: XMODEM,YMODEM,ZMODEM,KERMIT Which is best and why? Summary: okeZtext transfers? no problem. Keywords: ZMODEM Message-ID: <232@comcon.UUCP> Date: 2 Jan 90 20:42:21 GMT References: <32428@news.Think.COM> <1989Dec31.210253.25273@delta.uucp> <1636@rodan.acs.syr.edu> Organization: Computer Connection - Anchorage, Alaska Lines: 30 In article <1636@rodan.acs.syr.edu>, amichiel@rodan.acs.syr.edu (Michielsen) writes: > Y & Z are supposedly better & faster, with Z being the best. I won't argue > with that but it is in my experience the least implemented in the real world. Zmodem is primarily (for now) a PC protocol. There are implementations for Unix, though. (I use Zmodem on this Unix site daily) > I find that I can't live without straight ascii file transfers that non of > these will do. Straight ASCII files? I assume, since you mentioned it at all, that you are moving text files between a PC and a non-PC. Zmodem for Unix includes a -a switch to convert newlines as the transfer progresses. Of course, in the case of a batch transfer, you must make sure that all the files to be moved are ASCII, else any binaries in the queue will be demolished by the text conversion. (You are correct about Xmodem and Ymodem not having this ability) There are also a large number of utilities to make the newline conversion on your PC. I use Rahul Dhesi's FLIP. No war. No flame-fest (at least, not from me... ;-) I use Zmodem most of the time, and Kermit when I have to. -- _R_o_y _M_. _S_i_l_v_e_r_n_a_i_l | UUCP: uunet!comcon!roy | "Every race must arrive at this #include ;#define opinions MINE | point in its history" SnailMail: P.O. Box 210856, Anchorage, | ........Mr. Slippery Alaska, 99521-0856, U.S.A., Earth, etc. |