🚀 go-pugleaf

In  <792@stag.UUCP>, dal@syntel.UUCP (Dale Schumacher) writes:

> There is a nasty bug that crops up when you are working with both clocks
> at the same time.  If you read the system date and time, then read the
> keyboard time, and immediately set the system date and time, the KEYBOARD
> clock will stop counting and seems to set itself to an unusual value.
> If you read the keyboard clock first, then the system, and then set the
> system time, everything works just fine.

I think I was bitten by this on my system with a 60MB Supra disk with
built in clock. I would set the clock using the supplied SUPCLKRD and
then find that it seemed to have stuck. I checked it against all my
other startup programs and desk accessories and eventually discovered
that the problem only occurred with ROCP.ACC, the (extremely useful)
read only control panel accessory. With great regret I had to stop
using it. I've no idea if a fix is possible but if the author of ROCP
is listening ... :-)
-- 
Leila Burrell-Davis, Computing Service, University of Sussex, Brighton, UK
Tel: +44 273 678390   Fax: +44 273 678335  JANET: leilabd@uk.ac.sussex.syma
ARPA: leilabd%syma.sussex.ac.uk@nsfnet-relay.ac.uk
BITNET: leilabd@syma.sussex.ac.uk      UUCP: leilabd@syma.uucp