home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!uvaarpa!darwin.sura.net!spool.mu.edu!hri.com!noc.near.net!ns.draper.com!news.draper.com!MVS.draper.com!SEB1525
- From: SEB1525@MVS.draper.com (Steve Bacher)
- Newsgroups: bit.listserv.ibmtcp-l
- Subject: Re: Problem with AIX 3.2 telnet
- Message-ID: <19930127081143SEB1525@MVS.draper.com>
- Date: 27 Jan 93 13:11:00 GMT
- References: <IBMTCP-L%93012704341167@PUCC.PRINCETON.EDU>
- Sender: MVS NNTP News Reader <NNMVS@MVS.draper.com>
- Reply-To: seb1525@support4.draper.com
- Organization: Draper Laboratory
- Lines: 18
- Nntp-Posting-Host: mvs.draper.com
-
- In article <IBMTCP-L%93012704341167@PUCC.PRINCETON.EDU>,
- LDW@USCMVSA.BITNET (Leonard D Woren) writes:
-
- >Yep. I was going to suggest that speed might be the problem, since
- >that looks like what happens here when the speed comes up wrong when
- >connecting to our Micom port contention unit. I was told many years
- >ago to enter U (upper case) as the first character -- something about
- >that bit pattern which allows the speed to be determined correctly. I
- >have no idea why it works, but "U" has never failed for me, where C/R
- >fails something like half the time.
-
- May have something to do with the fact that the ASCII bit pattern for
- uppercase U is binary 01010101 (hex 55), and perhaps the alternating
- zero and one bits aid the connection in determining the line speed.
-
- --
- Steve Bacher (Batchman) Draper Laboratory
- Internet: seb@draper.com Cambridge, MA, USA
-