9 Nov
2006
9 Nov
'06
2:13 p.m.
On 11/10/06, Don North <ak6dn at mindspring.com> wrote:
I know back at DEC when we had a unibus CPU problem,
the first thing we
almost always did was pull the boards, run the trusty eraser up and down
the fingers, and then seat/reseat the boards a couple of times. This
invariably worked.
When I did support for Unibus and Qbus COMBOARDs, our first
recommendation to our customers with hardware problems was to reseat
the COMBOARD. That took care of 90%+ of calls (and we didn't have to
ship replacement hardware).
-ethan