A500 gurus when I try to set the time.

[Ral-Clan]

My A500 gurus when I try to start the TIME preferences tool in WB3.1.

I believe it also did this when I booted from WB1.3 as well.

The guru number is something like 8000000004.

I do believe the battery in my trapdoor 512K expansion / Real-time-clock is dead, so this may be the culprit - but I thought it would at least allow me to set the time for that boot session even when dead.

This Supra has a coin battery - so no leakage.

Anyone experience this before or know the cause (even if you can confirm it's the dead battery).  Thanks.

[Ral-Clan]

Hello again everyone.

So I finally got the new battery for the SupraRAM 512K trapdoor expansion and installed it on the board with the coin battery socket.  Tested the volatages coming out of it and everything is good.

But the Amiga still GURUs (80000004 or something) when I try to start the TIME preferences.

So....

- Amiga Gurus when I try to set the TIME preferences with NO trapdoor expansion / RTC
- Amiga Gurus when I use the trapdoor expansion / RTC with DEAD battery
- Amiga Gurus when I replace the trapdoor expansion / RTC battery with fresh one

Also, I should note that my A500 thinks it's October 1996 when it boots up under all the above conditions. Why would it default to THAT date?  That's long after OS3.1 was released (which is what I have installed) and two years after Commodore was defunct.

Using the SETCLOCK LOAD command causes the Amiga to think it's 1978.

If I start the CLOCK utility when first booting up, the clock runs nicely, although the time is wrong and it's October 1996.

If I have the clock displaying and I type in CLI: CLOCK RESET then the clock goes a little crazy - it refreshes itself every second (like it clears the clock window and redraws the clock).

This is weird and frustrating.  I have an old A501 in the garage I will pull out and try (although it has its battery removed as a precaution) - but if the Amiga gurus even WITHOUT a clock in the trapdoor, I wonder.....

[Ral-Clan]

Here's a strange thing:

I have a kickstart switcher....so I booted the A500 into Kickstart 1.3, and booted a 1.3 Workbench Disk.  I was able to set the time from there (on my RTC).

Then, switched back to KS3.1 and booted into Workbench 3.1.

The clock has the correct date and time now.  But TIME preferences still crashes the machine in WB3.1.

STRANGE!