:up: :up: :up: Felix - Your the man !!! Vive La France !!!
Printable View
->Anaya, neo2005th: what is happen when you save change?
Otherwize, check that you have an file named MemSave in C/: (C/:MemSave)
and check that you have an icone in the startup folder.
I install the program, i have the c:/memsave folder, memset icon is in startup folder, but the save changes button is deactivated, say: "Del. Save" but is inactive.
Capture http://i13.tinypic.com/712gehu.jpg
How do you proceed for use the save function on K8!?
I have disabled it on K8/K10 in beta4 for now... :confused:
Finale version coming soon... ;)
Proly has been asked before, any support for X38?
yeah the latest Beta 4 works great with X38.
Please, make 965pm support happen in the final version. I can't take it anymore, need more OC :D
Seems Gigabyte X38-DQ6 with F7D bios broke memset again heh wrong memory clock speed detected
http://fileshosts.com/intel/Gigabyte...3m22s813ms.png
cpuz dump here
hey eva ,can u change the cas latency ctl .on the DQ6 and beta memset?
ive no problem changing the others .but no go on the top one .
im using ballastics 8500 .
memset has never been able to properly case CAS value on any platform ... i mostly only use memset to display values.. to change i do it from bios ;)
Thread is stuck now
Keep the very good work Felix :up:
In the name of all XS comunity, a big thanks for the MemSet tool :clap: :clap: :clap:
what Pedro said and its about time it was stuck :up:
hey Felix, thanks for the continued work on Memset. have you thought about perhaps setting up a donation slush fund? just a way for us to financially say thank-you for all your hard work.
also, one suggestion...or i guess you could call it a request. i was wondering if you would be able to write into the program the ability to remember its screen position when it closes? that way when it opens the next time it opens to the spot where it was last closed from. i just found out that CoreTemp does this, only after you enter the settings screen for some reason, but it is kind of nice not having to always move it to the same spot when doing endless screenshots of the same nature.
thanks again Felix...keep up the great support, it is much appreciated :up:
Yeah remember screen position is very useful :D
maybe cpuz and memset authors can work at merging the two apps for one tool for all overclockers to must have - make screenshots alot easier :)
Sticky again: thanks guys. :)
Not Gigabyte problem, but Intel "problem": I use RDTSC for read frequency,
on most of Intel CPU, this instruction return FSB x max multiplier (9 in your case).
By deduction, in memset I do: Read memory frequency= (RDTSC : max multiplier) x ratio FSB/DRAM.
But with some CPU, RDTSC return FSB x real multiplier.
cpu-z read the multiplier in MSR register, it's the best way but I can't access RDMSR instruction.
Not possible to change Cas# under Windows.
The link is to beta 4, but the file name says beta 3.
:D Hey Felix,
maybe some more work for You. On X38 chipset DDR3 it shows 2T though I'm running my mem 1T.
But the same bug appears on CPU-Z 1.42...............:confused:
Hope You can fix it.;)
:up:
Here is the 3.4 finale version: MemSet.exe
-Add support for Intel X38 chipsets.
-Add support for K10 DDR2 and DDR3.
-Replace Precharge to Precharge delay by Refresh period (tREF) timing,
and add Command Rate detection, on 965 and P35 chipsets.
-Add some timings for K8 DDR2.
Tell me if you find bug or problem...
And here is my new website: www.tweakers.fr
You can find update, some timings explications and others.
Note that it's a beginning, I'll improve it in time... :)
w00t, thanks Felix :)
final catches the mems ok ,but now cpu-z 142 is partly blank .maybe its couse im running 1:2 .thanks felix .http://peecee.dk/index.php?lid=1&aid...2&loadid=83470