On Thu, 4 Apr 2002 15:32:10 +1000, da Silva, Joe wrote: > Actually, I was referring to Clarence's ARACHNE.BAT, but anyhow, > I've just downloaded your's too, and this also has no CR's.
> Personally, I don't believe in "ASCII" transfers or automatic/hidden > translation, just straight binary (avoids doppelganger degeneration! ;-). > If I want/need EOL translation, I'll do it myself. <G> I don't believe it made any sense to "invent" ASCII transfers either, but it's been done. The question is, will either of those .BATs run in DOS as received by you? I think not, as I've just tried it. DOS wants CRLF. Not LF or CRCRLF. If we upload in binary mode, they won't work for a casual (like me) downloader who does it the easiest way. (internal and automatic) What's worse, it could do some damage. This thread got started when I downloaded my own CLR.bat and screwed up my A1.66 install when trying it. I wouldn't assume that all users of the external FTP program would make bget their first choice for a text file transfer either. :( This document (somewhat dated) is the first one I turned up in a search for standards: (note that it is in ASCII format itself) ftp://nic.merit.edu:21/documents/rfc/rfc0959.txt An excerpt: 3.1.1.1. ASCII TYPE This is the default type and must be accepted by all FTP implementations. It is intended primarily for the transfer of text files, except when both hosts would find the EBCDIC type more convenient. - Clarence Verge - Back to using Arachne V1.62 ....
