New Memory Tweaker for Intel Chipsets

The CAS value could only be changed in some older versions. Since moths ago this is not available, regardless the SO.

That's because on most Intel chipsets you cannot change CAS Latency ( tCL ) after POSTing ( in windows/linux, etc )

OK, I get it. Thanks!

1) Memset hangs when run on the same directory with the auto-generated ini file

2) Memset will not hang when the settings are saved for automatic application on Windows startup because Memset will configure the auto-created shortcut to be run on the C:\MemSave directory instead of the nested directory inside the installed location which is created when the "Save" button is pressed.

I used Memset to set my "performance level" to 1. I immediately saw good results in SuperPI without losing stability in orthos or games. So I've decided to save the settings to be applied in Windows startup.

However I noticed that the settings were not applied on Windows startup. The auto-generated shortcut was created for a file on the "C:\MemSave" directory which didn't exist.

Apparently as Memset is now installed inside Program Files, creates its auto-startup files in a child path which is "C:\PROGRAMS\MemSet\MemSave".

Fortunately though; because in reality there is something wrong with the creation or application of the MemSet.ini file which results in immediate hangup of the system. (The 1st bug negates the second).

Fixes proposed:

1) Memset should point the auto-startup shortcut to the proper location of the auto-generated MemSave directory

2) Memset should create the correct MemSet.ini file so that it doesn't hang the system.

Additional info:

This screenshot shows MemSet with my setting. Hitting apply does not hang the system:
http://img155.imageshack.us/img155/3...age1rg2.th.png


The following code is the MemSet.ini that was automatically created. If this file is present along the MemSet executable, MemSet will hang the system.

Code:

---

[MS9XX]
AN=1
1A=1
1B=1
2A=2
2B=2
3A=2
3B=2
4A=1
4B=1
5A=5
5B=5
6A=1
6B=1
7A=20
7B=20
8A=0
8B=0
9A=7
9B=7
10A=5
10B=5
11A=2
11B=2
12A=5
12B=5
13A=4
13B=4
14A=1
14B=1
15A=12
15B=12

---

I understand that the "Performance Level" refers to the 8A and 8B registers. I've changed Performance Level to other settings (including the default) and the registers change as well but the hanging problem still exists.

Therefore I think MemSet creates in .ini file that contains settings I didn't manipulate which are incompatible to my system.

Thanks for your time.

@Felix, do you have a beta or something that supports G35 chipsets? I have a P5E-VM HDMI that needs tweaking.

->Vix: where is installed your OS? (C:\ or D:\....)
Could you try with this version.

->The Nemesis: could you try with this version too.

Felix: 1st thanks for the nice program. nice work!

since 3.5final tRTP reads 2 high from what I set in bios, with a 3.5beta I downloaded earlier this does not happen. I can ofcourse keep using that beta, but just wanted to report, maybe you can fix it.

btw. it's on a dfi p35dk.
http://xs128.xs.to/xs128/08233/trtp-off327.jpg.xs.jpg

tnx... Darkje

...could you check the tRTP with Everest.
I made a change in 3.5 for this timing, but it's seem that
this value it's not the same between different motherboard.

Everest (4.50.1394b) also shows tRTP=5 :(, but everest shows odd values on some of the other items too...
maybe DFI was reading it wrong?
I'll stay at 3.5b for now, as that seems to match what I set in bios.

Quote:

---

Originally Posted by FELIX

->Vix: where is installed your OS? (C:\ or D:\....)
Could you try with this version.

->The Nemesis: could you try with this version too.

---

I runs but the readings are incorrect.

Could you send a registers dump (with cpu-z) at memset@hotmail.fr...

Thanks for this great program FELIX! :party: :rocker: :rocker:

->The Nemesis: you can try with this version
It seem that G35 is the same that 965 chipset for mchbar timings, but not indicate in the datasheet.

Quote:

---

Originally Posted by FELIX

->Vix: where is installed your OS? (C:\ or D:\....)
Could you try with this version.

---

Felix, the serious crashing bug is fixed on MemSet352beta.exe (MemSet351beta.exe didn't exist). Two issues here:

1) A "ding" sound comes when running MemSet.exe when the MemSet.ini file is present on the same directory. (However the settings were applied correctly.)

2) Pressing "Save" creates a shortcut on the user startup directory which points to an incorrect "C:\MemSave" location. MemSet has been installed to its default location: C:\PROGRAMS\MemSet

Is it possible that the problem is due to my Program Files directory is C:\PROGRAMS and not C:\Program Files ?

Thanks for your attention.

Felix,

Why is the program installing both 32bit and 64bit drivers? On vista only 64 bit is allowed. You just make the system try and load it, stall and kick it loose, but if I delete it, your program not run.

What is it?

-R

->Vix: the "ding" sound would be fixed with this version. :)
The "C:\MemSave" location is normal, you can check that the file exist.

->DualCpuUser: I'll try to fix this problem at next.

OK, the "ding" no longer exists

When pressing save, MemSet creates a MemSave location under its own installation directory: C:\PROGRAMS\MemSet\MemSave

However it also creates a shortcut which points to an incorrect location (C:\MemSave) which results in settings not running at startup unless one corrects the shortcut.

However, MemSet is now fully functional. Thanks!!!

How is named your Windows file? is it C:\WINDOWS?

Quote:

---

Originally Posted by FELIX

How is named your Windows file? is it C:\WINDOWS?

---

No, it's C:\WIN

Specifically:

%SystemRoot%=C:\WIN
%ProgramFiles%=C:\PROGRAMS
Users directory (usually Documents and Settings) = C:\USERS

I am changing the names at setup with nLite for security reasons as well as compatibility with certain old programs.

...OK, try with this version: memset353beta

Felix

First, let me say what a fantastic job you have done with MemSet.

Secondly - This may seem like a real stupid request, but I'll ask anyway.

Is there any way to change MemSet to work on a 120dpi desktop?

I have to revert back to 96dpi every time I would like to use the program (which requires a restart).

I am using Vista Ultimate (64 bit).

Thanks

Felix, the latest beta fixes the startup issue. Memset now creates a real C:\MemSet folder which is correctly pointed to from the startup shortcut.

Excellent!

By the way, I wonder if anyone else is able to reach such a low "Performance Level" settings (low is good thing).

My memory runs at 1.9 volts only (Crucial d9gmh) at 4-4-4-3-6 timings at 780 Mhz. Performance level at 2 and works without problems. I've searched the net and it seems most people stop at performance level 6 (if possible, many have problems with anything less than 8)

Quote:

---

Originally Posted by Vix

My memory runs at 1.9 volts only (Crucial d9gmh) at 4-4-4-3-6 timings at 780 Mhz. Performance level at 2 and works without problems. I've searched the net and it seems most people stop at performance level 6 (if possible, many have problems with anything less than 8)

---

I was never able to go below 6 with an X48.
If you can check the performance level from the BIOS, does it match the value displayed by memset?

I never heard of such a low figure.

Has anyone gotten it to work on this board, and if so, what BIOS?

I'm over in the abit forums, and no one can get it to work over there (everything is just "locked" in place), but one member thought that some people over here got it to work with an older BIOS.

Thoughts?

Memset works with any BIOS older than v1.4

Edit: Just checked my review to be sure

Quote:

---

Just don't forget that it won't work with any BIOS release after v11 ( and up to v16 Beta 1

---