I've had to do that, or something similar, reading the raw
messages.dat file. If you have an editor with a good search and
replace function, you may be able to give the file a more
readable format. In the case of the messages.dat file, carriage
returns are represented by the pi character. Doing a global
search-and-replace substituting the carriage return character for
the pi character does a pretty good job.
However, I've found there are sometimes end-of-file characters
embedded in the middle of the file, which makes it unreadable in
my editor beyond that character. Using LIST, however, I can make
separate files of everything *preceding* and everything
*following* the end-of-file character, then put them together
into one file that my editor can handle.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Judy Stein * The Author's Friend * jstein@cnct.com +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++