info-mac@uw-beaver (01/28/85)
From: Ralph W. Hyre Jr. <RALPHW@MIT-XX.ARPA> Apparently the only problem is an extra CRLF sequence at the end of each line. Resulting in output like this: *** END OF DATA *** CRC:F001 This would explain why binhex couldn't find the checksum. Anyway, I deleted the blank lines and the 'broken' file (dataflow.hcx in this case) worked fine. I suggest modifying binhex so that blank lines are ignored, it possible, as the superfluous CRLF problem is a common one when transferring files between operating systems. - Ralph Hyre -------
info-mac@uw-beaver (01/30/85)
From: Gavin_Eadie%UMich-MTS.Mailnet@MIT-MULTICS.ARPA Another aspect of .HCX files that catches computers out is the fact that spaces are significant characters. That was a mistake! Our system trims trailing spaces when copying material to a terminal by default, causing no end of confusion when you use MacTerminal to capture a .HCX file (KERMIT works fine of course because it was designed to transfer files). Before leaping on our system to accuse it of foolishness remember that the copy operation was designed for people who have no use for trailing blanks - copying one file to another doesn't do this ...