22-Oct-86 19:00:15-EDT,1256;000000000011 Return-Path: Received: from seismo.CSS.GOV by CU20B.COLUMBIA.EDU with TCP; Wed 22 Oct 86 19:00:04-EDT Received: from rochester.UUCP by seismo.CSS.GOV (5.54/1.14) id AA11614; Wed, 22 Oct 86 18:37:16 EDT Received: by ur-seneca.arpa id AA14564 (4.12x); Wed, 22 Oct 86 17:35:15 edt Received: by cci632.UUCP (4.22/4.7) id AA08023; Wed, 22 Oct 86 17:03:31 EDT Date: Wed, 22 Oct 86 17:03:31 EDT From: rochester!cci632!djh@seismo.CSS.GOV (Daniel J. Hazekamp) Message-Id: <8610222103.AA08023@cci632.UUCP> To: SY.CHRISTINE@cu20b.columbia.edu, SY.FDC@cu20b.columbia.edu Subject: Re: [seismo!rochester!cci632!djh@columbia.edu (Daniel J. Hazekamp): Bug in C-Kermit 4D(61)] Frank, I didn't have a copy of the protocol manual when I made the changes. The issue of control prefixes is a minor one. The problem I'm experiencing is due to the prefixing of octal 243 with a #. When RT-11 Kermit (2.2C) recieves this, it converts it to octal 343. Is the prefixing of octal 243 correct?? If so, then RT-11 Kermit must be acting improperly. I would like to be able to upgrade to Kermit-11, but alas we are stuck with RT-11 V3 which makes it near impossible to do. Thanks for the quick response, Dan 23-Oct-86 08:37:26-EDT,646;000000000001 Mail-From: SY.FDC created at 23-Oct-86 08:37:25 Date: Thu 23 Oct 86 08:37:25-EDT From: Frank da Cruz Subject: Re: [seismo!rochester!cci632!djh@columbia.edu (Daniel J. Hazekamp): Bug in C-Kermit 4D(61)] To: rochester!cci632!djh@SEISMO.CSS.GOV, SY.CHRISTINE@CU20B.COLUMBIA.EDU In-Reply-To: <8610222103.AA08023@cci632.UUCP> Message-ID: <12249078426.15.SY.FDC@CU20B.COLUMBIA.EDU> It's RT-11 Kermit that's doing it wrong. It should only do the "xor 100" business if the prefixed character is in the range 77-137 (octal), otherwise the # prefix means "take the following character literally". - Frank -------