Quote Originally Posted by oc_junkY View Post
Congrats for the work man!
Especially the "remaining time" function is cool :-)
Thanks!

Quote Originally Posted by monza1412 View Post
Im having problems if I run it at real time priority, even at stock speeds, windows just freezes a couple of seconds after the start.
Anyone else experiencing this (running on win7 64b RC/ 4gb Ram)
Yes, this is kind of normal behaviour. Consider reading the hint over the Priority setting.
I personally wouldn't set priority to anything over above normal, as it only makes the whole OS almost freeze (or completely freeze, as in your case).
In 0.6.1 (which is currently getting its last polish) LinX will have same priority as Linpack, so at least it won't freeze and you'll be able to stop it. For now stick with lower priorities.

Quote Originally Posted by 123456iambelial View Post
How to use this?
Do I have to look at the time? Lower is better?
or
The highest GFlops peaks? Higher is better?
Well, you just test it, the more GFlops the faster is your system, on higher problem sizes/memory values you're likely to get higher GFlops and higher load and higher temps.
Linpack was designed as a benchmark, thus the time per test and GFlops values. If you're just stress testing/stability testing, you may simply ignore them.