Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!portal!cup.portal.com!Arved
From: Arved@cup.portal.com (Arved Guido Grass)
Newsgroups: comp.sys.amiga
Subject: AmigaUUCP
Message-ID: <17848@cup.portal.com>
Date: 2 May 89 15:22:26 GMT
Distribution: na
Organization: The Portal System (TM)
Lines: 46


     I have been trying to set up AmigaUUCP between two Amigas for a while
now, and would like to pass on my observations for comments on how others
have overcome these potential bugs.  These may be particularities of Amigas
talking to each other, or they may be root problems in the software.

     Before I begin, let me praise the work that has already been done with
this package.  The following is provided in this forum not to bash any
programmers, but to exchange information on the software's shortcommings.
All observations are based on two Amigas running AmigaUUCP version 0.50.

     1.  If a connection should fail for some reason, the host Amiga needs
to be rebooted (the Amiga that is polled).  Reasons for being unsuccesfull
can be many, from improper login, to breaking the polling Amiga.  When in 
"receive mode," AmigaUUCP is very particular about what happens, and although
it will drop carrier and hang up O.K., and while the modem will answer O.K.
for the next caller, it will not provide a login for the second caller.

     2.  The polling machine must not run with a debug value of 0.  This also
means that uupoll will not work between two Amigas.  uucico may be run without
any debugging options on the receiving end, but a debug level of at least 1
must be used on the polling Amiga.

     3.  There appears to be some problems with the data that is exchanged
after mail and other files are sent.  This was carefully observed with debug
level 9 on both machines, and we discovered that in the last data exchanges,
the Amiga polling would not send the expected characters to the host Amiga.

     4.  Node names of 8 or more characters are not allowed.  I "had my heart
set" on "daylight" as my machine name, but may have to settle for "sunset,"
or some other such nodename.

     5.  NOT AMIGAUUCP related:  the mount command from ARP 1.3 does not
properly mount the null: device required by AmigaUUCP.  Substitution of the
standard MOUNT from AmigaDOS 1.3 seems to cure this problem.  It may be a
problem with ARPs MOUNT command, or an incompatibility with some other
background task (Arexx, HandyIcons, Conman, SRT, or the fact that all of the
above programs are being run from Wshell.  Then again, it could be the fact
that I _am_ using ARP).
 
     I am NOT a unix or uucp wizard, so if any of the above is due to some
lack of knowledge about unix or uucp, please enlighten me.  I would rather
replies be via E-mail, and if response warrents, I will post a followup.

- Arved     Arved@cup.portal.com     sun!portal!cup.portal.com!Arved
uucp node under construction.  This is a detour.  Flagman ahead.