Fiery

Thank you, we'll fix the issue in the next AIDA64 beta update due in a few days from now. Regards, Fiery

We usually recommend several hours, and 3 hours is a good start. Regards, Fiery

AIDA64 does not delete or remove any log files. Regards, Fiery

Samsung 840 Evo and 850 Evo SSDs indeed support temperature measurement

AFAIK Vertex 460 SSDs are not capable of monitoring their own temperature. Note that many SSD drives have no temperature sensor, so this is not an uncommon issue. Regards, Fiery

Thank you, but it's not easy to accomplish everything you guys come up with We're trying to our best though

We'll implement the requested new hardware monitor item in the next AIDA64 beta update due in a few days from now.

We'll We'll fix that issue in the next AIDA64 beta update due in a few days from now.

Thank you for the feedback. We'll do that in the next AIDA64 beta update due in a few days from now

That feature can be used to write an entry to a SysLog server's log. http://en.wikipedia.org/wiki/Syslog Regards, Fiery

Thank you for the data. Your UPS doesn't seem to support the standard temperature readout report, but maybe it reports the temperature via an APC-specific report or such. Can you please check the temperature, reported by the APC software, and create a new Battery Dump, and copy-paste the dump here and let me know the temperature that I should look for in the dump? Thanks, Fiery

Thank you. We've implemented advanced support for UAS drives in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery Dump. Copy-paste the full results into this topic. Thanks, Fiery

0x5A = 90 Celsius. Regards, Fiery

Under Windows it's not possible to gain direct access to hardware without administrator privileges. Without administrator rights you cannot read GPU information, chipset information, SPD memory module details, sensor readings, etc. It's a Windows limitation that AIDA64 has to obey. There's no way to fix it. Regards, Fiery

Here's the new AIDA64 Extreme beta update that implements the 3 new media items for the hardware monitoring module: http://www.aida64.com/downloads/latesta64xebeta It only supports BSPlayer and Winamp at this time. We've tried our best to implement support for Windows Media Player too, but it's quite a bit more complicated than we've assumed. We'll keep trying though Let me know how it works.

Great tip, thank you! I should have tried that myself I did manage to install the DirectOutput SDK, but it has no documentation at all, just 2 DLLs and an EXE file. Quite tough to go further from here. We'll contact Mad Catz and ask whether we can access the documentation for the SDK.

I'd be happy to check out the SDK, but those drivers for the X52Pro do not seem to install at all without the actual hardware to be connected to the PC Do you know of a direct download link to the SDK alone, without the drivers and other buzz?

I'm not sure what do you mean exactly What do you do, and where does the progress bar appear? Maybe you can post a screen shot to illustrate the issue?

I'm afraid we don't have an idea about what could cause the issues on your system. We've done quite a few test runs on our R9 290X card trying to reproduce the lockup, but it worked flawlessly. It may be a combination of Windows version, Catalyst version and other factors. Are you using Win8.1 64-bit? What version of Catalyst do you have installed? Maybe if we use the exact same Windows version + kernel type and the same Catalyst release, we can reproduce the issue on our test hardware.

AI Suite II is not properly synchronized with our software, even though many of us already asked Asus to go down that route. Asus simply refuses to implement the industry standard synchronization methods that AIDA64, CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, SIV, Speedfan (etc) already use. For that reason, we cannot fix the issue from our software As for CPU-Z, that software should be synchronized with AIDA64 and other software, but maybe it doesn't use the SMBus synchronization mutex properly. If it's possible, please notify the authors of CPU-Z about this potential issue. We are pretty certain AIDA64 has that mutex properly implemented, so once again, the issue is not with our software. Regards, Fiery

Thank you for the feedback and the test runs. I'm afraid we cannot find the right register to use to measure pump power We have some candidates, but the numbers do not add up for some reason. Maybe the pump power is not scaled in a linear fashion or so. We'll keep looking, but at this time I cannot promise anything.

Such issues are usually caused by a security software that prevents AIDA64 from being installed as an auto-start process. Another problem may be that something has been mixed up in the Windows Task Scheduler. Try to close AIDA64, remove its startup entry from the Task Scheduler, start AIDA64 again, and see if it helps. Regards, Fiery

You don't have to install anything else. All you have to do is build your own custom LCD layout in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items. In case the text is too small, you can adjust the font size easily.

We do have plans for such a feature for the Android app. Meanwhile, you may want to check out the RemoteSensor feature that can already be used for such purposes: http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/ Regards, Fiery