Kermit for Windows

KermWin FAQ - Selecting Text or Binary Transfer

Under Construction

Kermit for Windows does not provide a setting to indicate whether you are transferring text or binary files. This may seem odd, but is quite intentional. A bit of an explanation should help.

The Kermit protocol provides a way to handle transferring text files between platforms that define text files differently. For example, UNIX defines text file lines to end with a single control-j (linefeed). DOS defines line ends to be control-m and control-j (carriage returrn followed by linefeed).

By telling Kermit that you are transferring a text file, you are requesting that text files be converted to a common format as they are sent or received. That way each side of the connection can then convert the data to an appropriate format, as needed.

As it turns out, the common format for text files defined by the Kermit protocol is the same format that DOS stipulates. That means that Kermit running under DOS/Windows does not need to perform any translation on text files (since the common format is already the format desired). This explains why you will not find a setting in Kermit for Windows to indicate text versus binary. Since text files require no translation under DOS, they can be treated just like a binary file (no translation).

WARNING: It is still necessary to indicate whether you are transferring text or binary files on the remote side of the connection (unless the remote side is also DOS).

Copyright © 1997, Wayne Warthen
Revised Sun Jan 25, 1998

E-Mail feedback to author: