The Mersenne project has a TortureTest mode that has helped me find how far I can overclock CPU or RAM without running into errors. It runs massive calculations and compares the results with pre-known values. If this is run while a disk I/O and graphics test run, the collision problems between these memory users can be (hopefully) caught without regard to whether you overclock or not.

See: http://www.mersenne.org/freesoft.htm

Brian Brunner brian.t.brunner@gai-tronics.com (610)796-5838

...

...

jlb17@duke.edu 11/22/05 02:34PM >>>

On Tue, 22 Nov 2005 at 11:30am, Robert wrote

} It might be useful if you specify what aspects of the box you want to } test. } } CPU? RAM? Disk? } } You mentioned disk, but is that all that you want to test? } } Regards, } Greg

i wish to test it all, everything, just not ummm extremely violently in terms of hard drive(s).

so, if the hard drive testing part is ultimately configurable that would be great... i just dont feel like pounding the drives for hours and hours

ummmmmmmmmm what are people using in this area?

i am familiar with memtest and some of the other small stuff yet i am looking for practical list wisdom on this whole scenartio.

thanks!

I've actually had pretty good luck with this little script:

http://people.redhat.com/dledford/memtest.html

It's not *too* hard on the disks, although that part isn't configurable.