Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!jtb
From: jtb@dhw68k.cts.com (John Gibbons)
Newsgroups: comp.sys.amiga
Subject: Serious amiga 2000 clock problems!
Message-ID: <1990Jul21.142922.959@dhw68k.cts.com>
Date: 21 Jul 90 14:29:22 GMT
Reply-To: jtb@dhw68k.cts.com (John Gibbons)
Distribution: na
Organization: Wolfskill & Dowling residence; Anaheim, CA (USA)
Lines: 65


    For quite some time now I have had a lot of trouble with my Amiga 2000's
built in clock. Well actually to be more exact, the built in clock is fine,
but once the software gets ahold of it I am in trouble.

    In order to relieve you of the hassle sending back the obvious responses
I will let you know now that it is NOT any of the software I am using on my
machine. I have made sure of this by booting off a floppy which does
nothing more than open a shell, I just Installed it with the cli install
command. Therefore it is another problem. I will attempt now to explain the
problem as best I can. (also I have used 1.3,1.2,1.3arp setclocks with the
same result)

    If I at ANY time do a "setclock opt load" the correct time and date is
loaded in perfectly without problem. However within 1 minute the current
time will be incorrect. The following is a buffered command line test I
performed while typing this post. All text in [Brackets] are my comments.

$ setclock opt load
Saturday 21-Jul-90 06:08:41 [this is the correct time]
$ date
Saturday 21-Jul-90 06:08:50
$ date
Saturday 21-Jul-90 06:08:53
$ date
Saturday 21-Jul-90 06:09:00
$ date
Saturday 21-Jul-90 06:09:30
$ date
Saturday 21-Jul-90 06:09:43
$ date
Saturday 21-Jul-90 06:09:46 [Still the correct time]
$ date
Saturday 21-Jul-90 06:08:43 [Aha! The clock has gone crazy!]

    So as you can see after about 1 minute the clock decides to go back 1
minute and will keep screwing around like that forever no matter how many
times I reload the battery backed clock. I have no intentions of dcron
setting the clock every minute or doing it manually. I just do not know why
it is happening or what it could be.

    I do, however feel it would be a good idea if I were to list all my
hardware that could perhaps be the cause of the problem.


    Amiga 2000 (B2000) V4.3 motherboard
    Commodore 2090A Hard Disk controller (Conner 40mb SCSI hd)
    2 floppy drives, (monitor, modem, printer etc..)

    If this is of any importance I do not know, I run my machine 24 hours a
day and rarely if ever shut it off. But seeing as how the problem with the
clock will begin as soon as I do a setclock I doubt if that matters.

    If anyone can give me any advice or solutions I would be forever
greatful, please either send email to one of the addresses below or simply
post it here as I am sure I am not the only person to have this problem.

    Also if this has already been discussed here, sorry I must have missed
it and you CAN'T get mad at me for seeking help. (Well I suppose you could
get mad, so if you do, /dev/null would be a nice place for any flames.)

Thanks a million
-- 
John Gibbons
Internet: jtb@dhw68k.cts.com       UUCP: ...{spsd,zardoz,felix}!dhw68k!jtb