PE> FM>> This time, I hope I've captured all the input so I can
recreate and
PE> FM>> possibly track down these problems. I notice you've sent me a new
PE> FM>> PQWK222.ZIP. What does it fix?
PE>> PQWK222 fixes the problem with people leaving "To:"
out of their
PE>> netmail, so please switch to it. And if you can reproduce the
FM> OK, then it's relatively minor and I can do that at my convenience.
NO IT IS NOT MINOR AND I WOULD APPRECIATE IT IF YOU UPGRADED TO IT
*STRAIGHT AWAY* NOT AT YOUR CONVENIENCE SEEING AS IT IS A DROP IN
REPLACEMENT, AND YESTERDAY YOU SENT A MESSAGE TO BOB LAWRENCE
WITHOUT PUTTING THE To: IN THERE AND IT WENT TO ZONE 5966.
FM> AAMOI, if I send netmail to Areafix (as I did today), I don't put a To:
FM> in the first line. What will 222 do then?
AND TODAY YOU SENT A MESSAGE TO AREAFIX, AND IT WENT TO ZONE
5966 ALSO. 222 WOULD HAVE SENT IT BACK TO YOU, INSTEAD OF
LETTING IT GO TO CYBERSPACE (I DON'T KNOW WHERE THESE
MESSAGES GO).
PE>> problem with PQWK222, especially the problem with CONTROL.DAT
FM> Why do you say that? Have you made other changes to PQWK222 apart from
FM> what you said above?
No, but I don't want to debug old code, I only want to debug
the latest version.
PE>> being zero-length, I'll take a look at it. Please include an
FM> I have already reproduced *that* problem with my existing PKT2QWK; if
FM> you insist I'll verify it on 222 as well before sending you enough stuff
FM> to reproduce it yourself. However, I want to try and track down the
FM> other bit, too - PKT2QWK generating fucked indexes. As I said, I think
FM> I've captured enough to be able to reproduce that problem too, although
FM> my one attempt to date, while it did create the problem, also exhibited
FM> another weird effect - the QWK was only ~1/4 the size it should have
FM> been! I think we've got more than one bug here.
Yeah, a separate archive for each problem thanks.
PE>> archive containing the PKT files, and a batch file that calls
PE>> PKT2QWK with whatever parameters you normally use. BFN. Paul.
FM> Yeah, it'll be the minimal amount I can put together which shows the
FM> bug, but be prepared to wait an hour while it runs - more if you're not
FM> running a DX50 :-)
I will print out the message number each time and went it gets
excessive I'll put a whole lot of printf's until I find out
where the problem is. BFN. Paul.
@EOT:
--- Mksmsg
* Origin: none (3:711/934.9)
|