On Feb 1, 9:52=A0am, "Michael J. Mahon"  wrote:

> The most fundamental troubleshooting technique is called "moving the
> problem", and involves changing parts in a combinatorial way so that
> the bad "chunk" can be identified. =A0(If there is more than one bad
> chunk, this strategy becomes much more difficult.)

A while ago, I used just this technique to isolate a bad RAM chip on a
Transwarp card. I progressively cycled the chips to 'position 1' , and
after only two swaps, a fault that only showed up running Apple Pascal
with a 1mb ramdisk resulted in a machine that wouldn't even boot.

I'm glad I tried the Transwarp memory before moving to the RamWorks
itself ;-)

Matt
--- SBBSecho 2.12-Win32