Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pt.cs.cmu.edu!cadre.dsl.pitt.edu!pitt!unix.cis.pitt.edu!ejkst
From: ejkst@unix.cis.pitt.edu (Eric J. Kennedy)
Newsgroups: comp.sys.amiga.tech
Subject: Re: 1.3 AUX: Device
Message-ID: <19606@unix.cis.pitt.edu>
Date: 18 Sep 89 02:06:23 GMT
References: <1285@cs.rit.edu>
Reply-To: ejkst@unix.cis.pitt.edu (Eric J. Kennedy)
Distribution: usa
Organization: Univ. of Pittsburgh, Comp & Info Services
Lines: 36

In article <1285@cs.rit.edu> txm2744%ucss@cs.rit.edu (Thomas A. Mikalsen) writes:
>I have my roomates and my Amiga connected with a NULL modem serial cable.
>I can do file transfers using a terminal program with no problem.  I can't,
>however, get the AUX: device to work.  Has anyone played around with this???

I use AUX: occasionally, with a vt240 terminal and null modem.  It's the
same null modem cable that I used when connecting two computers (Amiga
and IBM) earlier.  

I mount aux: in my startup-sequence.  (Doesn't take more than a few
bytes until AUX: is accessed, then the driver is loaded.)  My 
mountlist entry looks like

#

 AUX:   Handler = L:Aux-Handler
	Priority = 5
#

Make sure that the remote "terminal"  (The terminal program on the
"remote" amiga) is set to the same baud, parity, bits, and stop bits as
your Preferences serial settings on the host amiga.  Then "newcli aux:"
should open a cli on the remote amiga.

If you use 9600 baud, then the remote terminal is automatically
configured to run ROM-Wack if you need to do debugging.  I can't seem
to run reliably any faster than 9600, plus the vt240 isn't fast enough
anyway;  so I use 9600 baud.  If you're having trouble getting it to
work, gear down to 300 baud, it's much more forgiving about parity,
etc.

Hope this helps.

-- 
Eric Kennedy
ejkst@cis.unix.pitt.edu