From owner-freebsd-questions  Wed Feb 12 11:16:31 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA20889
          for questions-outgoing; Wed, 12 Feb 1997 11:16:31 -0800 (PST)
Received: from darling.cs.umd.edu (10862@darling.cs.umd.edu [128.8.128.115])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA20882
          for <questions@freebsd.org>; Wed, 12 Feb 1997 11:16:28 -0800 (PST)
From: rohit@cs.umd.edu
Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88)
	id OAA23249; Wed, 12 Feb 1997 14:16:12 -0500 (EST)
Date: Wed, 12 Feb 1997 14:16:12 -0500 (EST)
Message-Id: <199702121916.OAA23249@darling.cs.umd.edu>
To: questions@freebsd.org
Subject: 'tip' to a SUN.
Cc: rohit@cs.umd.edu
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

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.

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.

Any help appreciated!

Thanks.

--rohit.