Quote Originally Posted by A-Grey View Post
@Dua|ist

Could you add a feature to LinX for the competition that makes it possible to run LinX for the amount of time that will be needed to run LinX stable for a valid result.
Is that really needed? Not that it is so hard to implement, but one could possibly just look at the status panel and then stop the test if the required time has passed. I think some sort of minimum time requirement will do, without any particular upper limit.

Quote Originally Posted by slim142 View Post
Hey Dualist

Are you planning on upgrading LinX to 2.0 anytime soon? I just found out my RAM might be a problem Im having and when I read the changelog of Intel Burn Test 2.0, I thought it would be a great idea to stress my system with it, but I would really like the LinX interface
IntelBurnTest and LinX are not connected in any manner, they're just based on the same Linpack engine by Intel. And I haven't found anything Linpack-related in that changelog to be honest. And there were no newer Linpack files released by Intel, so LinX is still using the latest ones.
As for the memory, I'm sure that using higher problem sizes in LinX is still a good way to test memory too, and there always are such specialized tools like MemTest (both DOS and Windows-versions) which will most likely do the job even better. Or a good old Prime Blend.

But thanks for the info on IBT. It's nice to see the competition going. The «The original. All others are copycats.» motto sounds pretty weird now though.

Now that there's such feature in IBT, it would be interesting to compare the GFlops numbers...