BL> A single dropped message will show up in the converter itself,
 BL> and ought to be checked there.

 RS> Nope, we are talking about an overall check on anything that
 RS> might have gone wrong, completely separate from the work being
 RS> done. The best way to do that is assume nothing, count the
 RS> number of messages that go in, compare that with the number
 RS> that come out, as long as thats possible. Nothing else gives
 RS> the same level of overall check.

  I could just run it twice... no! I'll run it ten times, like having
ten clocks in the house. No one knows the right time.

 BL> RTL gave me the poos yesterday in AVTech, and it only took
 BL> three lines of code to add a twitter to the converter, but 150
 BL> messages became 127, and it ruins all my ratios!

 RS> Sure, but thats another design questions. You can argue that
 RS> its not that desirable to do that in a PKT->QWK converter coz
 RS> its not possible to conveniently make visible what is made
 RS> invisible.

  My definition of a twitter is one that removes all the twitted
messages, permanently. That's the whole point... gone!

 RS> IMO if you want a fancy twitter it has to be in the reader, not
 RS> the converter. If only coz the fancier it gets the more likely
 RS> you are to want to tune it.

  I read all information from a dat file. It's very easy to twit Area
and To/From, just in the dat file.

 RS> Nope, you certainly do have to actually scrutinise the unzipper
 RS> error code, not just ignore it like is done now, but thats dead
 RS> easy.

 BL> How?

 RS> if errorlevel nn goto xxxx

  That only works *inside* the code. How do I get it from PKUNZIP to
my program?

Regards,
Bob

___ Blue Wave/QWK v2.12
@EOT:

---