Yup. I would also pull the settings ram (5101 at S4) just in case. I
seem to recall some peanut-brittle junkie out there claiming the a bad
5101 was causing some havoc, and it is harder to test on the fluke.
Once everything passes Fluke tests, and it still dogs, you have to dig
into the cpu signals and power conditioning, me thinks.
Mike
________________________________
From: owner-vectorlist@vectorlist.org
[mailto:owner-vectorlist@vectorlist.org] On Behalf Of Kevin Moore
Sent: Monday, April 12, 2010 4:08 PM
To: vectorlist@vectorlist.org
Subject: Re: VECTOR: Omega Race
Good point on the long test.
The areas I'm testing are
4000-4bff
and
8000-8fff
Those the two you talking about?
They are all socketed so I pulled and checked them with my BK 575 first.
That's when I found the open traces eaten by battery acid. :( Replaced
sockets, and re-bridged bad traces. There were only a couple of bad
spots.
On Mon, Apr 12, 2010 at 3:00 PM, <mike.ranger@arcelormittal.com> wrote:
Make sure you do the ram tests on both banks, and do the long
test! I had one pass the short test on the vector ram, but failed the
long test!
Mike
________________________________
From: owner-vectorlist@vectorlist.org
[mailto:owner-vectorlist@vectorlist.org] On Behalf Of Kevin Moore
Sent: Monday, April 12, 2010 3:56 PM
To: vectorlist@vectorlist.org
Subject: VECTOR: Omega Race
Ok so I'm working on an Omega Race. My first one..
Cleaned up the Acid damage, and my fluke now reports nothing but
good things for the Ram/Rom/and Bus check..
However my CPU is still watch dogging. Is there any repair info
out there, or where should I go from here?
BTW I hate Midway Schematics..
---------------------------------------------------------------------------
** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
** Please direct other questions, comments, or problems to chris@westnet.com
Received on Mon Apr 12 16:14:17 2010
This archive was generated by hypermail 2.1.8 : Mon Apr 12 2010 - 16:50:01 EDT