From: Vincent Poy (vince_at_mail.MCESTATE.COM)
Date: Fri Jun 04 1999 - 08:33:56 EDT
On Fri, 4 Jun 1999, STeve Andre' wrote:
> In my experience, just leaving a unit on for a while and then simply using
> it has flushed out most problems. Will this find all problems? No--there
> are some conditions where a failure doesn't occur until a specifc bit
> pattern is held, but in my estimation that doesn't happen very often any
> more.
>
> Usually, flakey memory announces itself as soon as you turn the computer on.
> I don't think I've seen bad memory more than two times in the last four
> years, and both displayed their problems immediately.
Actually, this is only true with Parity memory. Non-parity memory
doesn't announce itself until it's too late.
> Yes, there are memory testers, but they are fairly specifc to the type of
> RAM being tested, and frankly I don't think they're very worthwhile any
> more. If anyone has experience to the contrary I'd be interested in
> learning more.
>
> So, if you want to test new memory, I'd say just use it a bunch a look
> for problems. Leave the unit on when you aren't using it. If you don't
> get errors in the first four days you probably won't see problems for a
> long time.
Yep, that's a good point.
Cheers,
Vince - vince_at_MCESTATE.COM - vince_at_GAIANET.NET ________ __ ____
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ]
GaiaNet Corporation - M & C Estate / / / / | / | __] ]
Beverly Hills, California USA 90210 / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:55:04 EST