New Memory Tweaker for Intel Chipsets

[GazC]

Not such a kick in the nuts after all then.

[bmg]

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.

Another plus for the Gigabyte is that it's memory latency numbers seems to be better than the P5K Deluxe. There's a lot to like about the Asus board so hopefully it'll continue to improve.

[dinos22]

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

looks like i'll have to buy a Gigashyte board again

[zsamz_]

oh

looks like i'll have to buy a Gigashyte board again

i did lol asus slackin off

[FELIX]

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.

It's very strange, an address or an other is not very important,
seeing that it's the reel address of MCHBAR.
Perhaps asus use an address for read and write, and an other address for read only...
Since 915 chipsets, MCHBAR address is practically always FED14000,
I just check on differents dump of P35, it's the same for Gigabyte motherBoard,
but different for Asus (3FFB0000 or 7FFB0000).

Try to read at Address FED14000 with pmem on a asus motherboard, it will be interesting...

Edit: In case it MCHBAR was locked on Asus MB:
if((Chipsets==iP35)&&(MBString=="ASUSTeK Computer INC.")) Write->Enabled=False;
like that no cheat

[The Stilt]

Got it working on Asus too

Weird stuff I must say

Reading the same address that Gigabyte used resulted only null data, so it is not the same address.

The MCHBAR baseaddress at 0x48 bus 0 / device 0 / function 0 had to be
re-written. The original address seem to block the write attemps.

FELIX will get the final data soon.

[hipro5]

Thanks for your time and effort guys.......

IF sometime FELIX decide to accept donations for his lovely work, I'll be glad to donate via PayPal.....

[FELIX]

Got it working on Asus too

Not easy to do.

Reading the same address that Gigabyte used resulted only null data, so it is not the same address.

When you say "null data" it's 0x0000 or 0xFFFF?

The MCHBAR baseaddress at 0x48 bus 0 / device 0 / function 0 had to be
re-written. The original address seem to block the write attemps.

You can't write a new address in this register,just write 1 at bit 0 for unlock mchbar.

FELIX will get the final data soon.

I hope get it tomorrow, official release for P35 is the 4 june

[FELIX]

Thanks for your time and effort guys.......

IF sometime FELIX decide to accept donations for his lovely work, I'll be glad to donate via PayPal.....

Very thank for this suggestion hipro5,

but I don't want any donation by XtremeSystems guys, simply cause
a lot of you help me to develop/debug this soft,
and surely memset don't be the same if you are not here.
Also I think some guys like you or The Stilt and others
pass a lot of time for help.It's my contribution.

On the other hand, I will probably sponsored soon

[dinos22]

Got it working on Asus too

Weird stuff I must say

Reading the same address that Gigabyte used resulted only null data, so it is not the same address.

The MCHBAR baseaddress at 0x48 bus 0 / device 0 / function 0 had to be
re-written. The original address seem to block the write attemps.

FELIX will get the final data soon.

OMG dude i almost had to buy gigashyte board again


thanks very much

[The Stilt]

FELIX, email sent.

It is up to you now

Now it´s whiskey time

[OldGuy]

Keep up the good work Felix Saving people from buying things they don't really want is a community service I feel compelled to remind folks that there is this thing called a bios and you can actually make changes there that will effect your computers performance

Keep up the good work dude for the hardest of the hard core

[dinos22]

it would be nice if companies did in fact have ALL RAM timings in the bios so that we don't have to resort to this software (well i would still use it for on-the-fly tests)

[OldGuy]

it would be nice if companies did in fact have ALL RAM timings in the bios so that we don't have to resort to this software (well i would still use it for on-the-fly tests)

Dream on Though if they provided everything it would leave little for guys like Felix to figure out for the rest of us common folk. I'm always amazed at the level of knowledge that floats around this place. They make it easy for us mortals to plug in numbers and feel like we actually did something on our own

[dinos22]

Dream on Though if they provided everything it would leave little for guys like Felix to figure out for the rest of us common folk. I'm always amazed at the level of knowledge that floats around this place. They make it easy for us mortals to plug in numbers and feel like we actually did something on our own

tell me about it

[FELIX]

FELIX, email sent.

It is up to you now

Now it´s whiskey time

...just got it: great work!

[Chosen.]

I have to say kudos and thanks for the great job, to both of you and everyone else who assisted.

(I can't wait to start using memset again in my P5K )

[Brama]

Thanks to Felix, The Stilt and everybody.......my Gigabyte DQ6 is ready to test new version of memset

[BAR*B*Q]

when i close memset 3.2 all timing readings are wiped out at least with xp64.
could you guys help ?

[xgman]

I know you will find a way Felix.

[Hutch]

when i close memset 3.2 all timing readings are wiped out at least with xp64.
could you guys help ?

Either check or uncheck 'lock mchbar.' It's at the bottom of the memset screen.

[yotomeczek]

Not easy to do.

I hope get it tomorrow, official release for P35 is the 4 june

Is Memset working with P35 avaliable now ??

[FELIX]

Not again, coming soon...

[BAR*B*Q]

Either check or uncheck 'lock mchbar.' It's at the bottom of the memset screen.

aah... thx mate. i had to unlock it.

[Learn]

Just installed windows 2003 X64 and memset 3.2 doesn't work.
I found a fix:
install TVicPort 4.0
http://stuffmate.com/download/tvicport/
reboot
and i started memset 3.2 (zip version) it works
voila