PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jun Qian <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Sun, 27 Jun 1999 23:37:09 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Two ways to check the CPU:
1) as your problem, if the computer failed at boot or other problem at
begining, then the CPU is easy to point out as bad (compare to more
complex problem I met).
2) if the CPU seems ok, you can run heavy CPU related program for at
least 1/2 hour, to give the CPU max workload as possible, if the CPU
passed this test, it is surely ok. This test can also be used to test
Socket 370 -> Slot 1 card.

J Qian

Ken & Barbie wrote:

> My question is this a reliable way to check for a failed CPU?

               PCBUILD mailing list is brought to you by:
                            The NOSPIN Group
                  http://nospin.com - http://nospin.org

ATOM RSS1 RSS2