Fiery

Administrators
  • Content count

    6544
  • Joined

  • Last visited

  • Days Won

    258

Fiery last won the day on June 22

Fiery had the most liked content!

Community Reputation

259 Excellent

3 Followers

About Fiery

  • Rank
    AIDA64 Developer

Contact Methods

  • Website URL
    http://www.aida64.com

Profile Information

  • Gender
    Male
  • Location
    Budapest, Hungary
  • Interests
    AIDA64 :)
  1. Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the devcie (in your case Meizu) didn't encode the info there, then sysinfo apps cannot read or detect it.
  2. It's not only about users' perception. We also would feel a jerky animation unsuitable for the generic quality of our software.
  3. Yes, because it would look bad with no anti-alias support
  4. When I said CRC above, I meant hash (SHA).
  5. Yes, we sadly couldn't finish it up before having to finalize AIDA64 v5.92. We'll work on it as soon as we can get a X299 motherboard, which would be an ideal platform to work on this matter.
  6. AIDA64 detects the current Windows Desktop layout when you start it up, and when it detects that the previous position where you've left the SensorPanel at no longer falls into the visible Desktop area, it will reset the position to (0,0) -- which is the top-left corner of the primary monitor. In your case the problem might be that when AIDA64 starts up, Windows still didn't restore the previous Desktop arrangement, and the Desktop area doesn't yet cover the secondary display. Can you please check if the issue only happens when you restart (or cold start) your computer, or it happens also when you keep your computer running and only restart AIDA64?
  7. Make sure to upgrade to the latest version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if the problem persists.
  8. Thank you. We will fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download.
  9. Thank you for the report! Reading that temperature would involve EC (Embedded Controller) bank switching, which is a dangerous thing to pull off, especially when AI Suite is installed. Or when AI Suite may leave behind its services after uninstallation...
  10. I'm sorry for the delays, and thank you for the dumps. I'm afraid neither of the RAID codepaths AIDA64 currently features supports your RAID controller. We'll try to find out how to handle it.
  11. Thank you. Sadly, Aquaero uses a slow USB protocol, and there's nothing we can do to get around that limitation
  12. Sadly, not all Adaptec controllers are handled properly by AIDA64 at this time. So it's best not to pretend it supports all Adaptec RAID controllers
  13. Multi-GPU support can be dangerous with ULPS-enabled CrossFire setups, but it is fine to have enabled with SLI
  14. That indeed looks very weird. We'll need to see the before & after dumps to find out more about the root cause of the issue.
  15. We don't use an offset for the "CPU" value. AIDA64 should show the same value that Gigabyte's own monitoring software displays as "CPU" temperature.