franky@dutesta.UUCP (Frank W. ten Wolde) (01/05/88)
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.
First I thought my M24 had broke down, but I discovered the same
problem on another M24 as well.
Is there anyone else who has this problem? Is it an error in the M24
or could it be the clock-chip?
Thanks in advance,
Frank.
##########################################################################
Frank ten Wolde | UUCP: ..!mcvax!dutrun!dutesta!franky
Delft University of Technology |
Faculty of Electrical Eng. | "They couldn't think of a number,
Delft | so they gave me a name"
The Netherlands | -- Rupert Hine
--
##########################################################################
Frank ten Wolde | UUCP: ..!mcvax!dutrun!dutesta!franky
Delft Univ. of Tech.
Fac. of Elec. Eng. "They couldn't think of a number,
Delft so they gave me a name"
The Netherlands -- Rupert Hine Usenet_area_"Cs.I.Pc"@watmath.waterloo.edu (01/07/88)
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)
aptr@ur-tut.UUCP (The Wumpus) (01/08/88)
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