Xref: utzoo comp.sys.att:1902 comp.mail.uucp:877 comp.unix.wizards:5884 Path: utzoo!mnetor!uunet!husc6!rutgers!ames!sdcsvax!ucsdhub!jack!crash!ford From: ford@crash.cts.com (Michael Ditto) Newsgroups: comp.sys.att,comp.mail.uucp,comp.unix.wizards Subject: Re: HDB UUCP fails on AT&T 3B2/310 Message-ID: <2211@crash.cts.com> Date: 27 Dec 87 19:55:07 GMT References: <75@quincy.UUCP> Reply-To: ford%kenobi@crash.CTS.COM (Michael Ditto) Organization: Crash TS, El Cajon, CA Lines: 35 Keywords: HDB, UUCP, fails, bombs, SLAVE MODE Summary: Same happened to me with "normal" uucp (non-HDB) In article <75@quincy.UUCP> lenny@quincy.UUCP (Lenny Tropiano) writes: > 1. Sending compressed binaries (16-bit compression) with > Penril modem 8216 from an AT&T 3B2 to another AT&T 3B2 > long distance, I receive the imfamous: > > CONVERSATION FAILED > IN SEND/SLAVE MODE INPUT FAILURE This sounds like something I've seen happen with "normal" (non-HDB) uucp. I had a large (almost 1 Meg) compressed tar archive that I tried to send to another system. The transfer was attempted five different times, to two different systems, and never worked. I don't remember if the transfer always stopped at a certain point (the only way to tell would be from the call duration). The logfile showed the above "SEND/SLAVE MODE INPUT FAILURE" message every time. All three systems were Unix PCs running the normal uucp. I split the large file into four pieces and they all went through on the first try. I was suspecting that there might be some sequence of bytes that interferes with the "G" uucp protocol, but I doubt that spliting the file would have fixed that. (I split the file with dd(1), so the smaller files contain the exact same bytes as the original, just split up). I have transfered files larger than this before without problems. Does anyone know if the uucp protocol is at all data-dependent? I thought it basically just packetized the file into 64-byte chunks with a header, or something like that. -- Mike Ditto -=] Ford [=- P.O. Box 1721 ford%kenobi@crash.CTS.COM Bonita, CA 92002 ford@crash.CTS.COM