My clock runs really Fast

Hello, I just wanted to know if there is a solution for a fast running clock on a riocar. Since I got the unit installed about 2 1/2 years ago the clock always runs super fast. That's the only issue I have ever had with the unit so it's not a big deal in my opinion, but it would be nice to figure it out.

How fast? Mine gains several seconds a day, but I tolerate it by running ntpdate every time it boots on the network, so it is only noticeably wrong when I have two or three weeks away from the office.

Since I got the unit installed about 2 1/2 years ago the clock always runs super fast.

This is unusual. I've never heard of the clock running fast, I've only heard about it getting reset each time the player is unplugged as described here. Do you think that might be what's happening?

Just to add, mine gains time every day as well, nothing I complain about. In fact the only reason I noticed is Strong Bad tells me every time.

Anything more than a few seconds? The original person posting described a large amount but didn't quantify...

Just a few seconds at a time. But over a couple months the clock was 10 minutes fast, so it added up in a hurry.

Over the past few days since I have been running the clock, everything seems fine. Not sure what will happen if I remove the player from my car, I will try that tonight. Maybe it was fixed when I upgraded to version 2.00. That might have been the fix, since I have not used the clock function for a year or so.

Not having this problem, but mine does not keep time no matter what and I have been meaning to post about it. I've had this problem with the player since I bought it 2 years ago. I checked that FAQ entry and none of those apply so I probably do need to contact support... although it's just a clock and not really much to get twisted over.

If I set the time, the next day when I start the car, it will say either Jul-1-2001 or something like Jan-11-2036 (not sure about the Jan 11 part but the year is always 2036).

I was having this trouble with 2.00 final (and betas) and then when I switched to 3.00 a7, the time actually seemed to stay corrected for a couple of days, and then about a week later i looked at it and again it showed the above symptoms. So I don't know what happened there. I'm not using a tuner so RDS is not a factor and I've set the correct time zone and all that.