Some non-Columbia Kermit implementations simply do not work, including some
found in BBS software. For example, if you download a file from a BBS using
their Kermit protocol option and find a lot of Ctrl-Ys in your file where only
actual letter Y's should be, then the BBS has a broken Kermit implementation.
The same is also true if a file downloaded from a BBS in binary mode is bigger
than the original. Ask your BBS sysop to install MS-DOS Kermit ("Kermit Lite")
as an external protocol. See the KERMIT.UPD file in the MS-DOS Kermit 3.14
distribution for additional information.
The more common cause, however, for "corrupted" binary files is that they
were transferred in text mode.
Both Kermit and ftp transfer files in text mode by default. This means
that record formats and character sets are likely to be converted. You can
tell Kermit to skip all conversions and transfer the file literally, as-is,
with the command: If you follow all these directions and binary transfers still come out
wrong, then perhaps the file you were downloading was corrupt to begin with --
e.g. it was ftp'd in text mode instead of binary mode.
12 Binary Files Are Corrupted After Transfer
SET FILE TYPE BINARY
Normally, it is sufficient to give this command to the FILE SENDER
before giving it the SEND command. But there are some exceptions to this rule:
Kermit FAQ / Columbia University / kermit@columbia.edu