Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!cs.dal.ca!aucs!840445m From: 840445m@aucs.UUCP (Mic Mac) Newsgroups: comp.sys.amiga Subject: Re: Big Problems with A1000 Keywords: clock broke Message-ID: <1699@aucs.UUCP> Date: 25 Mar 89 19:57:07 GMT References: <1683@aucs.UUCP> <2319@ritcsh.UUCP> Reply-To: 840445m@aucs.UUCP (Mic Mac) Organization: School of Computer Science, Acadia Univ., Nova Scotia Lines: 35 In article <2319@ritcsh.UUCP> franks@ritcsh.UUCP (Francis Shea) writes: >In article <1683@aucs.UUCP> 840445m@aucs.UUCP (Mic Mac) writes: >> What I mean is this, when I run any sort of clock >>program, time does not pass. > >Thats funny, my clock works fine, i think, i've never tried it...... >i get by just fine with a watch. >who cares about save times anyway????? > >frank shea > No. No. No. Listen and you shall here. Maybe I was ambiguous when I first stated my problem so I'll try again: On a 'normal' Amiga (e.g. the way mine was a few months ago), when you run the clock program, you can watch the seconds tick away, one second will elapse on the computer clock for each second of real time. On a f**ked up Amiga (e.g. the way mine is now), you run the clock program and you watch one second tick by on the computer ... oh ... about every two or three hours or so of real time. Note that I do not mean a battery backed clock or anything like that. I just mean the clock inside that ticks a second every second. Please, this is not a flame to anyone who misunderstood me ... maybe I was unclear in what I meant. Now, if anyone can offer any assistance, I would be very grateful. Oh, BTW, I did enjoy reading the person's reply to this message concerning stopping time and swiping all the -020's and -030's from the Macs. It was quite humorous. -- % Alan W. McKay % % % Acadia University % " The world needs more Socrates' % % Wolfville N.S. % walking the streets today " % % CANADA % - S. Corbett %