Xref: utzoo comp.sys.amiga.programmer:1724 comp.sys.amiga.hardware:7515
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: Is OS supposed to zero the TOD clock registers intermittently?
Keywords: Intuition TOD clock bugs race condition
Message-ID: <20076@cbmvax.commodore.com>
Date: 24 Mar 91 07:44:16 GMT
References: <1991Mar21.175806.23729@daffy.cs.wisc.edu>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 23

In article <1991Mar21.175806.23729@daffy.cs.wisc.edu> pochron@cat17.cs.wisc.edu (David Pochron) writes:
>
>In my (apparent) never-ending quest to figure out why my clock keeps going
>haywire when I drag windows around, I decided to look at the 8520 registers

>3) A hardware problem - A2630 timing problem, faulty 8520?
>   I don't think it is a hardware problem though, since the 8520 seems to work
>   fine, and the error is easily reproducible on my system.  Don't want to
>   think about a problem with the A2630...

	In the past, most cases I've heard of like this (things go haywire
when dragging things) have been caused by blown CIA chips.  I suspect that
if you were to swap them you'd see different behavior.

	It sounds very much like a CIA hardware bug to me (but remember, I'm
a software guy...).

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)