From owner-freebsd-questions  Wed Feb 12 23:14:42 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA22712
          for questions-outgoing; Wed, 12 Feb 1997 23:14:42 -0800 (PST)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA22700
          for <questions@FreeBSD.ORG>; Wed, 12 Feb 1997 23:14:32 -0800 (PST)
Received: (from davidn@localhost)
	by labs.usn.blaze.net.au (8.8.5/8.8.5) id SAA18436;
	Thu, 13 Feb 1997 18:14:04 +1100 (EST)
Message-ID: <19970213181404.31387@usn.blaze.net.au>
Date: Thu, 13 Feb 1997 18:14:04 +1100
From: David Nugent <davidn@labs.usn.blaze.net.au>
To: rohit@cs.umd.edu
Cc: questions@FreeBSD.ORG
Subject: Re: 'tip' to a SUN.
References: <199702121916.OAA23249@darling.cs.umd.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61
In-Reply-To: <199702121916.OAA23249@darling.cs.umd.edu>; from rohit@cs.umd.edu on Feb 02, 1997 at 02:16:12PM
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Feb 02, 1997 at 02:16:12PM, rohit@cs.umd.edu wrote:
> A friend of mine is trying to 'tip' to a SUN Machine
> thru the serial port (/dev/cuaa1) on a FreeBSD box
> running 2.2.
> 
> Somehow, not all characters are able to get across.
> For example the characters 's', 'n' and '=' just can't
> seem to get across. On the other hand some other characters
> like 'e' and 'f' seem to get transferred just fine.

I'm willing to bet you have tip calling out with even
parity (which is the default), and the other machine
set to no parity.


> Would somebody know what's going on? A serial null-modem
> cable is being used (I don't think the cable is the
> problem though). My guess is that some weird encoding is 
> going on. We tried various combinations of parameters to
> stty (2 stop bits, 1 stop bit, no parity etc...) but
> nothing seemed to work. What is puzzling is that some 
> characters work and some don't.

Because they're 8-bit characters, and probably be rejected
by whatever software you're running on the other system (a
shell, or getty?).

Let's see:

	s = 0x73 = 0x01110011 = 5 bits
	n = 0x6e = 0x01101110 = 5 bits
	= = 0x3d = 0x00111101 = 5 bits
	e = 0x65 = 0x01100101 = 4 bits
	f = 0x66 = 0x01100110 = 4 bits

Yep, looks like even parity. The first three get the 8-bit
bit set to make the number of bits in the byte even, and the
latter two pass through unchanged.

Add

	parity=none

to your ~/.tiprc

Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/