Xref: utzoo comp.dcom.modems:1725 comp.mail.uucp:1233 unix-pc.uucp:9
Path: utzoo!utgpu!water!watmath!clyde!mtune!icus!ditka!kls
From: kls@ditka.UUCP (Karl Swartz)
Newsgroups: comp.dcom.modems,comp.mail.uucp,unix-pc.uucp
Subject: UUCP dies on binary files via PC Pursuit
Keywords: PC Pursuit
Message-ID: <236@ditka.UUCP>
Date: 14 Apr 88 08:32:47 GMT
Reply-To: kls@ditka.UUCP (Karl Swartz)
Organization: Pittsburgh Fish Hackery, Pittburgh, PA
Lines: 34


One of the sites I talk to via PC Pursuit receives a partial
news feed from ditka.  Occasionally, a file has refused to
go across.  In addition to compressed news batches, I've seen
this with other compressed files.

Some investigation revealed that each such file apparently
caused uucp to trip at the same place every time.  None of
the files were excessively large.

Further investigation revealed that (a) I could ship the
same file to the Sun-3/160 at work and back without incident,
and (b) I could ship the file to the remote site via normal
long distance, again without incident.

I thus conclude that PC Pursuit is the culprit.  The only
PAD parameter I've set is 1:0.  Somewhere 10:0 seemed like
it might help (don't remember what that is at this point),
but it didn't make any difference.  Changing the batching
to -c7 (7-bit batches) has worked so far, but maybe that's
just luck.

Any ideas?

BTW, ditka is a 3B1 running 3.51a software and the remote
site is another 3B1, with 3.50 software.  Both are using
the on-board modems (yes, I know they suck, my TrailBlazer
is on order) and stock uucp (no HDB).

-- 
Karl Swartz		|UUCP	decvax!formtek!ditka!kls
1-412/937-4930 office	|	{pitt,psuvax1}!idis!formtek!ditka!kls
			|BIX	kswartz
"I never let my schooling get in the way of my education."  (Twain)