Path: utzoo!utgpu!water!watmath!221.162.fido!Usenet_area_"Cs.I.Pc"
From: 221.162.fido!Usenet_area_"Cs.I.Pc"@watmath.waterloo.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: M24 Clock wraps to 1984; Info needed
Message-ID: <16198@watmath.waterloo.edu>
Date: 7 Jan 88 14:35:18 GMT
Sender: ugate@watmath.waterloo.edu
Lines: 43

From Usenet: rutgers!rochester!ur-tut!aptr
From: aptr@ur-tut.UUCP (The Wumpus)
Newsgroups: comp.sys.ibm.pc
Subject: Re: M24 Clock wraps to 1984; Info needed
Keywords: Olivetti M24 AT&T6300 Clock
Message-ID: <789@ur-tut.UUCP>
Date: 8 Jan 88 03:50:44 GMT
References: <1064@dutesta.UUCP>
Reply-To: aptr@tut.cc.rochester.edu.UUCP (The Wumpus)
Organization: Univ. of Rochester Computing Center
Lines: 27

In article <1064@dutesta.UUCP> franky@dutesta.UUCP (Frank W. ten Wolde)
writes:
>    I probably found a structural fault in the Olivetti M24 Computer
>(AT&T6300 ??).
>It seems the clock-chip (MM58174AN) on my computer refuses to accept 
>1988 as the current year. After some inspection it appears that all 
>years are mapped on 1984-1987.

I have a Xerox 6064 (also and Olivetti M24) and my clock had been giving
me the same sort of problem.  It resets the date to 1980.  This bug does
seem to be somewhat strange because it depends when I try reading the system
clock.  I am currently running PC-DOS 3.3 and using a PD program called
ATTCLK to read the system clock.  My father is running a similar setup and
has similar problems with the clock.

After consulting the Xerox Tech. Ref. Man.  I discovered that the clock chip
seems to only keep track of years by LEAP_YEAR + {0 | 1 | ... | 7}.  This
would account for the 1988 -> 1980 problem.  

If anyone has any other info that may shed light, please let me know.

Thanks,

-- 
The Wumpus        UUCP:   {cmcl2!decvax}!rochester!ur-tut!aptr
                  BITNET: aptrccss@uorvm
		  Internet: aptr@tut.cc.rochester.edu
Disclaimer: "Who? When? Me? It was the Booze!"  - M. Binkley

--- via UGate v1.6
 * Origin: watmath (221/163)