Dave Garland wrote in a message to David Chord:
 DC> A couple of days ago I ran a little test on my system, 
 DC> entered a message from Max and a Message from TimEd 
 DC> with the computer set to the year 2K
 DC> Here's the resulting header :
 DC> Ä Local.Comments: Comments to the SysOp 
 DC> ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
 DC> Msg#:   263   of   268  - 262          Pvt Rec'd
 DC> From: David Chord                      07/Feb/1900 09:58:2
 DG>      From: Dave Garland                     Feb-09-00 01:14:25 
 DG> Wierd.  While I haven't tried it with a TimEd message (TimEd is
 DG> indeed reputed to have a Y2K problem), I just tried it with the
 DG> internal message editor, and the result didn't look like yours (see
 DG> above).  Mine only shows a 2-digit year, and shows it correctly
 DG> (i.e. "00"), in the "American" format.  
That'd be why you don't see the '19' :-) I've also discovered that TimEd 
doesn't seem to be able to display 4-digits correctly after 2k, but it does 
seem to *handle* them OK..
 DG> I've got 2 digits for the seconds, and dashes instead of slashes, 
 DG> also.  Have you customized the message edit header?  Maybe the 
 DG> problem depends on the date format selection? 
Nope, all I've done is select the NZ standard for the date. Maybe I'll change 
it to a 2-digit year field, could fix another nuisance I've been meaning to 
get onto for ages :-)
Thanks for the idea ;-)
Dave
Save your BBS! Join INTBBS_WK now! 
--- timEd 1.10
---------------