Yeah, it's come up a time or two. The deal is that there isn't really an internal clock, it kinda does it by dead reconning or something (I don't think anyone's figured out exactly what's going on). The practical upshot is that if you don't connect to the Connect software for long enough, the Reader loses track of where it is in time, and defaults back to August of '05. Kind of annoying, but not really a problem for what I need.