Fiery

Thank you

Even if it is open source, we are not in a position to modify a software made by another vendor. We've got a reply from Koolance meanwhile. It seems they're open to discussions in order to fix this issue. We'll come up with a way that based on the existing hardware, but by an updated Koolance software and an updated AIDA64 version it will be possible to read values in AIDA64 even when Koolance's own software is running. I'm not sure about the time frame, but judging by the quick and professional reply we've got from Koolance, I'm sure it won't take forever to get there. I'll post updates about this matter in this topic.

Thank you for your kind words As for Build 1137 vs 1130, we haven't changed anything, so try to restart your computer, and the SPD info should be back to normal

Thanks What CPU and motherboard do you have? I suspect it's going to be a bug related to Clarkdale/Arrandale core processors.

Can you please try to close that to see if it causes a collision with AIDA64, or we need to look elsewhere?

We'll offer upgrade prices at 70% of the new license prices. So you'll save 30% compared to buying a new license. Regards, Fiery

Thank you, that narrows it down to CPU clock measurement. Do you have any other software running in the background that may also monitor & measure CPU clock speed?

We've contacted Koolance to find out whether they would be interested in teaming up with us in order to come up with a solution so multiple software can access the TMS-200 device simultaneously. I'll let you know in this topic about their response.

Core i5 661 uses a max. non-turbo multiplier of 25x (25 x 133.33 MHz BCLK = 3333 MHz core clock). With Turbo Boost it can raise the core multiplier up to as high as 27x. So when AIDA64 reads 26x, it is absolutely normal for your CPU. Thank you for the feedback, please let me know if AIDA64 locks up when you have the Computer / Overclock page opened and updating.

There's no single standard on DES monitoring, and Gigabyte never published DES specifications, programming documentation or SDK. We've tried to add DES support via Gigabyte's own DES software, but it didn't work out as well as we hoped. Regards, Fiery

1) Do you overclock your system? 2) Do you have any external hard disk drives connected? If yes, then USB or eSATA or FireWire? 3) Does a lockup occur when you have the Sensor page showing and updating? 4) Please copy-paste the full content of the Sensor page into this topic. Thanks, Fiery

In case it didn't freeze right after you opened AIDA64 CPUID window, then I'm not at all convinced that the freeze is in connection with AIDA64, or that it's entirely AIDA64's fault But please let us know more about your system, e.g. CPU type, motherboard model, and whether you can experience similar lockups when you have e.g. the OSD Panel opened.

Instead of tweaking our Sidebar Gadget or making the current OSD Panel feature more flexible, we plan to introduce a brand new feature that will effectively replace both those features. The new feature will implement a much greater flexibility about items placement, and a visually more appealing look & feel (gauges, bars, configurable colour alerts, etc).

That option switches not only the tool bar icons, but also all the rest of the icons back to the old style, so it may or may not be suitable for Tistou We haven't yet finalized the tool bar icons, and we'd be happy to hear your feedbacks on the new tool bar icons. It seems Tistou would prefer the old one, but how about others?

Thank you for the feedback

Thank you for the suggestion, but due to a long line of feature requests piling up on our "desks", well only be able to start working on perfmon support as early as January I'll keep you posted in this topic.

Other tools include AIDA64, of course But that feature generally requires a platform that supports such readout, and AFAIK LGA1366 platforms do not support that due to lack of hardware implementation in ICH10 south bridge.

Please try to enable the option "Use HKLM in Registry" in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar. Let me know if it helps. Thanks, Fiery

Thank you for the clarification, now I understand the problem you're facing. We'll do some test runs to reproduce the issue, and I hope I'll be able to get back to you (in this topic) with a solution next week. Thanks, Fiery

1) AIDA64 has the gadget in its distribution package. It is the file named AIDA_VSB.VSB. As soon as you enable the Sidebar feature in AIDA64 (main menu / File / Preferences / Hardware Monitoring / Vista Sidebar), then the gadget files are copied to the relevant Sidebar folder on your computer. After that, all you have to do is manually add the gadget to your Sidebar or Desktop. 2.1) It is a limitation that no Windows software can get around. You simply need to have admin rights to communicate with sensor devices. 2.3) Have you tried to run AIDA64 by right-clicking on the AIDA64.EXE file (or the AIDA64 shortcut on your Desktop) --> Run as administrator? Regards, Fiery

We're still changing icons, so Build 1123 was only a mid-term preview The motherboard icon is not an old one, and it's not related to the previous WinXP-style looks, so we kept it. We may change it soon though, to make sure that icon also features a "fresh" look.

Please let us know more abuot your system: 1) Windows variant? 32-bit or 64-bit kernel? 2) Intel storage drivers version? 3) Disk drives configuration? Any RAID arrays defined? 4) AIDA64 version and build number? Thanks, Fiery

We've managed to fix this issue. It will be included in the next stable release of AIDA64. Thanks, Fiery

Can you please check if HWMonitor is also affected by this anomaly?

Thank you for the suggestion. We'll consider this in the a future release of AIDA64.