Date   : Sat, 06 Apr 1985 11:15:00 PST
From   : "R. MEIER" <rmeier@SU-STAR.ARPA>
Subject: re: kermit v4 binary transfer failure

Todd,
       I too have been using Kermit-80 v4 for routinely transferring
binary and text files without difficulty.  On the mainframe end, there
has been a Kermit-32 (VMS) and a UxKermit (Unix).  I encountered a
frustrating problem when I originally brought up Kermit v3, which might
be of help.  My version of Kermit used an unremembered character to
indicate characters > 80h, but both mainframe kermits used '&'.  This
was a simple problem, but I used Kermit for about 2 weeks without
realizing why it would not transfer binary files, but would transfer
most (but not all) text files.
       Another possibility to check is that you are using the correct
error detection code.  I have heard that some mainframes use 6-bit crc
on text files, but expect 12-bit crc on binary files.
       Both of the above problems should result in getting a large number
of retries (> 4, probably 20) for each packet.  If you don't get a quick
fix, or a pointer that solves the problem, you might try posting your
symptoms.  As a test to see if the first problem is correct, you might
try sending some text files in binary mode.  You should get correct copies
of the text files with garbage appended to the end.
                                       Good Luck,
                                       Bob (rmeier@star.arpa)