From owner-freebsd-hardware  Sat Jul  5 16:39:53 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA25257
          for hardware-outgoing; Sat, 5 Jul 1997 16:39:53 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25249
          for <freebsd-hardware@FreeBSD.ORG>; Sat, 5 Jul 1997 16:39:47 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id QAA13551; Sat, 5 Jul 1997 16:39:15 -0700 (PDT)
To: dburr@POBoxes.com
cc: freebsd-hardware@FreeBSD.ORG
Subject: Re: what is wrong with my machine??! 
In-reply-to: Your message of "Sat, 05 Jul 1997 14:41:57 GMT."
             <33c05876.34863358@mail.inreach.com> 
Date: Sat, 05 Jul 1997 16:39:14 -0700
Message-ID: <13547.868145954@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

[questions eliminated - only one mailing list at a time, please]

> Hi there.  Remember me?  I posted a few days ago with a strange
> problem i've been having with gcc.  Still don't remember?  Let me

It's not gcc.

> * Overclocking.  My friend (whom I bought this machine from) said he
>   ran the cpu (a 486DX2/66) as an 80.  I think the board is still set
>   up that way too.  Could this be causing this spurious behavior?  The

You bet your life it could be causing this.  Please switch it back and
test again; overclocking is a very frequent cause of failures.

> * Bad memory.  The memory is brand new and of a reputable brand, yet
>   it still could concievably be defective.  How can I test if this is
>   true?

Hardware memory tester, that's about it.  The software solutions
don't work for spit.

					Jordan