PE> You and others can call it an "error" or a
"bug", but it is a
 PE> documented (in the source code) restriction, ever since Day 1. 

  Be so true to thyself as thou not be false to others - Francis
Bacon.

 BL> Isn't one packet the same as another? You'd only get dupes. The
 BL> doubled packet I looked at seemed okay.

 PE> By not following the documentation (in the source code), you
 PE> are going to get unpredictable results. And no, I can't predict
 PE> what they are, either. It will be attempting to process a
 PE> half-written packet, which doesn't conform to standards because
 PE> it hasn't been written yet. BFN. Paul.

  You tell it to write to the outf with each packet one after the
other, and when it comes to the outf itself, it just goes ahead and
does it. As I said, the one I looked at just added itself (what
there was of it so far) in, and moved onto the next pkt. Why would
PKT2QWK bark on that? How would it know that the messages were
repeated?

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---