Fiery

OpenStore rules still dictate that only open-source apps can get to the store that require special privileges. Since our app requires special privileges (due to being a sysinfo type of app) and it's not open-source, it cannot get to the OpenStore. The community behind the OpenStore needs to change their rules in order for be more welcoming to non-open-source apps.

I can't see considerable enhancements to the core OS, the UI, or the API set. No new official devices either, and no new store that is not the Open Store. It's still not something we can work with.

Please post an updated RAID Dump with the LSI RAID support option enabled.

You can share the system specifications of your device in email, by sending a report.

No, it's not supported. Gauge supports time, as explained above, but it's not an analog clock.

Do you have the sensor item GPU BI Utilization listed in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications? If yes, then make sure to tick the checkbox next to it.

Please try to find what value (which line of the Sensor page) keeps disappearing and reapperaring -- because such anomaly causes the page to get reinitialized and scrolls back to the top. If you cannot pinpoint the line(s), then please try to create multiple reports of the Sensor page (by right-clicking on Sensor in the left menu --> Quick Report --> HTML), and compare them against each other.

No problem

Thank you for your feedback!

Make sure to have LSI RAID support enabled in AIDA64 / main menu / File / Preferences / Stability.

Here's the above mentioned new beta build with the fix implemented: https://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

Here's the above mentioned new beta build with the proper fix: https://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 gain a bit more knowledge about our software, try the different features and settings before submitting such bold and obviously incorrect statements. If you set the SensorPanel transparency setting to a non-zero value in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel, the whole SensorPanel will become opaque, not just the background. So it's not a background transparency setting at all. Second, if making only the background transparent would involve just a few lines of code, don't you think we would have done it years ago? It's a lot more complicated than that. Finally, the SensorPanel -- just like all other features of AIDA64 -- are still actively developed. Not everything is touched or tweaked daily, since that would mean hiring 100 more developers to work for us, but for example, a few weeks ago we worked on SensorPanel window and SensorPanel item configuration window positioning for multi-monitor systems...

Try to update the BIOS and Windows 10, as well as your video driver. Perhaps those will help.

Great news. Please let us know if the problem comes back again.

I have no idea what's enabled on your configuration But I'm glad you've managed to make it work. These days it is becoming more and more challenging to use legacy hardware...

It's on hold right now. We'll continue to work on it in December or January. We're currently very busy with other issues

Please let me know when you've finalized the protocol, after implementing all the features you want to have in the protocol. IMHO it would be best to send bitmaps in case the WLAN connection is fast enough to handle at least 1 (one) FPS. And even though it's a minor issue, but please also think of a name for your device, so we can refer to it in AIDA64 once we've implemented your protocol. Name can be anything, like PythonLCD or HbozyqLCD or anything Shared Memory can be used to export the sensor values measured by AIDA64 into a standard Win32 shared memory region. You can then take that from there and push it to your device the way you want. Please check the AIDA64 user's manual --> External Applications --> Shared Memory for more details.

The SensorPanel rendering engine doesn't support background transparency.

1) The multiplier range is supposed to show the non-Turbo values. 2) Most modern hard drives report a considerably lower value for buffer size in the ATA ID block than the real one. If you scroll down on the Storage / ATA page, and check the section called Disk Device Physical Info, you should be able to find the correct buffer size of 128 MegaBytes there.

Please contact the author of Office (Microsoft) to obtain your product key. This is a forum dedicated to supporting our software AIDA64, and not other company's software. This topic is locked.

Do you have the latest WHQL ForceWare driver installed?

The issue will be fixed in the next AIDA64 beta build. I'll post a message into this topic once the new update is available for download.

AIDA64 uses Asus WMI ACPI calls to measure sensor values on your motherboard. The incorrect readings are due to a BIOS bug.

Thank you. The RGB LED module of AIDA64 currently doesn't support fans or water coolers.