In a message of , andrew clarke (3:635/728.4) writes:
      
  ...(Edited to conserve space)...  

 ac>(so Msged 2.0x users [are there any left?] may also want to be aware of 
 ac>this problem).

Guess that leaves us 1.99L users _way_ out in left field.  

 ac>So, that's about it.  Providing the existing user support and interest 
 ac>in Msged continues, I'll stay motivated and focus on releasing a new 
 ac>version.

I've kept watch here for years hoping to find a 'better' version, but with
all the 2.xx releases revealing more bugs than I wanted to fool with, just
kept on reading.  I'd downloaded the 4.0 version some time back when Chris
got the echo re-opened, but was overwhelmed by all the 'on-screen' changes,
and hated to give up the old familiar screen format.

Now with the y2k problem 'just around the corner', I'm facing a 'forced upgrade'.

I for one will be watching for your new release, and at least hope the
provisions/instructions for displaying the 'real' .MSG number are clear, as
that's about the only feature important to _me_. 

To paraphrase an old tagline, I hate change, except from a vending maching.

      Thanks, M.

--- msged 1.99L MSC