Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!ncrlnk!ncrcae!hubcap!gatech!bloom-beacon!apple!bionet!agate!ucbvax!UIAMVS.BITNET!AWCTTYPA
From: AWCTTYPA@UIAMVS.BITNET ("David A. Lyons")
Newsgroups: comp.sys.apple
Subject: GS/OS date bug (31-mmm-yy)
Message-ID: <8810112043.aa00645@SMOKE.BRL.MIL>
Date: 13 Oct 88 10:52:35 GMT
Article-I.D.: SMOKE.8810112043.aa00645
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26
X-Unparsable-Date: Tuesday 11 Oct 88 3:57 PM CT

>Date:         Tue, 11 Oct 88 00:56:00 EDT
>From:         TMPLee@DOCKMASTER.ARPA
>Subject:      final(?) clue, weird one (lost date)

>Before giving up tried one more thing.  Very carefully set my clock back
>to Aug.  31, 1988 (wouldn't it be nice to be able to to do that in
>reality) and created a one line basic file in /ram5.  sure enough, the
>file exhibited all the properties of the one I had noticed before [...]
>your serve, experts.

I repeated your experiment successfully and found that the ProDOS FST under
GS/OS rejects *any* date that is the 31st of *any* month!  Will report this
to Apple prompto-style.

(By the way, 1-Jan-00 is just what an application gets trying to convert a
date of $0000 (which really means "no date available") into a legible date;
so some applications will show "unknown" or "no date" and some will show
1-Jan-00.  The bug in this case was the ProDOS FST returning $0000 when it
determined [incorrectly] that the date was not valid.)

>TMPLee@dockmaster.arpa

--David A. Lyons              bitnet: awcttypa@uiamvs
  DAL Systems                 CompuServe:  72177,3233
  P.O. Box 287                GEnie mail:    D.LYONS2
  North Liberty, IA 52317     AppleLinkPE: Dave Lyons