PE>> Hi guys. I am sending both of you PQWK218. There seems to
PE>> be a problem with messages greater than 32k, which may or
PE>> may not be causing your problem. I recompiled under
PE>> Borland instead of Watcom and the problem went away, so I
PE>> didn't bother investigating.
BV> That's what I like to see.
BV> Real programming techniques being properly applied :)
I was bloody tired, and I wasn't going to be jacked around
by not being able to use Turbo Debugger, so I figured that
Watcom could stick it where it fits. Of course, I don't
suspect the compiler to be at fault, but there are only two
things worse than vomiting, and one of them is looking at
Mark Kimes's code.
BV> It's not really that big a problem. On the RARE occasion that it
BV> does blow up (your BIG message was the only one recently) I can
BV> always undelete the original file and I then process each PKT
BV> separately. In this instance I just scanned your PKT and then
BV> trashed it. In future, I will send you a ZIP (renamed) containing
BV> any faulty PKT files.
You can put the PKTs into a ZIP file, so long as the extension
is ZIP, not MO0 et al. And so long as they are in a ZIP file,
not PKT. PKT and MO0, TU0 etc are all treated as mail and will
be automatically processed. BFN. Paul.
@EOT:
--- Mksmsg
* Origin: none (3:711/934.9)
|