public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Guido Roeskens <groeskens@bluewin.ch>
To: Andrew Thompson <andrew@waitaki.otago.ac.nz>
Cc: gnu-win32@cygnus.com
Subject: Re: ftp client corrupts binary files with ^m ??
Date: Wed, 05 Aug 1998 03:36:00 -0000	[thread overview]
Message-ID: <35C83670.2D6BD808@bluewin.ch> (raw)
In-Reply-To: <Pine.LNX.3.95.980805013441.6371C-100000@waitaki.otago.ac.nz>

Andrew Thompson wrote:

> I have ftp.exe installed on my system. When I get text files from other
> servers ftp works OK but when I set ftp to 'bin' and get a binary file the
> file comes out a little larger and (I Think) it has ^m's inserted into the
> binary code, hence it does not run.
>
> Do I need to mount everyting as "text=bin" on my system currently
> everyting is text=!bin??
>
> I do not understand how this system translates text files from unix type
> to dos type.
>
> Andrew Thompson

When ftp starts up it is in text (ascii) mode which does EOL
conversion("End-of Line" gets converted from 'LF' on Unix to 'CRLF' on DOS)

You have to change the transfer type to binary mode: Simply type "bin" as an
abbreviation for "binary". You can check the transfer type set with "type" or
with "status".

BTW: For help with ftp type "help" or "help <command>"Guido


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1998-08-05  3:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-03 17:22 Compilling squid Andrew Thompson
1998-08-03 17:30 ` ftp client corrupts binary files with ^m ?? Andrew Thompson
1998-08-05  3:36   ` Guido Roeskens [this message]
1998-08-05  4:28   ` Marius van Wyk
1998-08-06  0:57 Kevin F. Quinn
1998-08-06 14:36 ` Larry Hall
1998-08-07 17:07   ` Peter Dalgaard BSA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35C83670.2D6BD808@bluewin.ch \
    --to=groeskens@bluewin.ch \
    --cc=andrew@waitaki.otago.ac.nz \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).