This is a complaint caused many mostly by ‘rogue’ module chatting to a IIC train as well as wrongly environment a postponement bit upon a RTC carry out register. Symptoms of this function have been which a time is regularly a same each time we reboot as well as a module time tends to run somewhat delayed (losing about a notation each hour or so.). If we have been experiencing these symptoms this module should restart your RTC time :-
REM poke RTC carry out register
REM Bit 0 1
REM 7 Count ResetDivider
REM 6 Count HoldLastCount
REM write 0 for normal operation, write &80 or &40 freezes RTC
DIM cmosdata% 16
REM write 0 twice to RTC, initial 0 is address- carry out reg
REM second is carry out reg worth 0 is default i.e. time on
SYS &240, &A0, cmosdata%,2
You will need to reset a time after using this module though hopefully your RTC will keep a scold time from here upon in.
If a same symptoms endure after perplexing this module hit your internal Acorn play as something some-more critical has left wrong. Note which to check which a symptoms have been sustaining we contingency reboot your appurtenance after using this module as well as carrying set a time. This is due to a approach RISC OS maintains a ‘soft’ duplicate of a genuine time time as well as until we reboot it will not be viewable either your RTC has in truth proposed operative again.
Article Source: レジストリクリーナー