I will try with just loading SMSQE and nothing else which should eliminate the first two but for what its worth booting into Linux has no problems with the clock.
----------------------------- David Gilham ----------------------------- The universe is a queer place --- [EMAIL PROTECTED] wrote: From: Marcel Kilgus <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [ql-users] clock adrift in SMSQE Date: Tue, 13 Mar 2007 22:11:02 +0100 David Gilham wrote: > If I boot into SMSQE and let the system run for a reasonable > time printing date$ seems to indicate that the clock is losing seconds at > an large rate ,apparently 1 minute per hour. This was so whether I > typed Prot_date 1 or prot_date 0 immediatly after a normal boot. > If I do a soft reset the time display and hence the clock reverts > to a more or less accurate value. I am baffled by this. At least this is easily explained: the RTC is read once on boot (which should be fairly accurate), but afterwards the time is updated by the 50Hz frame interrupt. At first thought I see 3 possible causes: - something in your system is messing with the clock system variable value (unlikely, but can easily be checked by using a clean boot) - something in your system is disabling the interrupts for an extended period of time (possible, but should again be eliminated by a clean boot) - the frame interrupt is not working correctly because there is a hardware problem. Marcel _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
