From: STeve Andre' (andres_at_pilot.msu.edu)
Date: Fri Jun 04 1999 - 08:28:26 EDT
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.
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.
--STeve Andre'
andres_at_pilot.msu.edu
At 03:57 PM 6/3/99 -0400, Peter Wennersten wrote:
>
>could someone briefly tell me what should be done during such a burn-in
>period. Using the computer all the time, running test programs, anything
else?
>
>Also, apart from the computer breaking down and emitting smoke, how do I
>know I've got bad memory? Are the programs that test this? Freeware?
>
>Thanks,
>
>Peter
>
>> The purpose of adding memory is to
>>speed up a machine and reduce the load on the HDD from swapping.....
>>.....it's important to do the 72 hour burn-in period to make sure it works
>>correctly since if it fails, it will usually fail by then.
>
>
>
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:55:04 EST