LinX - A simple Linpack interface

[Dua|ist]

Most of you know what Linpack is I guess. In case you don't, it's a benchmark designed to measure performance on Intel CPUs in GFlops. But it's also a very useful tool for checking the stability of a CPU.
Now back on topic. A short pretty long now while ago I wrote a small graphical front-end for it, named it LinX and hosted it on a great Russian overclockers' forum forums.overclockers.ru.

Holy cow, it's been 4 years.

Changes in latest LinX v0.6.5:

- works with latest Intel Linpack binaries
- now uses Linpack's built-in error detection logic
- horrible source code available on GitHub

Couple of screenshots:





Some main features:

› a simple and intuitive interface
› max available memory detection and an option to use all available memory
› both Intel and AMD CPU support (thanks Right from forums.overclockers.ru for that)
› both 32 and 64-bit Linpack support
› Intel HyperThreading support (Pentium 4, Atom, Corei7) and ability to override the number of testing threads
› Linpack can be started with different priorities
› elapsed, estimated and approximate finish time displaying
› ability to test for a specified period of time
› optional sound beep on error/successful pass
› settings for the last run are remembered
› visual indication of testing process to quickly determine possible system hang
› monitoring data import from Everest or Speedfan and ability to create graphs for core temperature, fan speed, vcore and +12V voltage
› screenshot and graph saving in PNG format
› tray icon
› command-line keys support to automate testing (run LinX.exe -help for full list)
› no additional redistributable packages needed
› no installation required (however, there is a version with installer too )

Note that I'm rather new to programming, so there may be some bugs in there. Should you find one, report it and I'll do my best to fix it.
And note that I'm Russian, so some mistakes in text may also be present.

Just unpack the archive and launch LinX.exe.
That's it, hope you'll like it. Should you decide to give it a try, please comment. Every feedback is appreciated.

[burebista]

OK, I give it a try.



Vista64 SP1, 4GB RAM. I must kill it with Task Manager.

[Pyr0]

same error here in vista64 but with just 2x1gb of ram atm

[Dua|ist]

Damn, I don't have a Vista 64 installed atm, but now I guess is the best time to install it. I'll fix this asap.

And if you uncheck the 64-bit mode, still the same result?

[burebista]

Yep, but now it tells me that is not enough memory. The bright side is that it doesn't remain memory resident.

[RJARRRPCGP]

Yep, but now it tells me that is not enough memory. The bright side is that it doesn't remain memory resident.

Dua|ist, I believe to get around the 2 GB per-process limit is to have 2 Linpack processes! Sorry.

[Dua|ist]

It loaded mine 99.9%, all 8 threads, but there is some memory bug. Refuses to run sometimes with stopped unexpectedly, error not enough memory. If I try to run with 256 mb, very small, it tells me not enough memory and kicks it up to 1748. It will only let me run at 1748, no less, and half the time when I pick 1748, it tells me not enough memory, though I have 2748 free. (I know there is 1748 limit with xp 32 bit).

But once that bug gets fixed, pretty sweet being able to load all 8 cores with one instance at max memory

At least it works on all cores. Here's the fixed version : LinX 0.5.5.1

Dua|ist, I believe to get around the 2 GB per-process limit is to have 2 Linpack processes! Sorry.

Question is, whether we need to get around that limit at all? Most systems with 4GB of RAM and more have a 64-bit OS, and x64 version of Linpack has no such limit. There are of course 32-bit OSes with 4 GB of RAM and ~3.5 GB of useable memory, but that 2 processes idea was just a temporary fix to load all cores when HT is on. Now that it can be done in a much better way via Linpack itself I don't see any reason to keep this option. The current ~1750 MB limit for 32-bit Linpack is enough to adequately stress-test any CPU, while RAM testing is not Linpack's goal anyway. If you still want to test all your memory, just run 2 instances of LinX.

[WoZZeR999]

In Vista x64, when I try to run 256mb @ 100 times, I get an "Terminated unexpectedly" error. It seems to be running in the background, but the front end thinks that linpack is closed.

[Dua|ist]

All right I got it... First of all when running in 32-bit mode, try to set 2048 mb of memory or less. Maybe 2GB is a limitation of 32-bit Linpack itself. If so, I'll add a check for it.
As for the 64-bit Linpack, it's weird and I doubt I'll be able to fix it until I install Vista 64. And this won't happen till weekend, sorry.

[Pyroe_Inc]

All right I got it... First of all when running in 32-bit mode, try to set 2048 mb of memory or less. Maybe 2GB is a limitation of 32-bit Linpack itself. If so, I'll add a check for it.
And this won't happen till weekend, sorry.

IntelBurnTest make a similar error.

[nullface]

"Either "linpack_xeon32.exe" or "linpack_xeon64.exe" was not found Program will close."

Is it becourse i run a E3110? I use XP32

[Pyroe_Inc]

"Either "linpack_xeon32.exe" or "linpack_xeon64.exe" was not found Program will close."

Just the program is in the .zip file in attachment (you'll still need to have both 'linpack_xeon32.exe' and 'linpack_xeon64.exe' in the same directory to run it).

[Dee]

"Either "linpack_xeon32.exe" or "linpack_xeon64.exe" was not found Program will close."

Same for me.

[Evilsizer]

Same for me.

umm you need to download LinX.7z from rapidshare then the attached .zip file...

[slim142]

Suscribing. Fix this couple of bugs and I will make sure to use it everytime I overclock

[Dua|ist]

Suscribing. Fix this couple of bugs and I will make sure to use it everytime I overclock

Thank you for your support. I think I have found a way to fix this (at least I hope so). Might upload a newer (possibly fixed) version tomorrow.

[slim142]

Thank you for your support. I think I have found a way to fix this (at least I hope so). Might upload a newer (possibly fixed) version tomorrow.

Thats great to hear
I really like the design you gave the program. Hope to see the new version soon

[Dua|ist]

OK, I've coded a newer version. It actually does the same but in a little different way. I'm still without Vista64 (yet), so I tested it only on my XP32 where it works fine (just like the previous one though).
Once again a Rapidshare link with full 7z archive: LinX 0.4.4.

Only the program is in the attachment.

Hopefully this one will work. Please comment if it does (or doesn't).

[burebista]

Yep, you did it. Good job, I like it.

[Dua|ist]

Yep, you did it. Good job, I like it.

I can't express my happiness about that!
Time to update the 1st post.
Suggestions and bug reports are still welcome.

[OC_Newbee]

Thank you! will give it a try tonight.

[dafeeessh]

very nice work good job.

[WoZZeR999]

Nice work, it seems to fix my high run count with low memory runs. I know the progress is displayed in the lower left hand corner, but could you make an option to turn the elapsed time bar into a progress bar? If not, no big deal, thought it may be cool, as you can take a quick glance to see how far it is.

[Dua|ist]

I know the progress is displayed in the lower left hand corner, but could you make an option to turn the elapsed time bar into a progress bar? If not, no big deal, thought it may be cool, as you can take a quick glance to see how far it is.

A nice idea indeed. I'm not sure yet, whether I'll be able to implement it, but I'll try.

[HDCHOPPER]

exellent man exellent thanks for shareing this !