Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!daffy!rt5.cs.wisc.edu!pochron
From: pochron@rt5.cs.wisc.edu (David Pochron)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Is OS supposed to zero the TOD clock registers intermittently?
Summary: Ooops!  I posted the wrong addresses!
Keywords: Intuition TOD clock bugs race condition
Message-ID: <1991Mar22.165736.28132@daffy.cs.wisc.edu>
Date: 22 Mar 91 16:57:36 GMT
References: <1991Mar21.175806.23729@daffy.cs.wisc.edu> <1991Mar22.011550.23658@watdragon.waterloo.edu>
Sender: news@daffy.cs.wisc.edu (The News)
Organization: U of Wisconsin CS Dept
Lines: 26

In my message 1572, I didn't give the correct address values for the TOD
clock registers...I guess that is what happens when you try to commit these
things to memory!  :-)

I meant to say registers at $BFE801, $BFE901, $BFEA01, the 60-hz event timer
registers, and not the Hbeam sync registers.

In any case, I have been using the above registers, but I just didn't
post the addresses here correctly.


I went ahead last night and wrote a program called "ClockGuard" and it catches
many of the times that something bangs a random value into the TOD clock
registers, tries to fix it, and flashes the screen yellow for a second.
(You wouldn't believe the number of programs that trash the clock registers!)

Problem is, even though it is detecting all the "bangs", it doesn't always
correct the problem.  This weekend I will post the source, and maybe some kind
soul can look it over.


-- 

       -- David M. Pochron   |
                             | Canada: One of the world's greatest mysteries..
pochron@garfield.cs.wisc.edu |