On Sunday 28 September 2003 07:37 pm, fish wrote: > On Mon, Sep 29, 2003 at 12:54:37AM +0200, Michael Schierl wrote: > > On Sat, 27 Sep 2003 18:53:04 -0700, Martin Stone Davis wrote: > > > If I have faulty hardware, how am I supposed to tell? I'm not having > > > any problems with other applications (one of which is memory > > > intensive). > > > > http://www.memtest86.com/ > > > > Run it for several hours (if you can). > > it should be pointed out, that on systems with more than about 128meg of > ram, memtest86 is actually completly useless, because it cannot do the > required amounts of tests on a current system within even a week. There is > a big long explanation, but basically, because we don't have maps of the > way the ram is internally layed out, it has to do tests that run in 2^n > time, where n is the amount of ram yoou have. > > as n gets bigger... well, you know...
I have compleated tests 1-7 (the basic tests) in a few hours on a system with 512MB. On the memtest site, it states that those first 7 should be able to detect all but the most obscure errors. I would think that if is noticeably affecting stability, those would find it. So it's still worth a shot. Why do they not mention the problems with large amounts of ram on the site? _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
