Try with this version: memset
Printable View
Try with this version: memset
Any luck on the P35 memset that may work on the Asus PK5 dlx yet?
If memset support P35,it work on a asus and gigabyte or other MB with this chipset, but I need more info for finish the update... coming soon. :)
If you need any help and we can help...please tell it to us :)
what's the question???? help with what?? looks like buffalo d9gkx
Exact, memset don't detect correctly the multiplier,
so if you see a difference in memset between cpu-z, cpu-z is right.
Sorry for this inconvenience, I dont find a solution for now...
It seems that there wonīt be Memset or any similar programs for P35 or itīs successors.
The dram timing registers of Bearlake chipsets can be read and virtually written, but there is no real effect what so ever.
This is because the different dram timings are more or less tied together by several algorithms that are executed during memory initialization sequence.
In practice this means that the dram timings cannot be changed without resetting the mch. The timings can only be changed from the bios.
To prove a point, I changed dram timings to 1-3-3-7 (tCL-tRCD-tRP-tRAS) on the fly. It is clear that there is no such ram that can operate with those timings at DDR1000 (without mentioning P35 supporting tCL 1 Clocks).
CPU-Z Validation at DDR1000 with 1-3-3-7 timings
To prevent people from cheating in memory overclock / timing records none of this data will be published.
Darn that is terrible news. :( Maybe bioses will eventually allow adjustments of all ram timings. :confused:Quote:
It seems that there wonīt be Memset or any similar programs for P35 or itīs successors.
wonder why they decided to do so that way
bugger
boo
one point minus to p35... maybe x38 will be less locked :D
I've already got one P35 board, not buying anymore till' this is fixed. IF it gets fixed...:rolleyes:
Well, that's a kick in the nuts :(
Edit, I just got it, 1337 timings for DDR1000 lol! :D
:up:
;)
Good news for Gigabyte users and bad for Asus users.
It seems that only Asus is locking the dram timings registers since they can be actually written on Gigabyte boards.
There is something in Asus bios that makes MCHBAR locked.
The MCH programming is completely different between Asus and Gigabyte.
And so is the MCHBAR address. Thats why the testers could not get any data extracted.
Atleast tRCD, tRP, tRAS can be changed on Gigabyte.
I haven´t tested the other timings yet.
OH BOY! :) :thumbsup: