QUOTE(desertrat @ Dec 8 2005, 12:53 PM)
Sounds like you're hitting the "time jump" problem. If that's the case you need to set the system time properly. Search this forum for "hwclock", or "setting clock" or something along those lines should put you on the right track.
Hmm. Coincidently I did also find some of those instructions and used hwclock to set both the clocks today. But I must have not found the definitive fix, because I just tested the 3100's On/Off switch and it puts me in exactly the same position. And sure enough after I pull the battery and restart it reverts to three days ago (which it was doing before the fix, too.)
Kind of disappointing that pdaX hasn't even solved the clock problem in the year since I've loaded a new version. I'd just gotten used to the 860 not keeping meaningful time; but it wasn't causing me to have to pull the freaking battery just to get back to work. The 3100 boots a lot faster, which is good. Still ....
So there's a version of modifying the clock routines that works? Since there's at least one documented here that doesn't, any pointers will be welcome. Lacking that, what is the function that's consulting the time and deciding to shut down the system? How do I decapitate that? I'd already told X not to suspend or blank the screen while the unit's connected to the wall wart, but that doesn't prevent this.