home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.acorn
- Path: sparky!uunet!paladin.american.edu!news.univie.ac.at!hp4at!mcsun!sun4nl!utrcu1!infnews!kortink
- From: kortink@cs.utwente.nl (John Kortink)
- Subject: Arc's RTC
- Message-ID: <1992Nov5.121703.1830@cs.utwente.nl>
- Sender: usenet@cs.utwente.nl
- Nntp-Posting-Host: utis96
- Organization: University of Twente, Dept. of Computer Science
- Date: Thu, 5 Nov 1992 12:17:03 GMT
- Lines: 36
-
- In article <1992Nov3.133310.27976@dcs.warwick.ac.uk>
- gothick@dcs.warwick.ac.uk (Matthew B. M. Gibson) writes:
-
- >Since I upgraded to RISCOS 3.10, every time I turn off the computer, it loses
- >the clock setting. All the configurations stay, and I've just replaced the
- >betteries to make sure it wasn't them at fault.
-
- >I have an A440/1 (ARM3) and I've checked for any RISCOS 2 software left around
- >which might be doing silly things. Any suggestions?
-
- The Real Time Clock itself is most probably duff and could, conceivably, be
- the result of messing about inside the Archimedes (eg static). However, I'd
- suggest it's more likely coincidence that it's chosen now to 'become late'.
-
- I recently had the same effect on an 'old' A440 and had to replace the RTC
- chip. Assuming the 440/x also uses the same clock (PCF8583 I think), you
- should first check the voltage on pin 8 of the RTC. If this shows about 2.8
- V then it's almost certain that you'll have to replace the RTC. Luckily,
- replacement is easy, just a matter of unsoldering/resoldering the clock.
- Nevertheless, I would advise 'socketing' the new chip on the board just in
- case the same thing should ever occur again.
-
- >Thanks,
-
-
- >Matt
-
- My pleasure,
-
- Les Currell
-
- currell@mpi-muelheim.mpg.dbp.de
-
- !!! All flames will be incinerated !!!
-
-
-