Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!ukma!nrl-cmf!ames!oliveb!tymix!antares!jms From: jms@antares.UUCP (joe smith) Newsgroups: comp.sys.amiga Subject: Re: IFF viewer, UUencode, Kermit Summary: Problems with binary files Message-ID: <289@antares.UUCP> Date: 5 Dec 88 06:23:34 GMT References: <3763@pt.cs.cmu.edu> Reply-To: jms@antares.UUCP (joe smith) Organization: Tymnet QSATS, San Jose CA Lines: 28 In article <3763@pt.cs.cmu.edu> jwz@spice.cs.cmu.edu (Jamie Zawinski) writes: >> From: zlhb0a@apctrc.uucp (Lawrence H. Brown) >> My first guess is that the iff files are coming back mundged, > >Give that man a cigar! Kermit doesn't work for shit on binary >files, even if you use binary mode. I've been bitten by this >one before. You have to use UUencode or something. I have had no problems transferring binary files via Kermit from a Unix system. But I could never get binary files from a Fido (MS-DOS) system. The problem is that the Fido Kermit was doing 8th bit quoting when it was told not to. It sent extra ampersands which totally messed up the IFF file. Now for the good news. The Kermit that is inside VT100 (V2.6/jrbii.2) works fine with C-Kermit 4D(061) 4.2 BSD. I have "MODE IMAGE" set in S:VT100.INIT and use "kermit -i -s whatever.arc". "IMAGE" and "-i" are flags which say to not convert NL to CR+LF and vice versa. A quick check to see if the file made it OK is to compare byte counts from "ls -l" and "list". In summary - Kermit can handle binary files, including IFF images. -- +----------------------------------------------------------------------------+ | TYMNET:JMS@F29 CA:"POPJ P," UUCP:{ames|pyramid}oliveb!tymix!antares!jms | | INTERNET: (Office-1.ARPA is no more) PHONE:Joe Smith @ (408)922-6220 | +----------------------------------------------------------------------------+