harrow@exodus.DEC (Jeff Harrow NCSE TWO/E92 DTN=247-3134) (04/26/85)
Based upon a warning from Joe Wasser and subsequent experimentation, it
appears that, when downloading a COMPRESSED BINHEX file to the Mac using
MacTerminal's "Record text off top" mode, MacTerminal throws away
trailing spaces on a line. These spaces ARE significant to the
COMPRESSED BINHEX format, and so the checksum does not match and the
resultant file is invalid.
MacTep works just fine, however.
Does anyone have any ideas as to why MacTerminal is doing this, and/or
how to STOP it from this dastardly action?
Jeff
Work address:
ARPAnet: HARROW%EXODUS.DEC@decwrl.ARPA
Usenet: {allegra,Shasta,decvax}!decwrl!dec-rhea!dec-exodus!harrow
Easynet: EXODUS::HARROW
Telephone: (617)858-3134
USPS: Digital Equipment Corp.
Mail stop: TWO/E92
1925 Andover St.
Tewksbury, MA 01876jimb@amdcad.UUCP (Jim Budler) (04/27/85)
In article <1861@decwrl.UUCP> harrow@exodus.DEC (Jeff Harrow NCSE TWO/E92 DTN=247-3134) writes: >Based upon a warning from Joe Wasser and subsequent experimentation, it >appears that, when downloading a COMPRESSED BINHEX file to the Mac using >MacTerminal's "Record text off top" mode, MacTerminal throws away >trailing spaces on a line. These spaces ARE significant to the >... >Does anyone have any ideas as to why MacTerminal is doing this, and/or >how to STOP it from this dastardly action? Use one of the newer versions (hqx) which don't use a space as a significant character. -- Jim Budler Advanced Micro Devices, Inc. (408) 749-5806 UUCPnet: {ucbvax,decwrl,ihnp4,allegra,intelca}!amdcad!jimb Compuserve: 72415,1200