🚀 go-pugleaf

In article <1993Jul27.132234.8704@rzu-news.unizh.ch> ps@oci.unizh.ch (Sezgey Pachkovsky) writes:
>Mike Palmer (mpalmer@encore.com) wrote:
>
>: The power on test does not thouroughly test the memory at all.  You need
>: to run something like checkit memory test for 24 hours to be reasonably
>: certain that memory is OK.
>
>Hope, hope. I had seen machines which will run CheckIt's tests Ok for _weeks_,
>but will fail on a simple test of filling each doubleword with it's linear
>address and reading it back just once... The problem is what CheckIt tests
>memory in 64K-chunks, and if writing to some address will _sometimes_ change 
>memory at some +/- 64K location (it could happen if you address decoding logic 
>is at fault), most probably CheckIt will miss it...
>
>Cheese,
>
>/Serge.P
>
>--
>
>Russian guy from the Zurich university...
>


I mentioned in an earlier note that Windows 3.1 is an excellent tester
of memory.  That is, if you have Windows installed on your system.  This
method is much more effective than CHECKIT or QAFE.

If you delete the permanent swapfile (386 Enhanced Mode),
and then run as many applications as memory will permit, you will eventually
cause the bad memory module to be exposed.

Regards,

Mike Ullman
Rockwell International