David Chord wrote in a message to Patrick McCullough:
DC> A couple of days ago I ran a little test on my system, entered a
DC> message from Max and a Message from TimEd with the computer set to
DC> the year 2K 
 PM>  Well, there's a problem right there: timEd is _not_ Y2K
 PM> compatible.  It's a known bug, and according to timEd's author, it
 PM> will not be fixed.  TimEd and NetMgr both roll over and 'die' on
 PM> Jan. 1, 2000.  
DC> netMgr I'm not so sure about, but from my experiments to date
DC> (limited tho) TimEd will not do anything worse than incorrectly
DC> display the year.
 The problem comes later, when trying to toss what timEd generates.
 Same with Netmgr, which is far more integrated into the mail database
 than timEd.
 PM>  Anyway, you'll have to use the regular BBS message system or a 
 PM> Y2K-capable mail editor and run the test again to see what will
 PM> really  happen. 
DC> You should have read my message. What I did is quoted above still. 
 Lots of other people have tested timEd, as has its author, and it seems
 clear it will fail muster, so to speak.
 Are you linked to the Artware echo?  Anyone using Netmgr should be
 concerned about its Y2K problems, IMO.
 Patrick
--- timEd 1.10
---------------