wilde@tigger.colorado.edu (Nick Wilde) (05/23/89)
The following strange behavior has reared it's ugly little head: My system : B2000 CPU with 2090 (no 'A') controller hooked to a miniscribe 40 meg. The standard (I forget the number) Commodore 2 Meg ram expansion. What happens: Said system boots off of df0:. Transfers system to hard drive. As its last dying gasp.. startup-sequence does "setclock opt load". System time is set correctly. So far everything is hunky-dory. Wait precisely 1 minute and 9 seconds.. Watch the system clock DECREMENT itself. Yes, time runs backwards. The hardware clock still seems OK. If I do another "setclock opt load", the time gets set (once again) to the correct time... Only to decrement again 1 minute and 9 seconds later (Oh yeah, it repeats that 1 minute 9 second decrement cycle, so the system clock keeps falling further and further behind). Questions: Anybody got any guesses as to probable causes ? I seems to be hardware... 'Cuase I can go back to booting of my oh-so-sacred never-touched-but-once-to-copy-from WB 1.2 and 1.3 disks, and the same behavior still occurs. Question #2: Anybody care to hazard a quess as to wether this could effect (or is it affect ?) the operation of the rest of the system. I'm somewhat loath to take Amy in to get her clock fixed.. For the $100 or so that it may cost I can check my wristwatch. But I'm concerned that programs that use that time may do flakey things if time goes backwards.. -Thanx