The CAS value could only be changed in some older versions. Since moths ago this is not available, regardless the SO.
Printable View
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.
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.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
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.
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.
I runs but the readings are incorrect.Quote:
Originally Posted by FELIX
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.
Felix, the serious crashing bug is fixed on MemSet352beta.exe (MemSet351beta.exe didn't exist). Two issues here:Quote:
Originally Posted by FELIX
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?
No, it's C:\WINQuote:
Originally Posted by FELIX
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)
I was never able to go below 6 with an X48.Quote:
Originally Posted by Vix
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
@Felix
Here's a screenie of whats happening on G35. Cas is showing 10 Command rate 1T. Adjusting performance level seems to work but is had negative effect. Not sure what effect other adjustmests are having a system typically locks after hitting apply. Trying to drop done to 475 FSB now and try again.
Hello all!
I'm talking with some people over in the official abit overclock thread for this board, and a lot of us are not able to get MEMSET to work with this mobo. When you run the program, all the options are unchangeable, including the "lock mchbar" checkbox (which is checked), though im just guessing that this is the feature that locks/unlocks the mem timings for adjustment.
Anyway, someone mentioned that people over here had gotten it to work with an old BIOS of the board.
So, has anyone gotten MEMSET to work with the abit IP35-Pro (and if so, with what BIOS), or have any ideas why everything is "untweakable"?
Thanks!
->The Nemesis: I'll fix it soon.
->sirrealist: since bios 11, mchbar access is locked in write on Abit IP35, and I can't do nothing.
Damn... that BIOs is before they updated the microcode for the 45nm chips... no going back to that one.Quote:
Originally Posted by FELIX
What exactly us the "mchbar locked" option? Does it have to be unchecked to be able to change your timing values? I.E., since BIOS 11 we cannot change timing values using MEMSET on this mobo, or is "mchbar locked" unrelated to not being able to use the program to adjust timings on this board?
Look at Bus 0 Dev 0 Fct 0 ,OffSet F4h, bit [0];
If bit[0]=1, your MCHBAR is locked in the bios, and is not possible to reset this bit under windows. Only Abit can fix this problem.
Visit the abit sector of rebels haven. The admin has mods for the ip35 pro board and if not the one you need, I'm sure he can make one. Just post a link to the bios you want modded as he is on dialup because of where he lives.
so, by unlocking the MCHBAR i would then be able to edit RAM timings using the program?Quote:
Originally Posted by JWilson
I don't really know what the MCHBAR is, and what the ramifications are of having it locked. Only when its unlocked can you edit ram timings using MEMSET?
About first question: yesQuote:
Originally Posted by sirrealist
Someone locks MCHBAR to prevent using programs like MemSet. When it is unlocked, you can program it with MemSet or similar programs.
Called MCHBAR are the I/O memory locations of memory controller in PCI space: you can enable/disable functions or set timings.
-> sirrealist: Problem is mchbar can be unlocked only in the bios; perhaps with a bios modded.
Let me know if you can find it.
->The Nemesis: Reading Cas was fixed in this version;
For Performance Level, I know that it's don't work on some chipsets, sorry.
Rebels Haven posted a mod bios for the IP35 Pro that adds new Items Performance Level and Trfc. It leaves my MCHBAR unlocked, but I'm running XP. Are you sure VISTA isn't locking it?
http://www.lejabeach.com/ABIT/IP35Pr...5probios-2.jpg
...are you sure that you can apply settings with memset and this bios?
-I just flashed my IP35-pro with it (M629B_17.XXX) , run fine but mchbar still locked under XP.
My mistake, I mis-understood. But Polygon just posted this:
Quote:
Please re-download the Mod BIOS. Date on new files is 6/21/08. I added code to leave the MCHBAR unlocked so the Memset will be functional.....
Thank jWilson. :)
I have flashed with Bios 17.
mchbar is unlocked and memset work fine now.
Here is the bios modded download main page: http://www.lejabeach.com/ABIT/IP35Pro/
a great thank at Polygon for his work.
Hi all,
I have an ABiT IP35 Pro board, and have flashed to the Modded -17 BIOS, am using Memset 3.5.3 beta, but Memset still shows "MCHBAR Locked" at the bottom and nothing is changeable.
How is Felix getting it to work or why wont it on mine? :shrug: lol
Thanks, cool program if I could get it to function fully.
Have you reinstalled MEMSET? Maybe it's worth a try!Quote:
Originally Posted by Blitzman
Oh, just saw it's your first post: Welcome at XS!
Thx for the welcome Don Dan,
Yep I just tried uninstalling Memset, turned computer all the way off, started back up and reinstalled Memset 3.5.3 beta but still getting MCHBAR Locked....
dunno why...
System BIOS : 05/26/2008-P35-W627DHG-6A79OA1BC-17
Thanks
oh yeah and i did let system reboot after re-installation of Memset :)
Just make sure both "Invoke Boot Agent" Items are "Enabled". They are under "Integrated Peripherals".. The assembly code is substituted for the boot agent and they must remain enabled for the code to execute..
Well Geeya Mr Wilson, you sure fixed that one! LOL Was like thinking of Dennis the Menace talking to Mr Wilson har.
Yep that cured it! I had one Ethernet controller disabled cuz I was not using it.
Thanks very much!
Now I can more easily experiment :)
This should be a sticky note somewhere or something
It is here:Quote:
Originally Posted by Blitzman
http://www.rebelshavenforum.com/sis-...;f=37;t=000120
Wow, I've seen some appalling unreadable forum designs, but that one takes the biscuit. :eek: Tiny text, white on black, link underlines obscuring the text... whoever designed that should be shot.Quote:
Originally Posted by JWilson
Sorry for OT.
Everything looks good except command rate still reads wrong. I'm showing 1T. Thanks for all your effort now off to bench:)Quote:
Originally Posted by FELIX
***Edit***
Cas lat still can't be changed
Hi Felix,
Not sure if your aware of this, apologies if you are. :shrug:
Praz & I have found a few misreadings after manually changing bios values, with the
DFI UT X48-T3RS LanParty
Quote:
Following on from Praz's discoveryQuote:
tRD - 8.5, Memset Misreads The Value When Set Manually
I've found 2 more. These also occur when values are set manually in bios.
Working at 485 400/1600 on Auto
Write to Precharge Delayed (tWR) = 20
Write to read Delayed (tWTR) = 16
I manually changed to:-
Write to Precharge Delayed (tWR) = 22
Write to read Delayed (tWTR) = 17
with the resulting memset values :-
Write to Precharge Delayed (tWR) = 26 (+4)
Write to read Delayed (tWTR) = 21 (+4)
Memset Version 3.5
@memset generally. for me its a blessing from teh sky :D helps me a lot :) big up for the author ;) keep it coming ;)
:lol: Amen to that :D:up:Quote:
@memset generally. for me its a blessing from teh sky helps me a lot big up for the author keep it coming
memset is awesome :D
it helps me to go below the 4-3-3-3 Bios set mark to 4-2-2-1 1m stable at 1142mhz ddr2 :D
http://www.systemshock.co.za/forums/...=post&id=12488
Memset Rules! Definately eternally grateful to FELIX for such an awesome program!!
Nice timings vivi!!Quote:
Originally Posted by Vivi2
A bit late, but... you cannot change CAS Latency ( tCL ) in real-time on most Intel chipsets due to chipset design limitations.Quote:
Originally Posted by The Nemesis
I meet a problem with 3.5 Memset: It doesn't read memory frequency correctly, 100Mhz too high. Is there anything I could do too fix this ? Or do I have to deal with like this ?
CPU-Z 1,45 does read correctly, but 1,46 version shows the same error.
Mobo: X48 Evolution
Ram: Cell Shock 1800 8-7-6-21@1,9vdimm
OS: Vista and XPpro 32.
Would a Register Dump from Cpu-z help ? Thanks
...yes, you can send a register dump at memset@hotmail.fr.
What is the memory ratio in bios? On XP or Vista?
Strange that cpuz 1.45 read it correctly, and not 1.46...
I have an interesting question for you.Quote:
Originally Posted by FELIX
I have a dual socket SM X7DWA-N MB w/ 2-E5450 Harpertowns in it.
Memory is Kingston HyperX DDR2-800FBDimms 5-5-5-19
Default is 1.8v to the memory.
Acording to Kingston with 2.0v the memory will do CAS 4-4-4-12
If I can work out a vdimm mod on the board, how to reset the spd to boot at the cas4 settings.
No adjustments in bios available.
The only board that takes these sticks that has vdimm voltage adjustments in the bios is the Skulltrail and maybe the Asus Z7S/
Any thoughts?
Thanks
If you have no timings adjustement in bios, the only
way will be to change your spd table with a soft like SPDTool, but it's risky...
Here is the ratio shown in both vista32 and xp32, the one chosen in BIOS is readed correctly by cpu-z 1.45 -> 2/3.Quote:
Originally Posted by FELIX
http://images4.hiboox.com/images/280...9cf1bc5b43.jpg http://images4.hiboox.com/images/280...e163560fd8.jpg
I send the Dumps asap.
Thanks for the info..The 4-1 gig sticks cost me $280.00 so yes, I don't want to watch them go POOF in the night:DQuote:
Originally Posted by FELIX
Any new versions ready for testing yet?
http://images4.hiboox.com/images/320...b35dd76300.jpg
I still meet issues on ram frequency readings. It happens only when I set great ram speeds it seems.
MemSet v:3.5.5 beta
-Add support for Intel G35 chipsets.
-Add support for Intel PM45/GM45 (Mobile) chipsets.
-Fix a bug with the Save function on Intel chipsets.
-Improve reading frequency with some Intel CPU.
Cool Thanks going to try it on my x9100 & PM45 chipset now THX :DQuote:
Originally Posted by stasio
Some memory test from OCCT released 1-Aug-2008
CUDAMemTestv0.2a
Video memory test of Nvidia cards, I suppose....;)Quote:
Originally Posted by stasio
Felix your program is awesome Thanks :up:
Have used it since you began work on it. Just recently bought a new notebook and am trying real hard to find the memory speed but not having much luck here.. take a look at this!
http://img143.imageshack.us/img143/1...betazs3.th.jpg
Felix great work for the community, i hope you continue supporting us along
with future upcoming chipsets and faster ram chips. tweaking our mems this
way, is just awsome. :up:
unfortunately i'm having some issues to stabilize a E8600 at 4.7GHz with DDR3.
can't wait to use it here!
What is your memory frequency?Quote:
Originally Posted by ihjones
Could you send a register dump (with cpu-z) at memset@hotmail.fr ...
Done... :)Quote:
Originally Posted by FELIX
=> ihjones: could you try this version: memset357beta and tell me the result...
Cool THANKS Felix :clap:Quote:
Originally Posted by FELIX
http://img381.imageshack.us/img381/1...set2mu1.th.jpg
The program reads the values correctly for me, but as soon as I change anything and hit Apply, the system simply freezes and I have to hit the Reset switch. Any ideas?
http://img56.imageshack.us/img56/5571/memsetwm3.gif
System:
Asus M2A-MX mobo (690V chipset), Phenom X4 9650, 2x1GB Corsair XMS2, Radeon HD4850 512MB, M-Audio Delta1010LT PCI audio card, Vista SP1.
which chipset does your board have?
=>JimmiG: if you change nothing and click on "Apply" , is the system freeze too?
Could you run this soft, choose "Bus:0 Dev:24 Fct:2" in the second combo,
click on the "pci.txt" button and show the result here or send it at memset@hotmail.fr
Hi everyone, as I'm new on the forum, :)
I know MemSet since I used it on my old pc (mobo IS7, P4 3ghz@3.2) on which I tried to use 3 gb (3 sticks) sdram ...
But today, I woul want to use it on my notebook C90S ASUS. I have 2 gb DDR2, 5.5.5.15.
With Memset I've already got 5.4.4.12, but I can't change CAS (CAS#latency tCL). :(
Does anybody know why ? And how to fix ? :help:
Thanks in advance. :)
Bonjour à tous, je suis nouveau dans ce forum,
Je connais Memset depuis que je l'avais utilisé sur mon acien pc (mobo IS7, P4 3ghz@3.2) sur lequel j'essayais d'utiliser 3 GB de SDRAM, avec une barette différente sur les 3.
Mais aujourd'hui, je l'ai installé sur mon portable ASUS C90S. J'ai 2 Gb DDR2, 5.5.5.15.
J'ai obtenu avec Memset 5.4.4.12, but je ne peux pas modifier CAS (CAS#latency tCL). :(
Qq'un sait-il pourquoi ? Et comment corriger ce défaut ? :help:
Par avance, merci. :)
Es ist nicht möglich, sich #Cas unter Windows auf DDR2 zu verändern. :D
Thanks.
:(
Salut!
Can you add support of the nvidia nforce 630i chipset to your software?
Thx.
Could you send a register dump (with cpu-z) at memset@hotmail.fr
FELIX, do you know if its possible to modify certain Data Strobe timing values in the MCHBAR registers, such as tDQS, tDDQ, tDQSS, tRPRE, tRPST, tDS, tDH and so on. Data strobe timings, Read pre and postambles, and other values stored in SPD which from my undersdtanding if they exist in SPD then registers with RW flags must exist in the MCHBAR to change or initially set their values.
These timings are not documented in the Intel documentation,
you can see this datasheet at page 131 and higher for available timings.
All ready got a handful of chipset datasheets but thanks for the link anyhow! Some of those timings should actually exist in the MCHBAR registers, but I suppose your guess is as good as mine as to where. I've spent the last 8hrs disassembling the 1B bios core module from a Rampage Extreme bios, still at least another 3 or 4 hours work left on the disassembly. Hopefully once I've disassembled it completely, then disassembled the 21 language US module it'll be enough to figure out which assembly functions in the bios point at which strings in the multi-language module to work out what does what. Otherwise if that fails I'll have to go through Intel datasheets and work them out from the address'. That might be actually quicker, since it'd take me less time to search for the addresses and label the functions.
Hi!
I already send you CPU-Z dump. Did you got it?
Just installed 3.5 and following reboot, MCHBAR shows locked and can't find way to unlock. All timings shown are correct.
Uninstalled/reinstalled twice; and have tried closing with "Exit" and with "X", all to no avail.
No other programs, such as CPU-z open.
Thanks
abit has it set that way; locked tighter than fort knox safe...memset is locked out from adjusting the MCH registers on the Pro board.Quote:
Originally Posted by zalophus
Thanks Ace-a-Rule for quick reply. Interestingly, I found version 3.4 on one of my older drives, cut and pasted it onto my new drive, and it works just fine. So it looks like it may be more of a 3.5 version issue than Abit...?Quote:
Originally Posted by Ace-a-Rue
FelixQuote:
Originally Posted by FELIX
Thanks for the link, I have been looking for that info myself.
I got it a few day ago, thank. :)Quote:
Originally Posted by MadOverTolik
I add support for 630i and 790i ftw in this version: memset358beta.exe
Let me know if you find some problem...
Felix, is it possible you will ever make a portable version of MemSet? I love the program, but it's one of the few tweak tools I use that needs installation, almost everything else is portable.
memset 358beta works great on 790ftw!
thanks for your time and effort.
excellent Felix, looks to be working great with the EVGA 790i FTW Digital. i was just coming to ask what you needed from me to support it...but you are way ahead of me :up:Quote:
Originally Posted by FELIX
Hello all.
This is my first post on the forums, though I've been haunting this place for years. I am getting the same error message as Leotonch on page 36:http://www.xtremesystems.org/forums/...=92190&page=36
It is identical except the EaccessViolation is Memset.exe at 0005752B.
Access violation at address 004752B in 'Memset.exe'. Read of address 00000474.
My specs:
MSI P35 Platinum bios v 1.9
E8600 cpu
OCZ Flex PC2-9600
Windows XP 32 Bit Service Pack 3
I have tried earlier versions of memtest to the latest I see here. None are working. With my QX9650 with Service pack 2, it worked. Thank you all for the knowledge you all share, and thank you Felix for such a great work.
Could you run this soft , choose DMI-BIOS in the second combo,
click on dmibios.txt and send the dump at memset@hotmail.fr
Felix, I installed the software as requested and rebooted. It gave me an "Eaccess" error when I attempt to launch the exe. So you know, I have the Windows "Data Execution Prevention" feature disabled.
Could you test this memset version and tell me the result...
and send a register dump (with cpu-z->last table->register.txt) at memset@hotmail.fr
Not that I think it matters much, but MemSet 3.5 says my memory is DDR3, even though it is DDR2...
use latest beta 3.5.3 and above IIRC ;)Quote:
Originally Posted by daath
http://fileshosts.com/intel/Gigabyte...s50ps/cpuz.png
...and 3.5.8 ?
I made a little change in this version for read DDR type.
Any chance you can answer my question about a portable version, Felix?
What do you mean when you write "a portable version" ? :confused:
Portable = no installation needed.Quote:
Originally Posted by FELIX
Portable apps can be run from anywhere on a drive, or from a USB stick, etc. A portable version of MemSet would be great.