[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple IIgs Crashed



(my lay opinions and methods for problem solving..)

I think the first symptom indicates memory corruption from maybe a bad
PS, bad memory chips, or something else on the motherboard (cpu,
capacitors, ??). I don't know about the component quality used on Apple
IIgs motherboards, but capacitors can dry out and result in corruption
of address or data information on the bus lines. This happened with
some cheap PC motherboards and is a common problem with old video
arcade boards.

The main method of trouble shooting I use is "cut the problem in half".
Simplify things as much as possible - take out everything not essential
to the manifestation of your problem. Maybe even swapping out the
entire motherboard, etc. Just so you know the problem is *on* the
motherboard (or not). So you assume (not always correct, especially if
things interact) that if you remove something, and the problem goes
away, then the problem is likely caused by the thing you removed.

o Establish a method to reproduce the problem (it might be as crude as
1-3 hours of on time -> corruption of basic program). Of couse this can
be difficult if the problem is random. Once you find a method that
works, try and stick with it - i.e. don't change it.

o remove all the peripherals you can
o swap out, one at a time:
- power supply (as you mentioned)
- memory (?) (or test it)
- motherboard ? (maybe a last resort)

For each swap you run your "method" and see if the problem manifest
itself. This is your compass to guide you in solving the problem.

(I assume you have extra parts around since you hand out here on this
ng)
Stop using disk i/o for now.