BL> tried it manually, just overwriting the message with spaces,
 BL> and it seems to work okay, but I'm a worried there may be a
 BL> trap for young players (and poor old pensioners).

 PE> Yes, that's a very bad thing to do. You are essentially
 PE> screwing up the packet by doing something like that. And if you
 PE> screw up the packet, different programs will do different
 PE> things. Tobruk would stop processing and tell you that your
 PE> packet is screwed. Other programs just ignore that message and
 PE> try to resynch.

  PKT2QWK doesn't seem to mind at all. If I erase the message in the
PKT it gets upset and wipes the whole packet, but if I just write
spaces on top of the twit's message, starting from the date to the
next date, it ignores the spaces and makes up a perfectly good QWK
packet.

  In fact, I've got it working. Rod no longer exists!

  I wrote it in Visual Basic, but I'll go back and translate it to C,
seeing there's no need for the VB graphics. This is fun!

 BL> 2. If not, what is?

 PE> 02 00.

  Unfortunately, you are wrong. Your packets have got lots of 02 00 in
them, and not all of them at the beginning of messages. I'll have a
think about it. How about 02 00 00 00 00?

  What identifies the end of the packet? Your ones have 0D 00 00 00 
but you'll only tell me it's hex for "Merry Christmas."

 BL> 3. Will over-writing spaces between the C702... etc damage the
 BL> packet?

 PE> Yes.

  Works for me... but I'll freq the specs anyway.

 BL> 5. Is true love the most important thing in the Universe? (I
 BL> just threw that in, on the offchance you'd know).

 PE> No, it is just one of the things. Savate is equally as
 PE> important. BFN. Paul.

  Savate? I've got some Sauterne. Will that do?

Regards,
Bob


___ Blue Wave/QWK v2.12
@EOT:

---