Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site usc-cse.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!usc-cse!randvax!%SRI-KL.ARPA,%SRI-CSL:engvax!KVC@CIT-VAX
From: KVC%CIT-VAX@%SRI-KL.ARPA,%SRI-CSL:engvax.UUCP
Newsgroups: fa.info-vax
Subject: Machine checks...
Message-ID: <611@usc-cse.UUCP>
Date: Tue, 23-Oct-84 04:33:15 EST
Article-I.D.: usc-cse.611
Posted: Tue Oct 23 04:33:15 1984
Date-Received: Thu, 1-Nov-84 02:48:14 EST
Sender: uucp@usc-cse.UUCP
Organization: Univ. of Southern Cal., Los Angeles
Lines: 20

From: engvax!KVC@cit-vax

We've occasionally had some real sticky hardware problems...  The
kind where everything passes the diagnostics or different things
fail the diags at different times.  One of the things I've found out
from sitting with the FE all night while he swapped boards is that
quite often the problem ends up being a flakey power supply.  This
is true for CPU power supplies and disk drive power supplies.

What I wanna know is, how come these guys don't check the %*&$%&*$
power supplies first?!?!?!?!?!?!?!?   I really don't like sitting
in a cold machine room to all hours of the morning watching someone
yank my VAX apart only to discover, several hours later, that a flakey
power supply was the cause of it all!

Now I tell them to check the damn things first, then they can start
pulling logic arrays...

	/Kevin Carosso             engvax!kvc @ CIT-VAX.ARPA
	 Hughes Aircraft Co.