On Friday 23 January 2004 09:44 pm, David E. Fox wrote:
> On Fri, 23 Jan 2004 10:26:31 +0000
>
> John Richard Smith <[EMAIL PROTECTED]> wrote:
> > I just ran mprime on my machine and got a core dump
> > immediately in the
> >
> > same directory as mprime.
>
> Ouch. That might indicate shoddy hardware. Tom can chime in,
> he's more knowledgeable about this than I am.
>
> > John
memtest86 should be the first test, but its sort'a lite,
will let a lot of hardware problem pass. './mprime -m', and
choose the torture test (17) is a better hardware and ram tester.
BUT, keep in mind there is no such thing as a software ram test.
All tests involve the whole system from the PSU on up. cpuburn's
module for the appropriate processor is the acid test (burnBX
burnK6 burnK7 burnMMX burnP5 burnP6). Caution tho, you
should already have confidence that your hardware is capable, and
you need to monitor cpu and chipset temps while 'burn*' is
running. It can damage oc'd, weak or marginal systems.
That said, if the system can't run 'mprime -m', 17 overnite,
without stopping on hardware error, IMO the system hardware is
not stable enough for Linux use. If it can run cpuburn for an
hour its bulletproof. Many Windoze boxes will fail cpuburn,
specially ready mades (Dell, et al, and laptops). Shouldn't even
try it.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
