Fiery

PSU information is only available for Gigabyte Odin PSUs. For the rest, yes, AIDA64 provides detailed information on all of those components. Regards, Fiery

Do you mean you would prefer to purchase AIDA64 on a physical media? Or that you want to copy AIDA64 to your media and use it from there as a portable software?

No, they're all unsupported. Out of those picture frames that you can pick up from a store, only Samsung SPF is supported. It is a limitation of the DPF devices, they aren't designed to handle such tasks... BTW, if you're US based, check out eBay. From time to time you can find a Samsung SPF device there for a great price.

Only Samsung SPF and AX206-based hacked firmware DPF devices can be used with AIDA64. Most DPFs do not support sending images on-the-fly (without copying them to the DPF's flash memory) over the USB connection.

Please let us know what exactly the problem is about the serial number detection. What is the expected serial number, and what does AIDA64 show? And if possible, please use English. Regards, Fiery

We haven't yet found a way to have a window like SensorPanel shown in Aero Peek

Unfortunately controlling fans, especially if you wanna do it "right", would take a lot of efforts and resources on our part. And if you fail to configure it properly, quite dangerous things could happen that might just destroy some of your hardware It's not something we'd like to deal with in the near future. We do however allocate even more resources on improving the monitoring capabilities of AIDA64 next year.

It is possible. What you have to do is set proper values for Min, Limit 1, Limit 2 and Limit 3, and set a too low value for Max. The only trick is that Max has to be higher than Min. So for example, for a CPU fan you can set the following values to have a full bar that changes colour depending on the value limits: Min = 0 Limit 1 = 1000 Limit 2 = 3000 Limit 3 = 5000 Max = 1

We've tested it with RTSS, and GPU Bus Type appeared on the OSD properly. Can you have other values displayed properly, or no AIDA64 values appear on the Rivatuner OSD?

You can already use the Aquaero sensor module in the latest AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta

That's fine of course, but the problem in your case is that your fan registers seem to report a zero current even when they're spinning. At least that's what I can see on the Alarm Level related screen shot of yours. Most of the items are already on the SensorPanel. The ones missing are the Pressure, Water Quality, UpTime and Total UpTime. As for the zero fan speed, it will of course be indicated as a zero value on the graphs, as expected.

It seems the problem is that your fans sometimes report a meaningful current, while in many cases they report a zero current. The zero current can also be seen on the Aquasuite 2014 screen shot that you've posted about the alarm level. And when a measured fan current gets zero, AIDA64 will remove the line from the Sensor page and update the whole page since the number of list items changed. Power #1 is the Power Measurement 1, as you can see it in Aquasuite 2014. We'll add Actual Alarm Level in the next AIDA64 beta

Chassis fans on Rampage V Extreme are not calculated or adjusted. They are directly interpreted from the fan registers. Do you have Asus AI Suite installed? If yes, then the issue may be because that software collides with AIDA64 sensor module.

Thank you for the feedback and your kind words

Thank you for the feedback and the report. On the Sensor page it should only reset the page position when the number of items on the page (the number of populated lines) changes. If it's possible, please try to find which value keeps disappearing and appearing again, that should be the one that causes the resets. If you could find the culprit, we can look into it

When we mention "Hardware Monitoring" in the changelist, it refers to a group of AIDA64 modules actually. Those modules are the Sensor Icons, OSD Panel, Desktop Gadget, LCD, SensorPanel, Logging, External Applications, and Alerting. When we add a new item to Hardware Monitoring, it means you can now monitor such values or measurements using either one of the listed modules. Of course such items may or may not be available on a particular hardware configuration. There are many hardware specific readings, for example the SoC temperature is only available on Aquaero or Aquaduct devices. Regards, Fiery

Here's a new AIDA64 beta update ... http://www.aida64.com/downloads/latesta64xebeta ... where we've added the following new bits & pieces to the Aquaero/Aquaduct sensor module: - SoC temperature (a.k.a. Aquaero CPU temperature) - Pump #1 and Pump #2 speed (RPM) and current. We haven't added the frequency value since it's simply 1/60 of the RPM value, and not a separate measurement - Power measurements (as Power #1 .. Power #4) - Water quality (%), pressure sensor, uptime and total uptime. These values are only available on the Computer / Sensor page though Now AIDA64 supports the upcoming new generation of firmware (FW Revision 2000) for Aquaero and Aquaduct devices. The new firmware revamps the HID input report layout, and introduces a few notable feature improvements as well. We haven't had a chance to test the new firmware yet, so the current code may or may not work perfectly. As soon as the new firmware is rolled out, please create a new Aquaero Dump and post it here, so we can analyze the registers output and make changes to AIDA64 if necessary.

We've added the BIOS Version hardware monitoring item. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3219zk8j3xcnhszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. I cannot make any promises about the fan control feature though, since it's still not on our roadmap for this year or next year. Regards, Fiery

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3219zk8j3xcnhszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 2) Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

That value isn't meant to be put on graphs or bars. Regards, Fiery

Thank you for the feedback

Thank you, we'll add the Aquaero temperature in the next beta

Thank you. I'm afraid we need Aqua Computer's kind assistance to figure the missing bits out. They said they will be able to give us a hand next week, so stay tuned Thank you, we'll fix that.

That is a Windows limitation, you can look it up. Many websites bashed Windows 8 and Windows 8.1 for example, when they were rolled out, that they still don't solve the DPI scaling issues. E.g. http://techreport.com/blog/25797/high-ppi-support-in-windows-8-1-still-not-so-great Yes, it is possible to develop a DPI aware application user interface, but it requires a complete rewriting of the user interface code, and reproducing all graphical content like icons and placeholder pictures as well, in multiple DPI levels. The user interface part of AIDA64 is over 200.000 lines of code, not in the league of such utilities like WinRAR or DropBox. Don't get me wrong, they are great utilities, but they don't have a complex UI like AIDA64. And yes, Microsoft fixed Office 2013, but it's the least you can expect from the company that develops Windows and fails to come up with a real solution to the DPI issues And I'm pretty sure not even Microsoft has a full software portfolio that would support proper DPI scaling. As for 4K, as I've mentioned above, when you use 200% DPI (or 400%), things are much less blurry. We've got a Win8.1 tablet with a 2560x1440 native resolution, and we use 200% DPI scaling on it. AIDA64 looks fine there, but of course it's not as sharp as without DPI scaling. And with 4K displays you can simply use 200% DPI scaling setting to avoid blurriness -- which affects most Windows applications. You've listed a few exceptions, but the majority of Windows applications are still not fully DPI aware. We would be more than happy to come up with a quick fix for the DPI issue, just like we do with other bugs or anomalies about AIDA64. But with DPI scaling, there's no quick fix. Yes, you could add a simple entry to the manifest file to enable DPI awareness, but then the whole UI would fall apart. You could of course rewrite 200.000 lines of code, but it would take a hell of a lot of time. And quite frankly, we're still hoping to see Windows 10 or worse case Windows 10 SP1/Update1 to come up with a real solution to the DPI issue. A new windowing system that is based on relative placement and percentage-based UI element dimensions would be terrific. Of course that would also raise the need to rewrite all the UI code, but at least it would mean a proper solution, a proper fix to the problem, not just beating around the bush. I would personally feel like a fool if we had to rewrite the UI code to make it DPI aware now, and then having to rewrite it again when Microsoft comes up with the proper DPI solution...