Path: utzoo!attcan!uunet!mcvax!cernvax!ethz!forty2!poole
From: poole@forty2.UUCP (Simon Poole)
Newsgroups: comp.sys.atari.st
Subject: Re: 8th-Bit Prefixing Bug in UniTerm Kermit
Summary: Don't jump to conclusions.......
Keywords: How, to, report, a, bug
Message-ID: <344@forty2.UUCP>
Date: 26 Jun 88 20:49:07 GMT
References: <6720@cup.portal.com>
Reply-To: poole@forty2.UUCP (Simon Poole)
Organization: Exp. Physics University Zuerich
Lines: 48

In article <6720@cup.portal.com> R_Tim_Coslet@cup.portal.com writes:
...
>
>The UniTerm Kermit has the following bug in its 8th-Bit Prefixing
>Algorithm when it is Receiving...
>
Thanks for taking the trouble to report this problem and making
such a 'in depth' analysis, but as so often the reason for the effect
you are seeing is something completly different than the conclusion
you arrived at, and definitly is NOT a bug in the 8th-Bit Prefixing
Alogrithm.
>			Other Kermit		UniTerm Kermit
>
>Mode:			Sending			Receiving
>"S" Packet QBIN field:	"&"  (Prefix)		"Y"  (I can Prefix)
>
>Thus the two Kermits have agreed to do 8th-Bit Prefixing.
No, they haven't! What you CAN'T know, is that UniTerm actually
responds with the prefix character the other Kermit wants to use
if it gets the send-init packet correctlly (it only uses 'Y' if it
is initiating the transfer and doesn't need prefixing or the other
Kermit has sent 'Y' aswell (the correct meaning of 'Y' being:
 I don't need to prefix, but I'll do it if you want to...), so the 
problem is actually one of the following: 
      - UniTerm not receiving the send-init packet correctly
      - UniTerm not interpreting the contents of the send-init packet
        correctly
(later being rather unlikely, as it works without problems with
C-Kermit 4d and 4e (caveat: don't try it with 4e, it's got a few problems
with 8-bit prefixing), VM/CMS Kermit, VMS Kermit, Kermit-11 and MS-DOS
Kermit (I retested with exactlly the sequence you had problems with)).
To get an analysis of what is causing the problem, I need:
      - a copy of the log file (packets only), the first few packets
        will be enough
      - Name and version of the other Kermit
      - a list of all the settings of the RS232 port and Kermit. 

>During the transfer (about 11K Binary) the following occures...
...
Rest of letter irrelevant .......
...



-- 
----------------------------------------------------------------------------
UUCP:   ...mcvax!cernvax!forty2!poole			Simon Poole
BITNET: K538915@CZHRZU1A
----------------------------------------------------------------------------