Amiga Diagnostic Pgms?
11 messages in this thread
My Amiga 3000 is giving me problems. Sometimes it just freezes up. Other
times I get a nice orange box on a black screen with the message error
8000 0004, task 0748 2f40. Of course, this message is nowhere to be found
in any of my AmigaDOS manuals. Does anyone know what this message means?
I have the 2.0 ROMS installed, Kickstart V 37.175, WB V38.35, 2 MB Chip
ram 12 MB fast ram.
I added memory a while back and it seems that these occasional problems
started happening then – but it is hard to be sure. I'd like to test the
memory to be sure that it is OK.
I downloaded the latest version of the MEMTEST program from the database
here but it freezes up too. This is an older program, does anyone know if
this program will work properly on a 3000 or with WB V2.x?
There are at least a couple of commercial programs that claim to diagnose
problems with your Amiga, does anyone here have any of these programs? Are
they worthwhile or not?
How does the Amiga operating system allocate FAST memory (i.e. does it
start allocating memory from top down, botton up, etc., if I knew this I
might be able to try loading various in various orders and try to track
down the problem if it is indeed memory related)?
Thanks for any insight you can provide,
-J
There a memtest program over in AmigaVendor in the microbotics section.
If you have a bad ram chip it ought to find it.
Bob Comer — Cruising the nets on AutoPilot from Cheyenne, Wyoming
Thanks for the information, I never bothered to look in the Vendor's
database!
I got the program and it seems like a pretty nice program. It didn't find
any memory errors though so it looks like I might have other problems.
(Sigh)
Thanks again,
-J
Your welcome! Have you tried turing off Burst with the CPU command?
(Burst on, and errors you've been having, usually indicate a RAM type
mismatch.)
Bob Comer — Cruising the nets on AutoPilot from Cheyenne, Wyoming
I have a 3000. All of the RAM is identical.
I was not aware of the CPU command, I turned off all burst and cache modes
and there were still no memory errors found.
I may have to get a commercial program to do further diagnostics.
-J
Do you still get the guru's with burst turned off? That's what I
meant…
Bob Comer — Cruising the nets on AutoPilot from Cheyenne, Wyoming
Oh, I didn't understand what you meant!
I'll experement with that and see what happens. It may be hard to do
because I can't seem to find any pattern that leads to a crash other that
they seen to happen at the most annoying times possible.
-J
Turning the Burst off might help tell what's wrong. Another possibilty is
that you have some utility running in the background that'll cause a
lockup for no reason (that problem bit me BAD, I almost sent my A1200 back
because of a bad screen blanker!) Maybe one of the things you start in
user-startup, or WB startup can't handle the extra RAM.
Bob Comer — Cruising the nets on AutoPilot from Cheyenne, Wyoming
I guess I'll try turning off burst for both instructions and data as I
can't see how the distinction would matter, RAM access is RAM access.
-J
To true… (I forgot about the Data Burst!)
Cache's shouldn't be a problem unless your running some kind of wierd self
modifying code.
Bob Comer — Cruising the nets on AutoPilot from Cheyenne, Wyoming
Jay,
you might want to try MEMDIA.ARC. It does run on a 2.x system with an
'030 (I just verified it), but you may want to break the startup-sequence
and give it a higher stack, before running it.
I can't answer any of your other questions as I just use what the I
have on hand. No special programs beyond Memdia.arc.
Brian