[OT]Dumb hardware question

[bconway at alum.wpi.edu (Brian J. Conway)]

My experience with Memtest86 has been exactly the opposite.  If I don't
get errors from a system in the first minute or two (which usually end up
spewing lines up the screen faster than I can read), I don't get any, even
if I leave it sitting for a day or more.  Booting a Linux CD-based distro,
as was mentioned earlier, sounds like a good idea.  If it crashes there
will be a lot more useful information to sift through to find what is
actually the problem.  My $0.02.

-b

On 10 May 2003 14:47:25 -0400
Derek Atkins <warlord at MIT.EDU> wrote:

> Jerry Feldman <gaf at blu.org> writes:
> 
> > On 10 May 2003 13:52:51 -0400
> > Gregory Boyce <gboyce2 at badbelly.com> wrote:
> > 
> > > You might want to run memtest86 first.  It'll check for bad memory,
> > > which could easily cause freezes, and you dont' have to talk
> > > anything apart first.
> > That was done quite a while ago. Ran it for about an hour.
> 
> An hour may not be long enough... I had to run it for about 24 hours
> before it found the error.
> 
> -derek
> 
> -- 
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord at MIT.EDU                        PGP key available
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss