Praz, 10x for good explanation.Quote:
Originally Posted by Praz
Praz, 10x for good explanation.Quote:
Originally Posted by Praz
A64Info is evolving into a must have program. It is now to the point of replacing most other single purpose programs. I think at times we fail to convey how appreciative we are of your hard work. But please, reconsider removing the thermal sensor information. Those that believe the thermal diode is more accurate can just ignore it. Or how about the possibility of including the diode along with the sensor reading.Quote:
Originally Posted by lukija
Thanks
yeah..thanx too from me because this is an excellent tool !
Regarding the thermal sensor(s): Interesting info there, i couldnt get any clear information in the whitepapers regarding what's the preferred way to read temps...but praz is definitly right. However, i think that the majority of end-users use the thermal diode/mbm/speedfan method.
lukija, did you get the FID/VID working now ?
I'd like to extend my thanks for all your work on the program.
Definately a must have for me.
Wonderful to see you and Vitaliy sharing information.
I have to agree 100%.Quote:
Originally Posted by Praz
The readings obtained are from two different sources using different methods.
While they may be very close at Idle there can be a large difference under load.
And while the accuracy of either method can be questioned, please leave it in the program as it is an extremely useful tool.
I find MBM5 almost a necessity due to it's configurability and use in/with other programs (WebTemp, LCDC, LCD Smartie, MBM5 log, etc). The ability to calibrate/compensate voltages and temps is a nice touch for me. But there are many who don't like the program or bother setting it up. To each his own.
ITE SmartGuardian, Speedfan, Everest, and NextSensor (all except the latest Everest are FREE) are also great programs. While I prefer VVJ's NextSensor program, others may prefer the GUI or featureset of another program.
As new boards are introduced with many using newly introduced sensors (ITE IT8716F on the AMD M2 boards instead of the older IT8712F) MBM5 may not be able to be used and using the CPU's internal sensor (A64 Info, Core Temp, NextSensor, Everest) may be the only way. Vista (whether you like it or not) will become mainstream over the next 12-24 months and those using the 64-bit Final version may find themselves UNABLE to use any of the programs that DO NOT have a "signed driver".
KEEP THE THERMAL SENSOR INFO IN
My apologies if I have gone too far off topic but for those that prefer Johnny Lee's SP2004 to Prime 95 he is working on a new Beta for 64-bit based on P64v2414 that now dispalys the sensor info from MBM5.
your doing Great Work lukija, keep it coming
some pics in Vista x64
http://img109.imageshack.us/img109/4...compxc0.th.jpg
http://img353.imageshack.us/img353/8...ax64rf0.th.jpg
http://img71.imageshack.us/img71/583...4x64xg8.th.jpg
Brilliant this software! I added it on my site :)
>> http://www.nokytech.net/telechargement-a64_info-92.html
Great job once again lukija :toast: I also will encourage you to leave in the temp monitor, very nice addition.
Can anyone tell me what that "disable jitter" does?
And to the author, A64info .61 reports that my cpu voltage is 1.425v while my vcore is 1.525v in the bios. I run a winchester 3200+ @ 2.5GHz, for reference. Of course, I understand that this is beta.
*bump*
anyone?:stick:
it acquired me some time to find this info for you :
'When set the DDR compensation circuit will not change values unless the change is more than one step from the current value. This bit should be set
for all revision E and later processors'
so, if u have rev.E processor, like me, don't touch it, live it checked.
When I click this link, I get 0.61?Quote:
Originally Posted by lukija
Cheers! This seems like a great tool, but i cannot get it to work properly on one of my computers, both 0.50 and 0.61beta tested. Specs:
DFI NF4 Ultra -D
Windows 2000 sp4
AMD 64 3000+ (Venice E4) @314x9
The 0.50 shows completely wrong info, while i cannot even get the 0.61beta to open, it simply says "error loading driver".
http://www.xtremesystems.org/forums/...1&d=1157218068
In order for the driver to load your user account must have administrative priviledges. Also check that your local or global security policy does not prevent loading and unloading device drivers. If that doesn't help and you can't or won't use Windows XP I guess you are out of luck.Quote:
Originally Posted by Frodin
http://www.forumdeluxx.de/forum/atta...5&d=1156337670Quote:
Originally Posted by lukija
http://www.forumdeluxx.de/forum/atta...1&d=1156417740
thx for v0.61 lukija. it works great so far :toast: :clap:
Thank you so much for finding that info.Quote:
Originally Posted by emaniac
But I am not very good at this thing. I have a 3200+winchester (rev DH8-D0). So, can I or can I not check the 'disable jitter' checkbox? It seems to affect stability only AFA I can tell, and since I run stable now I don't think it's required.
welcome.
then leave it as is. lukija knows better then me. ask him if must know for sure.
for those who have a very restricted motherboard (unable to set vcore in bios), is it possible to make this program such that it can set the vcore higher than the "maximum" found, which i know is definately not the maximum the cpu can do.
despite that i think bugs are the same as xpsp2?
http://img145.imageshack.us/img145/7...tledkp5.th.jpg
0.6 won't even work says error loading driver.
and i'm admin .
Just wanted to say "thanks" - for all the hard work and constant innovation on this program. It also takes time and effort to read forums like this and respond to ongoing questions and problems, and for that, I applaud you.
Also wanted to say that, like many others, this program is a "must-have" for me on my Neo2 board... With a lack of RAM timing options available in the BIOS, and the inability to boot with certain (otherwise stable) dividers, this program now loads everytime I run windows.
...And as soon as you enable FSB overclocking in the settings window, I can get rid of Clockgen!
Peace
P.S. Also, as a suggestion - how about adding a startup 'bypass' key which allows one to bypass startup settings like the nVidia overclocking utility? Would make recovering from failed settings a bit easier (hasn't happened yet, but who knows?).
Eeek, sorry, dbl post :(
Any good ??? hmmmmm
are the volts for cpu maxed at 1.55 for everyone? casue in bios i can do 1.8 max.. so please tell me whats up...
Great program, I've just downloaded it.
I noticed however that I can choose any multiplier up to 25x on my X2 3800+, just before I try it to find it won't work, I won't destroy anything will I?
Everything else seems to be working perfectly, cool prog!
Edit: Don't worry, I just tried, to learn it just resets to the largest multiplier possible.
On another note, is the voltage change pretty safe? Any reports of problems with it?
It maxes at 1.55v here also and my BIOS goes quite a bit higher, but with DFI, I can also set VID Special -- a value that multiplies VID to get the actual Vcore. I have mine set for 144.4 (14.4% increase) so I can get quite a bit more than the 1.61 that I run when at my max OC. I've read that other MBs can be set to add an offset (200mv).Quote:
Originally Posted by JamesBong420