CompuServe Messages

JD >>I found that the month-day was correct, the year is off by 20 (like it has always), and the time was when I shut down last night.<< Try forcing another RESET with the SetClock command, or perhaps removing the battery completey so the clock is forced into its default settings. If the clock isn't bad, or scrambled, and the battery is ok, then something is crashing the clock… Perhaps the the OS is finding files that were saved with the future date, and is getting confused. I believe the system checks the date of certain files when it can't find the clock. This allows the system to default to a more current date than the Amiga's inception date. Check the libaries for a "touch" utility, that can update the "last saved/changed" date of all the files. If you can get all the files to a current date, Ron. – ap'ing with AP. (Eagles may fly, but weasels aren't sucked into jet engines.)