[Coco] Bad Driver Combination?

[Lothan]

If I remember correctly from looking at the code a while back, NitrOS-9 uses 
1900 as an offset for the year so 0-99 are 1900 through 1999 and 100-199 are 
2000-2099. Assuming this is correct, the year in the clock should be set to 
112. I'm sure Boisy or Gene will have the definitive answer if I stepped in 
another mud puddle.

-----Original Message----- 
From: K. Pruitt
Sent: Saturday, March 10, 2012 1:47 PM
To: Coco at maltedmedia.com
Subject: [Coco] Bad Driver Combination?

When I make a NitrOS9 boot disk using the no-halt driver for the Disto Super
Controller II (rb1773_scii_ff74.dr) and the smartwatch driver (clock2_smart)
together, the Coco 3 will crash instantly when the system tries to access
the clock chip.

Anyone else had this experience and is there a solution (other than not
using the smart watch driver, which is the solution I am currently using)?

Also, when I use the getclk utility to get the date/time from the chip,
date -t reports the date as 1912.  This is confusing to me because as far as
I know the watch chip doesn't hold the century but rather only holds the
year, and getclk doesn't seem to be passing a "19" to F$Time - at least not
as far as I can tell from a disassembly of getclk.  Where is this 19 coming
from?  Does NitrOS9 default to 19 in the absence of a century digit?  Does
the NitrOS9 F$Time system call use the same 6 digit scheme as the OS-9
version or does it actually have space for a century digit?  I'm using Y2K
updated modules in OS-9 so there it is not an issue, but under NitrOS9 that
19 always shows up.

Thanks for any info you might pass on.



--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco