Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!van-bc!mdivax1!wilson
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Setting a 2000 year date *HELP*
Message-ID: <1991Jan14.181009.19394@mdivax1.uucp>
Date: 14 Jan 91 18:10:09 GMT
References: <17750004@hpgnd.grenoble.hp.com> <17750005@hpgnd.grenoble.hp.com>
Reply-To: mdivax1!wilson (Paul Wilson)
Organization: Mobile Data International, Richmond, B.C., Canada
Lines: 36
Return-Path: <mdivax1!news>
Apparently-To: van-bc!rnews

In article <17750005@hpgnd.grenoble.hp.com> alex@hpgnd.grenoble.hp.com (Alexis MERMET-GRANDFILLES) writes:
>Hello,
>
>Please send flames to /dev/null.
         .
         .
         .
>
>
>2)
>
>But my problem is different. Everythings works well if the date is before 2000.
>If I try to set a date after the 2000 year , the GEMDOS seems to accept
>the request , then it tries to forward it to the keyboard clock which seems
>to refuse it. Then the GEMDOS clock is set back to the previous value it had.
>
>
>Actually, If a program sets a 2000 year date with Tsettime() ,then gets the 
>date with a Tgettime() call, the Tgettime() returns the correct 2000 year date!
>
>But then, if you quits it, return to the desktop
>and run a little program that read the date, you get the previous value ???
>
>Strange isn't it.
>
>Atari users, is it reproducable on your systems ? on the TT ?
>
I have seen something similar on TOS 1.4 on my system. However, at the time
I was not all that concerned about it so I did not investigate it as thoroughly
as you have. From what you describe, I believe that the problem that I saw
is the same one.

Paul Wilson

Bang path: ...!uunet!van-bc!mdivax1!wilson
Compuserve: 72057,2374