Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!watmum!smvorkoetter
From: smvorkoetter@watmum.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Kermit and Procomm
Message-ID: <1043@watmum.UUCP>
Date: Fri, 26-Jun-87 13:11:25 EDT
Article-I.D.: watmum.1043
Posted: Fri Jun 26 13:11:25 1987
Date-Received: Sat, 27-Jun-87 06:36:02 EDT
References: <12809@topaz.rutgers.edu> <739@cod.UUCP>
Reply-To: smvorkoetter@watmum.UUCP (Stefan M. Vorkoetter)
Distribution: world
Organization: U. of Waterloo, Ontario
Lines: 18

In article <739@cod.UUCP> medin@cod.nosc.mil.UUCP (Ted Medin) writes:
]In article <12809@topaz.rutgers.edu> msmith@topaz.rutgers.edu (Mark Smith) writes:
]>I recently have been having trouble with my Procomm 2.4.2 and Kermit.
]>It transfers text fine, but it has trouble transmitting binaries.
]>When I receive a binary, such as an exe or arc file, it tacks on about
]>another 1/3 the number of bytes, and the file is messed up.  I have
]>not changed any of the kermit defaults.  Can anyone help?
]
] Yes i have had the same problem. Eight bit quoting was my view of the 
]problem. The bbs said it was 8 bit no parity but sent the 8 bit quoting
]anyway and procomm wasnt looking for the quote character so it just stuck
]it in the file. The bbs was a fido and that was the real root of the problem
]they should not have been quoting if they really had an 8 bit path.

I don't think the BBS was the problem.  There is no rule anywhere in the
Kermit protocol that says you should not quote when an 8 bit path is available.
The only related rules are that you must quote when 8 bits are not available,
any you must quote when one Kermit requests it.