PE> Tobruk reject a packet of messages from you today, because
PE> the message origin was wrong (in the header).  The reason

FM> Can you tell me what it was, so I can resend it (modified of course)?

Didn't I mention?  I modified Tobruk to make it accept the
message anyway.  That's why I run Tobruk - total control.

PE> it is wrong in the header is because of a bug in PQWK.  I
PE> have modified PQWK, and will send it to Brenton for testing

FM> Send it to me, too. I don't mine guineapigging that.

Ok, I'll give you about 10 seconds to reply to this message,
and then I'll look at releasing it.

PE> isolated the text for the second bug yet (as I asked)?
PE> BFN.  Paul.

FM> Sent to you just now.

I finally figured out what you were probably doing - putting it
into "Special Requests".  If the file is for *me* because you
are talking to *me* about it, then you can just send the file,
no need to send a .TIC file, as either way I have to get them
out manually.  Anyway, a quick hexdump of your reply packet
shows a whole lot of NULs.  That is sure to screw up PQWK's
search functions.  You could say that PQWK could convert NULs
(probably illegal) into spaces or something, but I won't be
modifying PQWK to do that.  Your options are:

1. Use proper software (preferred)
2. Change QWK reader to one that doesn't generate nuls
3. Find out what quote string you are using, and find out if
you have done anything wrong that would cause NULs to appear.
4. Make your quote string longer or something to see if the
NULs get replaced with other characters.
5. Change PQWK yourself
6. Get someone else to modify PQWK
7. Rewrite PQWK
8. Use Bob's PQWK
9. Use proper software (preferred)

MSGED/SQ 3.30 is here and now, it's had extensive work done on
it, it's public domain, and I actually use it myself, so am able
to test it properly (ie live).

PE> P.S. For anyone waiting for replies in AUST_AVTECH, I have
PE> just left the message pointer where it is and will go into

FM> Didn't realise there was a problem there, or are you saying it's replies
FM> from you which you haven't been able to get around to doing?

It is replies from me.  I haven't got the energy to reply to
millions of messages.  That will have to wait.

PE> the area when I have finished work currently underway on
PE> PDPCLIB.  Oh, and also I found a bug in Tobruk today, and I
PE> have to think very hard about how to fix it, so that has to
PE> be done too.

FM> So many bugs, so little time. :-)

The bug in Tobruk was more like two-bugs bug, which is why it
took 2 separate code changes for me to fix it, but it is fixed.
PDPCLIB is looking good, with no bugs that I know about (I
haven't tested lots of stuff though, just the main stuff that
I use).  BFN.  Paul.
@EOT:

---