Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!swrinde!ucsd!pacbell.com!pacbell!att!mcdchg!laidbak!obdient!gagme!grahj From: grahj@gagme.chi.il.us (jim graham) Newsgroups: comp.dcom.modems Subject: Re: Zmodem Worked!! Message-ID: <607@gagme.chi.il.us> Date: 9 Aug 90 01:22:06 GMT References: <1990Aug7.011103.6176@ariel.unm.edu> <606@gagme.chi.il.us> Distribution: usa Organization: GAGME - Public Access UNIX of Niles, Illinois, USA, Earth Lines: 40 In article <606@gagme.chi.il.us> I wrote some stuff about getting X/Y/Zmodem to work through a network....but forgot to mention a couple of things.... and my computer at work just reminded me....when a transfer refused to go.... First, if you are going from a dos box to a UN*X machine, you may run into problems with file name arguments..... dos seems to think that all filenames are in UPPERCASE, while UN*X understands both upper and lower case.... So, if you are using something like Zmodem, that takes care of the filenames anyway, do NOT specify filenames....the 2 sides may just argue forever about what the filename is, and what is supposed to be sent. Second, and this is a trial-and-error thing, you may have to add some options to the rz command when uploading from a dos-box to UN*X (others?) in the case of binary files (e.g., tars, compressed tars, etc.). If you try the transfer, and it doesn't manage to send even the first packet (but the transfer DID manage to get started.....), you may need to tell the Zmodem receiver 2 things: 1) this is a binary file (normally it figures this out on its own....but...) 2) force the sender to escape all Zmodem transfer control chars. To do this, give rz the ``-be'' options. This will result in reduced throughput (on a good phone line, at 2400 bps, normal throughput tends to be about 245 CPS --- with the -be options, it drops to about 190 CPS). If anyone has any other info on file transfers through terminal servers, or through networks in general (X/Y/Zmodem, that is....not ftp, etc), I'd love to hear about it. If you don't want to post it to the world, please just send a reply to me. Jim Graham Amoco Corporation Network Design/Transmission Engineering Standard disclaimer applies....these opinions are mine, not Amoco's. > > >