Path: utzoo!attcan!uunet!super!udel!mmdf From: detert@lognet2.arpa (CMS David K. Detert) Newsgroups: comp.sys.amiga Subject: A500 Problem Message-ID: <6859@louie.udel.EDU> Date: 19 Jan 89 00:46:47 GMT Sender: mmdf@udel.EDU Lines: 26 Here's a problem a friend is having with her A500 I hope someone can help with. Everyone once in a while (twice in last 2 months), the date goes out in never-never land. Booting will result in a date like 18-May-78 or some such nonsense. Analysis shows a disk file on the boot disk with a similar date. I assume the system is reading that since it takes what it thinks is the date off the most current file if there is no setclock or date command in the satrtup-sequence. Anyway, we can't find where this date is coming from. To make matters worse, the files affected the last time this happened were the .info, the Expansion.info and the System directory entry. These were verified by the LIST command. There is nothing in the boot sequence to write to these files and she has not done anything to write to those files. I suspected the date was getting munged and then she was doing a SNAPSHOT or something, but she maintains that is not the case. There is nothing in the Expansion drawer and the startup-sequence is plain vanilla as shipped from Commodore. Running SETCLOCK seemed to indicate the battery clock was functioning. I put SETCLOCK OPT LOAD in the startup-sequence, but we would like to find out how the date was getting munged in the first place. Can anyone help track this down. BTW, this has happened with her normal boot disk and her Word Perfect (4.2) boot disk. I'm at a lost to explain it. Thanks in advance. Dave CMSgt David K Detert ARPANet: detertlognet2.arpa PS. One other thing I just remembered, one time the dates were something like 02-- 88. Strange???????