Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!MATHOM.CISCO.COM!BILLW
From: BILLW@MATHOM.CISCO.COM (William Chops Westfield)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Problem with Xmodem and 3Com terminal server
Message-ID: <12634372337.2.BILLW@mathom.cisco.com>
Date: 1 Nov 90 07:20:04 GMT
References: <9010312149.AA07742@z.nsf.gov>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

Even when transferring text files, XMODEM needs a clear 8-bit path to
accomadate its block counts and checksum.  By definition, telnet is a
7 bit protocol, and you must negotiate "binary" mode to get an 8-bit
path.  The terminal server may be refusing binary mode negotiations,
may just do binary incorrectly, or may just need configured differently.

Also, some telnet implementations ignore the "7-bit" definition, and
routinely send 8 bit data anyway.  This is useful, but means that a
telnet terminal server strictly adhering to the standard might not work
as well as one with a more flexible interpretation.  The Hosts Requirement
document was carefully worded to allow 8-bit transmission, as long as
you were doing actual "parity".

Bill Westfield
cisco Systems.
-------