View Single Post
Old 29 December 2012, 18:18   #8
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 3,347
One reason would be, it helps people wanting to make their code compatible with that type of real Amiga. Things like AROS, Linux, NetBSD etc. could be tested on WinUAE if the developer doesn't have a real A2000.

Commodore softened the message shown by SetClock with Workbench 1.3. And the Workbench 1.2 startup-sequence does SetClock >NIL: so the message doesn't appear. It's unlikely CBM actually wanted to be besieged by A2000 owners looking for their motherboards to be updated.

Interestingly, battclock.resource in Kickstart 2.0 and later (even the earliest v36 one that I could find) doesn't seem to support the clock at $D80000. Maybe it was hard to reliably detect a $D80000 clock without affecting whatever hardware lived at that address in later Amiga models???

A2000 owners who use Kickstart 2.0 or later would need to use the SetClock command from Workbench 1.2/1.3 in order to save and load the time. (The Y2K-compatible SetClock 34.3 which used to be available from ftp.amiga.com does still support $D80000 clocks. I just posted that in this thread if anyone wants it.)
mark_k is offline  
 
Page generated in 0.08010 seconds with 11 queries