Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.sys.ncr
Subject: Re: Does uucp have to be slow?
Message-ID: <110@raysnec.UUCP>
Date: 23 Oct 90 13:52:47 GMT
References: <4221@lib.tmc.edu>
Organization: IRS/CI - Technical Solutions Branch
Lines: 24

jmaynard@thesis1.hsch.utexas.edu (Jay Maynard) writes:

>I was able to get the two machines talking. There are two problems: 1) It
>won't run over 1200 BPS, and 2) it won't run for more than a few hours. In
>both cases, the failure mode is the same: The AT (running Microport System
>V/AT 2.4, with HDB) eventually hangs, and, if I used Uutry to start the
>connection, reports an "alarm 1". The Tower simply gives up, leaving the
>status "CONVERSATION" in the STST.* file. I have to reboot the AT to clear
>out the uucico process.

	Question: Are we talking about multiple files totalling ~30 MB
or one large file? Both the NCR and Microport may have a ulimit set down
in the 2 MB range (uPort's old default). I'd run my old uPort 2.3 with
HDB regularly at 2400 baud, passing many megabytes without problem provided
I didn't exceed the ulimit. "alarm" messages can have many causes, any of
which can represent failure to send or receive a packet. Connect the two
boxes serially if you can; if that works, push the speed higher.

>Any suggestions out there? Should I have the Tower call the AT? Should I jump
>through the hoops required to get HDB on the Tower (I don't expect the
>installation to be difficult, but getting the file to the Tower may be)?

	HDB UUCP is a wonderful enhancement to the standard version.
Install it unless you are aware of problems with NCR's implementation.