Quote Originally Posted by jcool View Post
I always get low Gflops with HT enabled, I thought that was a Linpack general problem and "normal"?
Uhm, actually not. At least it isn't for Core i7 with HT on and Linpack being run in all 8 threads. Running Linpack on a Core i7 in only 4 threads, however, would indeed result in lower GFlops (this is normal).

LinX is supposed to detect the change in # of logical processors (when turning HT on/off) and set the number of Linpack threads to the actual value.

As for the i9 of yours, it looks really weird. Maybe it'll be possible to do some Linpack tweaking to see if anything changes. Once I implement this, you'll be the first to know.

Quote Originally Posted by Bitgod
In the IntelBurnTest thread, it mentions doing 16 threads on i7s, is that recommended here also?
Sure, if you have HT on, 16 threads is way to go. As already mentioned, LinX should default to 16 threads on an i7 PC on the first run.

Quote Originally Posted by Bitgod
So finished one batch, quit the app, reopened, still working. I noticed when it's not working, it doesn't save changes you make to it like the settings, but it does remember the changes when it's working right, so it seems like it can't write to it's config file. I wonder if turning off UAC fixed something?
What you said about the settings not being saved is interesting indeed. Never heard of such an issue and never experienced it myself. I can't imagine what could be preventing it from saving a dozen of string into an ini-file… Thanks for the observation, I've gotta check it.

UAC is turned off by me, but never heard of LinX having issues with it. Any chance you can turn it on and see if the bug you mentioned will re-appear?