Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.milw.wisc.edu!mailrus!ncar!boulder!tramp!rademach From: rademach@tramp.Colorado.EDU (Simon Rademacher) Newsgroups: comp.sys.amiga Subject: Re: A500 clock gone senile Message-ID: <10644@boulder.Colorado.EDU> Date: 10 Aug 89 18:28:06 GMT References: <10619@boulder.Colorado.EDU> Sender: news@boulder.Colorado.EDU Reply-To: rademach@tramp.Colorado.EDU (Simon Rademacher) Organization: University of Colorado, Boulder Lines: 7 Just a cliarification on my original post (deleted for brevity): It is the battery backed up clock on the A501 that is giving the wrong time via setclock opt load. Apparently, there was some confusion. ======================================= = Simon Rademacher = = rademach%tramp@boulder.colorado.edu =