Real Time Clock/NetTime

3 posts, 2 voices

Jan 15, 2011 4:51pm Chris Hall (132) 3558 posts	Setting the time to 1970 on the BBXM (using !Alarm) and then running NetTime_Kick causes the year to be set correctly to 2011 and the time to be correct. However leave the time at 1970 after a power on and NetTime_Kick does not do anything. The work around is to include a BASIC programme in !Boot.Choices.Boot.Tasks after the NetTime module is loaded and NetTime_Kick’ed containing the following: SYS "OS_Word",15,CHR$(15)+"Mon,17 Feb 1992" *NetTime_Kick

Jan 15, 2011 8:05pm Andrew Conroy (370) 740 posts	I’ve just tried it on my BBxM with NetTime v0.36. I set the year to 1970 and the rest of the date/time to be wrong, powered down and then rebooted. I did a nettime_kick and everything came back to the correct date/time/year. This was with EtherUSB via the on-board NIC. My BBxM does have a RTC battery fitted.

Jan 16, 2011 8:49pm Chris Hall (132) 3558 posts	Perhaps the bug is only evident on BBXM with no RTC battery fitted. Also is there some utility to read the on-board RTC hardware and set the CMOS soft clock copy? Because that would have the same effect as the work around on a non-RTC battery/utility fitted machine.