Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    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. Fiery
    It's not only about users' perception. We also would feel a jerky animation unsuitable for the generic quality of our software.
  3. Fiery
    Yes, because it would look bad with no anti-alias support
  4. Fiery
    When I said CRC above, I meant hash (SHA).
  5. Fiery
    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. Fiery
    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. Fiery
    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. Fiery
    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. Fiery
    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. Fiery
    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. Fiery
    Thank you. Sadly, Aquaero uses a slow USB protocol, and there's nothing we can do to get around that limitation
  12. Fiery
    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. Fiery
    Multi-GPU support can be dangerous with ULPS-enabled CrossFire setups, but it is fine to have enabled with SLI
  14. Fiery
    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. Fiery
    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.
  16. Fiery
    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.
  17. Fiery
    Are you sure Afterburner has no background task that would keep monitoring your sensor readouts, even after you've closed its main window?
  18. Fiery
    The CRC for the ZIP package is downloaded (acquired) from our update server, so it's not possible to manipulate the ZIP package. The CRC is not part of the ZIP package at all, and it doesn't necesserily come from the same download server either. We don't see a vulnerability there.
  19. Fiery
    It is rooted in It is rooted in the limitation of the chipset, since it can only handle up to 8 DIMM slots by default. So the SMBus mux is necessary to make sure it can handle up to 16 DIMMs slots (using a 2-way / binary mux). The SMBus mux of Intel S5500BC, S5520HC, S5520SC and S5520UR motherboards are handled by AIDA64. Rare exception, but it's there. The mux of a few Asus and Supermicro motherboards are also handled.
  20. Fiery
    We can implement any mux, as long as we get the technical guidelines on it. In case Lenovo is willing to help us out about that, we'd be happy to add a mux for your motherboard. It's a discontinued product, so if you ping the right person at Lenovo, there's a chance they figure there's nothing wrong handing out such details on an old-ish product...
  21. Fiery
    Sadly, most 2-way and 4-way server motherboards use a SMBus mux to handle the SPD for more than 8 DIMM slots. Such muxes are proprietary and not documented at all, so we can only support a few of them where we somehow could obtain the technical guidelines on handling the mux. I'm afraid we have absolutely no such information on any Lenovo server motherboards though, so we can only support them without handling the SMBus mux. It usually manifests as AIDA64 being able to detect half or 2/3 of the installed memory modules -- exactly as it is in your case.
  22. Fiery
    Yes, our automatic update system verifies the CRC for the downloaded ZIP package before extracting it and moving the files to replace the old files. Regards, Fiery
  23. Fiery
    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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  24. Fiery
    Great minds read each other
  25. Fiery
    I've sent you my email address in private message
×
×
  • Create New...