CG>>> The FTS file I have says the .MSG format should be NULL
 CG>>> terminated.

 >> what FTS file is that? there is not one that lays out the *.MSG
 >> file format specifically as the FTSC is not concerned with local
 >> storage issues.

 ac> On the contrary, FTS-0001 documents the *.MSG format explictly,
 ac> including the required null termination of the user text.

on the contrary... FTS-0001 defines "a stored message" that is
also of the same format as packed messages in a FTN type 2 style PKT. no
mention is made that this is *.MSG format. indeed, that section starts
out...

===== snip FTS-0001.015 =====
B. Application Layer : the System from the User's View

   The application layer is outside the domain of a FidoNet standard, as it
   is the layer that the user's application sees as opposed to what FidoNet
   sees.   In  recent  months,  there  has been  sufficient  confusion and
   discussion  about  the  format  of  data at this level  to  warrant the
   description  of the data structure, the message as it is stored by Fido,
   SEAdog, and Rover.

   Perfectly valid FidoNet systems may be implemented whose stored messages
   differ greatly from this format.
=============================

i stand, once again, by my statement above... -=B-)

yes, i do also agree, that what is detailed in FTS-0001.015 section B is
the same basic format of a *.MSG message but it is not specifically defined
as "the *.MSG spec" >

)\/(ark