Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!pasteur!agate!ig!uwmcsd1!marque!uunet!portal!cup.portal.com!R_Tim_Coslet From: R_Tim_Coslet@cup.portal.com Newsgroups: comp.sys.atari.st Subject: 8th-Bit Prefixing Bug in UniTerm Kermit Message-ID: <6720@cup.portal.com> Date: 21 Jun 88 08:03:01 GMT Organization: The Portal System (TM) Lines: 63 XPortal-User-Id: 1.1001.4086 I have encountered a bug in UniTerm's Kermit File Transfer Protocol. I thought other users of UniTerm might like to know about this Bug, so below is a copy of the e-mail I sent to Simon Poole on the problem I encountered. =============================================================================== I am currently using UniTerm 2.0c 008 The UniTerm Kermit has the following bug in its 8th-Bit Prefixing Algorithm when it is Receiving... 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. During the transfer (about 11K Binary) the following occures... Data in file: 26 B0 (Hex Bytes) Other Kermit Sent: #&&0 (Ascii in "D" Packet) UniTerm Kermit Wrote: 66 26 30 (Hex Bytes) Somehow the UniTerm Kermit is converting (what should be) 2 Bytes of data into 3 Bytes (also UniTerm Kermit failed to set ANY 8th-Bits anywhere in the file it wrote!). It looks to me like UniTerm Kermit does not recognize that it has agreed to do 8th-Bit Prefixing, and has 1) controlified the first "&" even though it isn't a "control character", 2) then saved the "&0" directly without decoding the Prefix. The UniTerm Kermit does correctly perform 8th-Bit Prefixing when it is Sending... UniTerm Kermit Other Kermit Mode: Sending Receiving "S" Packet QBIN field: "Y" (I can Prefix) "&" (Prefix) Thus the two Kermits have again agreed to do 8th-Bit Prefixing. During the transfer (about 11K Binary) the following occures... Data in file: 26 B0 (Hex Bytes) UniTerm Kermit Sent: #&&0 (Ascii in "D" Packet) Other Kermit Wrote: 26 B0 (Hex Bytes) I have verified this Bug both in UniTerm 2.0c 008 and in an old UniTerm 2.0a that I still have available. If it would be any help in debugging this problem, write me and I will send you a UUENCODED copy of the about 11K Binary file I tested it with. R. Tim Coslet Usenet: R_Tim_Coslet@cup.portal.com BIX: r.tim_coslet