Nice, I'm going to try this program out.
Printable View
Nice, I'm going to try this program out.
OC_Newbee
I think I've fixed that bug on Vista64 with max mem option.
As reward for your patience LinX now can be resized vertically for more test results to fit on the screen (thought it might be useful for screenshot purposes).
Something like that:
http://img152.imageshack.us/img152/1...ightgf2.th.pnghttp://img152.imageshack.us/images/thpix.gif
Full archive link: LinX 0.4.8.2
You are awesome! again fast service as usual. Thank you very much.Quote:
Originally Posted by Dua|ist
Quote:
Originally Posted by Dua|ist
Nice - great work. So just wondering what would you suggest would be a good amount of runs to prove stability? I've just been running 3 passes right now and its a pretty good indicator of prime stabilty.
Well, I usually start with 5000-6000 problem size, say 15-20 passes, just to see if there's any chance for CPU to be stable at that frequency. If it passes OK then 10000 or maybe maximum memory (about 14K on my 2GBs) for 20-30 times. For me it's good enough to call it rock stable (CPU-wise at least). Some people prefer something like 100-200 Linpack passes at maximum possible memory though. It's a matter of taste I guess. :)Quote:
Originally Posted by dnottis
Same here 20-30 pass plus maximum memory available. Some time to get windows to release the maximum memory available I run a short 1-2 pass for about two rotation before proceed to 20-30 pass, this way linX will use at least 3000mb or more (utilize 95-98% of memory) of 4 gig.Quote:
Originally Posted by Dua|ist
Ok, here's yet another update: LinX 0.4.9
Changes:
- possibly fixed a bug when LinX would fail & exit if an error was detected in the last test
- added "Always on top" mode. Double click window caption to toggle it
- LinX now saves its window's vertical size on exit
- when "Enable sound notifications" box is checked LinX will also play sound upon successful completion of all tests
- added status bar flashing during testing
- minor UI changes
Thanks for continuing to improve this great tool. I do have one issue though...it's not a very big one. Whenever I select max memory, it still overestimates and fails (it's very close though). I just ran this latest version and it says the max memory is 1989 mb (I have 4 Gb, and XP sees 3 Gb as usual). But when I run at 1989 mb, it fails with the not enough memory error. I have to step that value down to 1800 mb in order to run (which appears the be the max memory I can run the tool with). Just an FYI. Thanks again.Quote:
Originally Posted by Dua|ist
platojones
Thank you for that info. I know that max memory algorithm for Linpack 32 isn't perfect, but it's mostly because of Linpack32 limitation (which should be somewhere around 2GB, but seems to vary on different systems). Problem is, I have only 2GB RAM and thus can't play with it. The 1989 MiB value was suggested by one member of russian overclockers' forum, who reported it to be the maximum possible to run Linpack32 on his system. Is the 1800 MiB the max possible for your system (i.e. setting 1801 results in Linpack's not enough memory error)?
got a suggestion. can u do a moving logo so I need to move my mouse to know my rig hasn't freezed?
The status bar (the green one) is now flashing every second during testing since v0.4.9. This was added just for the purpose you mentioned. I thought flashing woud be visible enough...:confused:Quote:
Originally Posted by Shrekogre
ah i must have missed it. sorry.Quote:
Originally Posted by Dua|ist
Nice
Upgrading my files right now!
Nice job Dualist, for a moment I thought you were already thinking about leaving this program... (never had a problem ;) )
Thanks for the update!
Hi Dua|ist,Quote:
Originally Posted by Dua|ist
Yes, 1800 is the approximate max for my box (I just got it within 100 mb when I was testing with it, because I know 1900 caused it to fail)...but I suspect it is different on each box, it's weird how XP handles max memory a 4 GB box. But just now, playing with it, 1881 is the max I can go before it errors out. 1882 results in error for me. Keep up the good work. It is appreciated.
No way. There's still a lot of things to do. And as long as somebody is using LinX (and that'd be at least me :)) I'll do my best to improve it.Quote:
Originally Posted by slim142
I'll try to examine this problem more closely (once I finally make a visit to my good friend nearby with couple of my G.Skills ;) ; I just hope they will be good neighbors to his Tracers :D).Quote:
Originally Posted by platojones
Great...it's not a real big deal though. You have a very nice feature where it keeps it setup state, so once I dial in the max memory for my box, it keeps it unless I change it...very handy feature!Quote:
Originally Posted by Dua|ist
Dualist
0.4.9 already has the new 1.7 files from IBT right?
Thanks for the great UI for this tool Dualist. Been testing the heck out of my system ... so far so good!
Hm, just checked Intel's site and haven't found any new Linpack executives there. The latest ones according to Intel are from 20th of August, and LinX uses those since its very first versions.Quote:
Originally Posted by slim142
Well, I ask because there is a new version of IBT. It is 1.7 and the changelog says "updated the files" or something like that so I wanted to make sure you also kept the stress files updated.
Maybe Im wrong and you already have them.
excellent little app, thanks :up:
the interface is much nicer than IBT :)
slim142, i believe IBT 1.7 is using some customized linpack binaries
Quote:
Originally Posted by AgentGOD
oh well, if thats the case then is ok. I rather stay with official files for now.Quote:
Originally Posted by Pyr0
I like this.
I've been using IBT, but i'll likely start using this as i prefer the GUI.
Both are great though; much easier than having to fiddle with the non-packaged LinPacks like in the old days.
Yeah
Like another member said, the classic IBT gives eye cancer...