Subject: Re: Y2k problems on a IIgs w/ProDOS 4.0.2
Newsgroups: comp.sys.apple2
From: dempson@actrix.gen.nz (David Empson)
Date: Mon, 4 Oct 1999 13:49:42 +1300
Message-ID: <1dz5knc.1ehtuei1x5ft1cN%dempson@actrix.gen.nz>
References: <021019991844159182%bvito@ne.mediaone.net> <37ff9401.12001867@news.kico1.on.wave.home.com> <1dz4aqs.1s91h2b1czg24gN@dempson.actrix.gen.nz> <HUIJ3.9369$t%3.845342@typ11.nn.bcandid.com>
Organization: Empsoft
User-Agent: MacSOUP/2.4.1
NNTP-Posting-Host: 202.49.157.176
X-Original-NNTP-Posting-Host: 202.49.157.176
X-Trace: 4 Oct 1999 13:47:54 NZST, 202.49.157.176
Lines: 23


Randy Shackelford <shack@southwind.net> wrote:

> In article <1dz4aqs.1s91h2b1czg24gN@dempson.actrix.gen.nz>,
> David Empson <dempson@actrix.gen.nz> wrote:
> 
> >There have never been reports of Y2K problems with the IIgs internal
> >clock.  I just tested it on my ROM 3, and it rolled over perfectly
> >happily.
> 
> But my understanding is that having the year field zero in dates is considered
> an invalid date i.e. <NO DATE>.

OK, but that isn't a problem with the clock, per se, but with
applications which have not been updated to comply with ProDOS Technote
#28.

Some clocks (and clock drivers) may have their own problems (bogus day
of the week, for example), but the IIgs clock is not one of them.

-- 
David Empson
dempson@actrix.gen.nz
Snail mail: P O Box 27-103, Wellington, New Zealand