Fiery

Normally, when you click on AIDA64.EXE (or a shortcut leading to it), it tries to elevate its restricted privileges to administrator privileges, and that triggers an UAC prompt. After then, if you accept it, AIDA64 should be running with full privileges.

I've sent you your product key in private message. BTW, you can initiate the renewal from AIDA64 / main menu / Help / About / Renew Now anytime

It could be because of the lack of or inoperational kernel driver. Can you see anything on the Motherboard / SPD page in AIDA64? Does your Windows user have administrative privileges?

Use the down arrow next to the value to set it to a lower value. Or, you can simply delete the "5.000" in the edit field and write "100" in there.

You can configure the LCD update frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. The lowest value you can specify there is 0.1 sec (100 millisec). Regards, Fiery

Because of this: http://forums.aida64.com/topic/2913-memory-commit-limit-double-available-ram/

Don't be afraid of asking questions The product key is stored in the PKEY.TXT file using encryption. Both legitimate and pirate keys look pretty much the same if you look at just the PKEY.TXT file content. Regards, Fiery

It would be a quite complicated project First of all, you have to develop the hardware + firmware to drive the gauges using a microcontroller. Then you have to connect each gauge to your PC via a standard interface. Considering you would have multiple gauges, using USB, LPT or RS232 may not be the best idea, unless you drive multiple gauges from a single connection. But, even after you've solved the hardware side, you would have to develop a Windows driver and software as well, to process the data coming from AIDA64 and send it to the gauges. Regards, Fiery

I think what you need is Odospace: http://forums.aida64.com/topic/2776-display-pc-sensor-values-on-android-device-connected-via-usb-odospace-remote-panel/ Regards, Fiery

Thank you for the feedback

Thank you for the feedback

Thank you, the issue will be fixed in the next AIDA64 beta update due in a few days from now.

Using the latest AIDA64 beta update (Build 3521) please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic. If you have Windows 10 installed, you may have to enable the status bar first, in AIDA64 / main menu / View. Please also let me know what water level does Aquasuite display. Thanks, Fiery

Thank you for your kind words Please find the mentioned new AIDA64 Extreme beta update at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

Yes, it's less than 50%. The fully random image that you've used to test the JPEG size limit was 1088 KB long. What's unclear to us at this point is whether the SPF JPEG size limit is always a multiply of 64 KB or 100 KB. We have to do more test runs, and also have to get more SPF devices. Please find the mentioned new AIDA64 Extreme beta update at: http://www.aida64.com/downloads/latesta64xebeta Simply add the new RTSS FPS item to your LCD layout, and start RTSS. That's all you have to do basically

Please find the mentioned new AIDA64 Extreme beta update at: http://www.aida64.com/downloads/latesta64xebeta

Thank you for the feedback. We've implemented RAID SMART support and also RAID controller temperature measurement for Adaptec RAID controllers in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works on your RAID setup.

Thank you. The issue was that AIDA64 treated flow rates over 2000 LPH invalid We'll fix that issue in the next AIDA64 beta update due in a few days from now

Thank you. I'm afraid I've asked you to send the wrong debug dump Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic. I'm sorry about the mixup Please also indicate how many flow sensors do you have connected, and what does Aquasuite display as their readings/values.

800P works fine, that's all I can tell about it. There's no real alternative though, since the only other DPF that AIDA64 supports is the AX206 based firmware hacked picture frames, which are small devices, like 2.4 inch and so. Most of the picture frames simply do not implement a feature to push image data through the USB connection and get it displayed directly, without altering the on-board flash memory. Samsung SPF devices are really unique, so if you're looking for a large diagonal picture frame to display real-time sensor data, there's no real alternative to that. Unless of course you would get a cheap Android tablet and use RemoteSensor, Logitech Arx or Odospace with it.

Thank you, but I'm pretty sure that is due to either a temporary or a persistent malfunction of the CPU thermal diode or the motherboard sensor chip. Try to do a complete power-off of your system (disconnect A/C from your power supply unit), and see if it helps.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB Dump. Copy-paste the full results into this topic. If you have Windows 10 installed, you may have to enable the status bar first, in AIDA64 / main menu / View.

Have you tried to upgrade to the new & fixed AIDA64 beta I've linked above?

AFAIK SPF devices do not feature a software method to adjust contrast. There's an interface to control brightness, but we haven't found a SPF device yet where that would work That's why on the AIDA64 / Preferences / Hardware Monitoring / LCD / Samsung page you cannot see brightness or contrast sliders -- while you can see that for other LCD devices like LCD2USB.

Thank you for your reply. Meanwhile we've tested AIDA64 with a great number of combinations on how to utilize fan connections, and our HeatMaster 2 worked flawlessly. The fans never spun up and AIDA64 never became unresponsive. Maybe your HeatMaster 2 has some hardware issues or hardware incompatibility (with your motherboard / USB controller), or has an older firmware than ours. But since you've already retired your device in favor of the more capable Aquaero 5, I suppose we will have to wait for the next similar bug report from another user to see if this issue plagues other HeatMaster 2 devices as well. Thank you again for your attention to this issue.