...no, memset don't support 965 Mobile chipset for now.
memory configuration space is completely different than 965 desktop chipset.
Printable View
...no, memset don't support 965 Mobile chipset for now.
memory configuration space is completely different than 965 desktop chipset.
Ok, looking forward for newer versions then ;)
@FELIX:
Q: why doesn't Memset show/allow to config tWR timing [Write Recovery Time] (at least on P35 chipset)?
I also see that tRC is missing @P35 but I guess it's normal on this chipset and not an omission (I had AM2 before and rRC was there in MemSet AFAIR). Is tWR same story on P35 chipset as tRC (but then, latest Everest DOES show tWR on P35, so...)?
please explain this tWR thing @P35...
ps any chance to add advanced AMD/AM2(+) timings I had asked about a few pages above, please?
ps2 also, latest Everest started to show a few more P35 MC timings not available in MemSet currently:
- DRAM Read ODT
- DRAM Write ODT
- MCH Read ODT
is it feasible to add them to MemSet, too (to be able to config them at view their current values at least)?
ps3 what about CR (Command Rate) on P35?
-For Write Recovery time, read post #583 in this thread.
-tRC is not present in Intel MCH registers.
-I add some timings for K8-DDR2 in 3.4beta.
-Changing Command Rate on P35 under windows have no effect on performance,
it's why I disable it on 3.3beta version and replace it by an other timing on final version.
FELIX
PLS list the command rate so we know what is being selected as some mobos don't list it and others may be buggy that's all
i also like to test mobos first with everything auto to see how they behave at different FSB ;) :)
There is mine with Asus Maximus Formula:
CPU-Z Dump
http://kotisivu.dnainternet.net/bull...etFSB_beta.png
@FELIX:
thanks for for the explanations.
1 more Q: P35 chipset and tRTP timing [Read To Precharge Delay] - latest Everest shows it as 5T (in my case) while MemSet 3.4b1 - as 3 (it's called Read to Precharge in MS). Why that difference? According to SPD tools it should be 3 as well for that freq (DDR2-800).
New beta version: memset34beta2
-Fix a bug with tREF on some P35/X38, when "0" value is show after apply.
Sorry for this inconvenience. :(
FELIX
Again want to thanks for your work and dedication, memset is a great program. Although I feel depressed when I think I have to change DPI settings and reboot each time when I want to use it. Would you fix that BUG and allow running it with various DPI scales ?
Thanks
FELIX
PLEASE add command rate in there again (testing different mobos that don't have the CMD rate selection means that we are in the dark what's selected as CPUz doesn't reliably show it still)
Command Rate is detected by a single bit in MCHBAR registers.
The value is either 0 or 1.
CPU-Z can read the command rate on any current Intel chipset.
the thing is stilt it wasn't reading properly on the Gigabyte P35T-DQ6
CR (Read only) added in this version: memset34beta3.exe for chipsets 965/P35/X38.
Work on mine, but don't sure that it's work for all MB/chipsets.
...no, work only with bios #11.
mchbar is locked in write with others bios, and I can do nothing.
Did I miss it where is the P35/P38 Memset link?
...read post #692. :rolleyes:
Would it be possible for a Linux version of memset? Only thing I miss in Linux is this program and games. >.>