Xref: utzoo comp.mail.uucp:3236 comp.unix.questions:14109
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!bellcore!texbell!vector!killer!kcdev!gentry
From: gentry@kcdev.UUCP (Art Gentry)
Newsgroups: comp.mail.uucp,comp.unix.questions
Subject: Re: problems with uucp
Summary: have had same problem - here is a possible solution
Keywords: alarms
Message-ID: <782@kcdev.UUCP>
Date: 7 Jun 89 20:19:22 GMT
References: <1526@infmx.UUCP>
Organization: AT&T Kansas City, MO.
Lines: 22

In article <1526@infmx.UUCP>, jms@infmx.UUCP (John Stephens) writes:
> I am having a problem with some (but not all) of my uucp connections.
> After negotiating a login and begining the protocol, we are getting
> a number of alarms instead of packet completions (CY ?).  This occurs
> at random times, early in the transmission and both when sending and
> receiving  files.
> 
> [additional verbage deleted]

I have had the same problem 2 times and both times it was the other ends'
modem eating dc1/dc3 characters.  Some modems allow you to set the flow 
control directly within the modem, for uucp transfers, this must be disabled
since uucico expects to see the dc1 character in its packet.  Turning off
this option in the far end modems cleared up the problem for me both times.



-- 
| R. Arthur Gentry     AT&T Communications     Kansas City, MO     64106 |
| Email: killer!kcdev!gentry         ATTMail: attmail!kc4rtm!gentry      |
| The UNIX BBS: 816-221-0475         The Bedroom BBS: 816-637-4183       |
| $include {std_disclaimer.h}        "I will make a quess" - Spock - STV |