🚀 go-pugleaf

In article <40671730@okapi.sub.org> "Peter Vohmann" <piet@okapi.sub.org> writes:
> For several months I've been getting errors about news batches
> with a bad checksum. This happens on a weekly or even daily basis
> up to once in a uucico session. I'm getting used to gzcat'ing the
> bad batches out, and most often the end of the news file is
> garbled.

Once the batch generates a bad checksum, gcat'ing the batches will
give you garbage. The way the encoding in a batch works, if a
compressed block isn't terminated properly you'll get garbage at
the end.

> The modem (USR Sportster v32bis) uses error correction, my feed
> (Unix W/ current Taylor) runs Zyxels. I use G-Protocoll with
> large window sizes. I've tried the internal or the ckptss; I've
> turned serial speed down to minimize errors between modem and
> computer, but no-no. The errors repeat with someone I feed in
> turn.
>
> I used uucicos of 1.17b as well as wUUCP, but I believe the
> g protocoll engines are all the same.

They are quite close, although not identical.

> I'm at my wit's end. I still receive corruptet files without
> being flagged, corrected or rejected by uucico. Has anyone had
> happen something like this, or knows enogh of uucico internals to
> comment on this?

I doubt _very_ highly that it's a UUCICO issue. More likely a
cable problem, or a buffer problem on your end.
--
  //   Michael B. Smith
\X/    mbs@adastra.cvl.va.us