thank you very much for informing me
Printable View
thank you very much for informing me
FELIX
Please add support ATI Radeon Xpress 200
I need datasheets for do that and ATI don't allow access to these infos.
can you add support for vista x64 ?
Vista64 require signed driver for work, and the driver I use with
memset (TVicPort) is unsigned for now; it's the raison that Memset
work on Vista32 and not Vista64.Perhaps at next...
when ? :/ .....
...now: memset
Works under vista x64 !!!!
thank you so much
je te remercie felix
Hey Felix,
Thanks for a great app!
In Vista 32bit, I have to scale DPI to make the text readable on my 32" LCD TV. If I try and launch it with the Vista scaling disabled, I get a
"You must use normal size (96ppp) to use this software," error.
A fix possible?
I dunno if this is a bug or not. & it defiantly makes no diffrence to me.
But on my Laptop which has a 855PM chipset the speed of the ram is constantly changing in memset. It goes right down to about 4mhz when doing nothing on comp & when running mbench I've seen it say 2201mhz & it generally sits between 10 & 100 :s. Ive locked the CPU to 2Ghz & the FSB to 100 using NHC. & CPU-Z dun seems to pick up the speed variation.
Also size is says 512 when i actually have 1526MB of ram so thats odd as well :S
Thank you..
Thanks for the wonderfull program Felix....
Im having problems with memset where sometimes the settings will be all blank except the last 4 values which reads 15-15-15-15.... after that even if I reboot, memset will not function anymore...... anything I can do?
I got the same issue...also on the Commando. ;)
...otherwize you get that:Quote:
Originally Posted by nordicpc
http://www.xtremesystems.org/forums/...d=11603620 29
and, because memset use differents windows size, make that the soft work with
differents ppp is a hard work with C++-builder (more simple with Visual C++) :
memset is made with C++-builder. :)
->BenArcher: I send you an MP.
->luied & Gautam: Read post #234 on this thread, and don't use the save function if you have this problem, I try to fix that soon...
I think theres a prob in x64 vista version ?:S
I can only run it with compatibility mode for XP or it says ''not for vista 64''
And a second prob is that it reports wrong frequency.
Eg I have 450mhz and it reports 600(sometimes goes up..604-608 and then back to 600 :S)
Can you make it support Abit Fatal1ty F-I90HD?
It uses ATi RX1250 chipset:
http://www2.abit.com.tw/page/no/moth...775&DEFTITLE=Y
->cmos.gr: Try with this version: memset
->BulldogPO: I need datasheet for do that and ATI don't allow access to these infos.
Quote:
Originally Posted by FELIX
Checked but same problems...
First : Warning : not for vista 64
compatibility for Xp sp2
Then : Works but 600-608 mhz dram.;)
Thanks for the effort on such a sweet proggy Felix. I just picked up a DFI Infinity 965-S and having an issue with running the new version. I get an error that says "the driver TVicPort can not be found". Any ideas?
that's not a fault of the dfi board. you using vista?
No xp. Tried reinstalling program, works once or twice but error keeps returning.
XP 32 or 64 bits?
Is your OS installed on C:\ or D:\?
XP 32bit. C:\ HD location
Hey FELIX, I don't know if it has been mentioned, I am using the old v3.2 and closing via windows (X or taskbar) works good, but when i press the exit button in the app it takes longer to shutdown and when I run memset again the values are missing/wrong, which requires a restart to fix.
Sorry if it has been mentioned before :)
Read post #234 on this thread, and don't use the save function if you have this problem...
im getting the same problem as Peakr with my dfi, same error code
im using win xp,
thanks for any help
DFI 965-S same problem as Peakr.
Peakr, Praz, MADMAX22: Have you the same problem with 3.0 or 3.1 version??
Not sure, dunno where to find older versions. Happy to try them out though. Seems to be a prob with this mobo it seems. Tried re-installing many times, deleting reg entries and files. Nothing seems to work. The program works once or twice then after a reboot I get the error. Hope this helps.
3.0 seems to work fine by itself. Once 3.2 reports that TVicPort cannot be found, 3.0 will say the same until 3.2 is uninstalled.
OK, probably a problem with 3.2 version...
I try to fix it soon.
Thanks FELIX
thanks felix, and does anyone have a link to 3.0 version
Here: memset3.0
only for xp32.
thanks, yeah fully removed 3.2 and 3.0 works now with my dfi
->cmos.gr,Peakr, Praz, MADMAX22,you can try this version: memset
I'll run it as soon as I get home tonight and let you know the results.Quote:
Originally Posted by FELIX
Thanks
John
I just downloaded the latest version and tested it on the QuadGT. For some reason I cannot change CAS. I get the dropdown meny but whatever I choose the timing set in BIOS get selected.
You can't change tCL ( CAS Latency ) in real-time.Quote:
Originally Posted by blossa
Sometimes the answer is very simple. :rolleyes: Thank you very much for that! :toast:Quote:
Originally Posted by BenchZowner
Thanks again Felix. Off to work now but I'll test it later on.
Edit: Ok new version working fine. Awesome job!
FELIX
I have tested the new version on the 965-S and the QuadGT. Seems to work fine on both boards.
Thanks
John
Thanks for that last version FELIX, working good :toast:
Thanks for new one.
hey Felix it would be REALLY NICE if you could add the new P35 chipset to your software support..............need it badly for RAM tweaking here :D
Support for P35 chipsets coming soon, but I need the datasheet for do that,
and Intel don't provide it for now... probably in June.
if you need a beta tester, let me know :D
I'm realy need memset for my P35 ! Wating, FELIX ! $-)
Hello guys,
Having problems with memset and vista32 + DFI 965-S. Once I start the program it tell me that I am using vista 64 bit...
Does anyone know were should I find the version that works?
Thanks
Try with this version: memset
Contact me by pm :up:Quote:
Originally Posted by FELIX
Any luck on the P35 memset that may work on the Asus PK5 dlx yet?
....and or on Gigabyte DQ6 and similar one?Quote:
Originally Posted by xgman
I am available to test any upgrade, I own a DQ6 with latest bios (F4).
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 :)
OK, Please see this picture:confused: ,PLEASE !Quote:
Originally Posted by GoriLLakoS
what's the question???? help with what?? looks like buffalo d9gkx
Question is,Quote:
Originally Posted by ziddey
@MemSet, Display 751.7Mhz
&
@CPU-Z, Display 644.3Mhz
Question is WHY?????, PLEASE:confused:
Nice to hear that. I'm waiting for latest version that support my Asus P5K Deluxe :up:Quote:
Originally Posted by FELIX
nothing to worry about. trust cpuz.Quote:
Originally Posted by caesarean
you lowered your multiplier from 7 to 6. Here's how memset made the calculation:
default / actual x fsb / divider.
so in your case, 7 / 6 x 429 / 2 x 3 = 750
dont worry about it
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.
...I'm not surprised of that for tCL, it's already the same for P965 chipsets.Quote:
Originally Posted by The Stilt
But for tRTC and others, it's a bad news... perhaps more infos in datasheets.
Yes, tCL is not a surprise, but everything else is "locked" too.Quote:
Originally Posted by FELIX
I doubt the datasheet will make any difference, since I have already talked with one of the chipset architects who was working on Bearlake.
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:
Quote:
Originally Posted by The Stilt
ouch!!! I was counting on Memset to come to the rescue here. :(
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:
Not such a kick in the nuts after all then. :)
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.Quote:
Originally Posted by The Stilt
oh :banana::banana::banana::banana:Quote:
Originally Posted by The Stilt
looks like i'll have to buy a Gigashyte board again :D
i did lol asus slackin offQuote:
Originally Posted by dinos22
It's very strange, an address or an other is not very important,Quote:
Originally Posted by The Stilt
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 ;)
Got it working on Asus too ;)
Weird stuff I must say :D
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.
Thanks for your time and effort guys....... :) :up:
IF sometime FELIX decide to accept donations for his lovely work, I'll be glad to donate via PayPal..... ;) :)
Not easy to do. :confused:Quote:
Originally Posted by The Stilt
When you say "null data" it's 0x0000 or 0xFFFF?Quote:
Originally Posted by The Stilt
You can't write a new address in this register,just write 1 at bit 0 for unlock mchbar.Quote:
Originally Posted by The Stilt
I hope get it tomorrow, official release for P35 is the 4 june :)Quote:
Originally Posted by The Stilt
Very thank for this suggestion hipro5, ;)Quote:
Originally Posted by 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 :)
OMG dude i almost had to buy gigashyte board again :ROTF:Quote:
Originally Posted by The Stilt
thanks very much
FELIX, email sent.
It is up to you now :D
Now itīs whiskey time :slobber:
Keep up the good work Felix :up: Saving people from buying things they don't really want is a community service :D 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 :ROTF: :eek: :rofl:
Keep up the good work dude for the hardest of the hard core :up:
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 :p:Quote:
Originally Posted by dinos22
tell me about it :DQuote:
Originally Posted by OldGuy
...just got it: great work! :)Quote:
Originally Posted by The Stilt
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 :( )
Thanks to Felix, The Stilt and everybody.......my Gigabyte DQ6 is ready to test new version of memset :)
when i close memset 3.2 all timing readings are wiped out at least with xp64.
could you guys help ?
I know you will find a way Felix. :)
Either check or uncheck 'lock mchbar.' It's at the bottom of the memset screen.Quote:
Originally Posted by BAR*B*Q
Is Memset working with P35 avaliable now ??Quote:
Originally Posted by FELIX
Not again, coming soon...
aah... thx mate. :) i had to unlock it.Quote:
Originally Posted by Hutch
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 :D