[comp.sys.amiga] A500 Problem

detert@lognet2.arpa (CMS David K. Detert) (01/19/89)

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:  detert<at>lognet2.arpa

PS.  One other thing I just remembered, one time the dates were something
like 02--  88.  Strange???????

martens@frigate.cis.ohio-state.edu (Jeff Martens) (01/19/89)

In article <6859@louie.udel.EDU> detert@lognet2.arpa (CMS David K. Detert) writes:

		[ almost the whole article deleted ]

>PS.  One other thing I just remembered, one time the dates were something
>like 02--  88.  Strange???????

I've been getting this one.  When I use list to get a directory
listing, sometimes files will come up with the month totally missing,
like:  02--89 for example.  It looks like a reasonable day and the
right year, but no month.  If I touch the file, the date reverts to
the present properly.

I'm still running 1.2 (grrr... thanks to Commodore or my local dealer
-- don't know quite where to put the blame) on a 512k A1000.  I always
set my date upon boot before running anything else.

-- Jeff (martens@cis.ohio-state.edu)

pfaff@mercury.asd.contel.com (Ray Pfaff - Oakwood 457 934-8162) (09/22/89)

Recently (like today) my A500 went belly up.  The symptoms are that the
machine displays the insert workbench prompt for about 3 seconds, then 
the power light flashes once and goes out and the screen displays either
a white screen or a series of different colored screens in about a one
second-per-screen sequence.  Is this the dreaded "Fat Agnes" problem?  I
tried thumping the Amy as well as removing all peripherals ( execpt the 
monitor) and removing the 512k memory, but the problem remained.

detert@lognet2.af.mil (CMS David K. Detert) (03/02/90)

Included is a short description of a problem a friend of mine seems to

be having with his A500.  If anyone knows what might be causing the

problem or what he might check, I would appreciate email back.  I will

forward any responses.

 

>

>Need your help again.  My computer is acting up.  I try to klick on a

>icon and I can only click on it one or at most twice.  After that I

>have to take the disk in and out to get another click.  If I press the

>right mouse button it will lock the system up, but then again, if it

>will not click, it will not work.  Any ideas?

>

>I do not think it is related, but I also now have the Gravis

>Mousestick.  Excellent!  I love it.  Best mouse and best joystick I

>have every used.

>

 

Again, any help anyone can give will be most appreciated.  He is

stationed over in Korea and it's kind of difficult finding a local

dealer.:^)

 

Cheers, Dave

 

PS.  His system is an A500 as far as I remember.

 

CMSgt David K Detert, USAF     MILNet: detert@lognet2.af.mil