Fiery

I'm sorry for the delays. I've just sent you a private message about this issue.

Thank you for the feedback

I'm afraid AIDA64 cannot expose or export SensorPanel images in any ways.

Unfortunately AIDA64 OSD Panel and SensorPanel cannot be displayed while running a full-screen 3D application. They are still running and updated on your Windows Desktop while e.g. playing a game, you just cannot see them -- same way that you cannot see the Windows Desktop while playing a game.

Yes, we do have plans about such a feature for AIDA64. However, since the Modern UI applications are quite limited in their communication with other processes and drivers, it's not easy to come up with a proper live tile sensor application. We'll work on it in 2013 Regards, Fiery

We've fixed the drive space update issues in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...50x4gbkpyq1hzip

Thank you for the bug report. Please note that 1.65.1.1000 is the version number of Malwarebytes Anti-Malware that you have installed. We've changed the product name detection from simply "Anti-Malware" to "Malwarebytes Anti-Malware" to clarify that. We've also added firewall software support for Emsisoft Online Armor, and anti-virus software support for Emsisoft Anti-Malware. With Anti-Malware the virus database date indicates the database date for the BitDefender Engine. The mentioned changes will all be introduced in the next AIDA64 beta release. Regards, Fiery

An external DLL would be something we'd prefer to avoid if possible. We may be able to add the requested feature in a way that would require your software to write and update a string Registry value under the HKEY_CURRENT_USER\Software\FinalWire\AIDA64 path. AIDA64 then would pick up the value from the Registry, and place it on the OSD Panel (or SensorPanel, Desktop Gadget, log file, etc) Would it be suitable for you? Thanks, Fiery

I'm sorry, but currently we have no plans to add such a feature to the AIDA64 OSD Panel. We rather focus on the more advanced SensorPanel, although we wouldn't add slide-in/slide-out to that module either. However, in case more user requests arrive on the same feature, then we may add it to our development roadmap. Regards, Fiery

We've already discussed Corsair Link matters with our friends at Corsair, but their latest status on it is that they don't want to open up the Corsair Link specifications to let 3rd party developers read values from Corsair Link capable devices Let's hope they will change their mind soon. Regards, Fiery

Thank you for the clarification Let's hope they will eventually decide to roll out a public SDK.

It's still under development. We wanted to roll it out before xmas, but it wasn't perfect, so we had to postpone it until it gets more mature and provide more stable results. Let's hope we can release the new memory benchmarks sometime in Q1 2013.

Without a SDK there's not much we can do... If you want to put a fire under Cyborg, to push them into releasing a SDK, please feel free to do so. But it's not our responsibility to do that, since we are not customers of them.

Please contact me in email to discuss those.

I'm afraid we have no SDK form of AIDA64, so we cannot provide you with an AIDA64 detection engine to be implemented in your software. For further details (e.g. a potential OEM relationship), feel free to contact me directly at: tamas.miklos AT finalwire.com (replace AT with @)

Can you please post a few more scores, e.g. CPU Queen and FPU Julia? I wonder whether CPU and FPU benchmarks also indicate low performance or not.

AIDA64 can only use the fonts that Windows has installed. If you miss a font, then please try to install it via Windows font services. Regards, Fiery

Your other topic was placed in the right forum, and I've replied there. Please avoid posting the same issue into multiple topics. This topic is closed.

A couple of issues may cause such consistently low benchmark results: 1) CPU clock discrepancies. E.g. when the CPU is running all the time at LFM (Low Frequency Mode, e.g. 600 or 800 MHz) instead of full clocks. I suppose that's not the case, since CPU core clock seems to reflect values matching HFM (High Frequency Mode). 2) CPU throttling. In other words, your system may be overheating, and the processor is slowing (throttling) itself down to prevent fatal damages. You can check that by launching the AIDA64 System Stability Test (main menu / Tools / System Stability Test). Check if the bottom throttling graph shows any activity (any values other than 0%). If there's a throttling activity even at idle, the overheating is quite serious. If you don't see throttling at idle, then try to enable only the FPU subtest (untick the rest of the tests), and press the Start button to initiate the stress test. Wait for a few minutes, and check if the throttling graph shows any activity. If it does, then your system is overheating under heavy load. Either way, if there's any throttling occuring ever, it is a problem that you need to address by cleaning the exhaust ports of your notebook. 3) Background processes. There may be other software or service running in the background that uses a lot of CPU cycles, and that impacts benchmark results. Try to close all background software, especially ones that may also be monitoring your CPU or system. Regards, Fiery

PCH is the chipset component of your motherboard. It tends to run a bit hotter than processors, especially at idle. Anything above 80 Celsius is considered high for chipsets, and beyond 90 Celsius is considered critical. Regards, Fiery

I'm afraid AIDA64 SensorPanel and OSD Panel are not usable while you're running a full-screen application or a 3D game.

We've already got the SDK -- check my previous post above I'm not sure what you mean. AIDA64 already measures all of those, except for the FPS counter. You can configure graphs with AIDA64 SensorPanel to display all those information on a single SensorPanel.

The slow startup of AIDA64 is caused by Windows itself that has difficulties loading the dynamic kernel driver of AIDA64 on some configurations. Even if we stripped down AIDA64 to an even lighter software (which we will not do), Windows would still load the very light sized AIDA64 kernel driver (less than 30 KiloBytes) rather slowly. All of the Windows Gadgets that come built-in with Windows Vista and Windows 7 do not use a kernel driver, hence their loading at Windows startup could be swift. BTW, before you call our software a bloatware, make sure to check what size is its files are (combined), and what memory footprint does AIDA64 have. Both values (typically both are under 30 MegaBytes) are fractions of a modern 3D game and several of the software you have installed on your Windows system. Regards, Fiery

Right-click on the SensorPanel --> SensorPanel Manager, and push the Import button on the top of the window to import a .sensorpanel file. Regards, Fiery

TMU count is calculated from the shader count, so it will also be fixed