>> Yup. Pretty much the same here. I was running NDOS, but currently am 
>> running MS DOS 6.22, and occassionally Win4WG3.11. MsgEd must have a 
>> problem scanning 1.msg format netmail areas.

RH> Hmm... duh... let's see if Paul knows the answer...

RH> [yelling help mode on]
RH> Paul! Can you figure this one out?
RH> [yelling help mode of]

You know Andrew is in charge of Msged now?  Anyway, I don't actually run
any *.msg areas myself, but it is unlikely that *.msg fails for everyone,
which means we have to find out what is specific to you.  So, firstly you
need to find out if you have the same problem with msged.exe.  Next thing
you need to do is be able to recompile msged in order to put in some debug
lines.  If you have Borland C etc available, that is the easiest, but you
can use Pacific C, a free C compiler also.  You then need to find out how
msged reacts to an empty messagebase, and you start creating messages one
by one.  If it doesn't show the problem like that, then you will need to
zip up your netmail area that shows the problem, and use that for all
testing.

This process will take a period of months if you do it via remote debugging
via the echo.  You can speed it up by doing your own debugging, or getting
a local C expert to help you.  BFN.  Paul.
@EOT:

---

SD®¯W»