Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12228

  • Joined

  • Last visited

  • Days Won

    539

 Content Type 

Everything posted by Fiery

  1. Fiery
    It's not relative to the main monitor. It simply has a fixed X,Y coordinate on the Windows Desktop. The Windows Desktop may span across multiple monitors, and the Windows Desktop arrangement may change in case Windows shuffles monitors around or when resolution of one ore more monitors change. It's best if you could assure that the monitor where your SensorPanel is placed gets fixed coordinates on the whole Windows Desktop. Try to make that monitor to be left and top of everything else.
  2. Fiery
    Thank you for your continued support.
  3. Fiery
    I suppose it's because when AIDA64 is restarted during the automatic update process, the RemoteSensor module may not be properly closed and de-initialized. We will tweak that in the next AIDA64 beta update.
  4. Fiery
    Thank you, we'll order a unit and check it out.
  5. Fiery
    Custom Variables is a feature that is designed for a different purpose, it's geared towards assisting network audits in corporate environments. AIDA64 currently supports reading strings and DWORD values from the Registry, and put them on external displays (or SensorPanel, OSD Panel, etc). You need to find a way to write the Registry values into the following path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues And name them as: Str1 Str2 ... Str10 for string values, or: DW1 DW2 ... DW10 for DWORD values. As you keep updating those values in the Registry, the values get updated on your external display.
  6. Fiery
    I suppose in your case we'd need to focus on the Razer 8-port hub you've mentioned. That's the device that we need to natively support in AIDA64. Please let us know what's the model name or part number of that Razer device. I assume it is connected via USB to your motherboard, is it the case?
  7. Fiery
    I've sent you a private message about this.
  8. Fiery
    Thank you! I've sent you a private message about this.
  9. Fiery
    Awesome, thank you! We will fix the fan labels in the next AIDA64 beta update. I will post a message into this topic once the new build is available for download.
  10. Fiery
    Do you have a reference software, made by e.g. Minisforum that could show you the list of fans with their proper labels? Another solution may be to go to your BIOS Setup (UEFI Setup) and check the fan RPM readings there. If you do this, please take a photo of the page where the BIOS Setup shows the fan readings, and send us here.
  11. Fiery
    Thank you for your feedback!
  12. Fiery
    We’ve fixed the issue in an updated v7.20 build that you can download from: https://www.aida64.com/downloads/latesta64xe
  13. Fiery
    Can you please share one of the layouts you're trying to import?
  14. Fiery
    I've sent you an email about this issue.
  15. Fiery
    Do you mean this software? https://getfancontrol.com/ And if so, how come it can monitor more fans than AIDA64? What are those fans connected to?
  16. Fiery
    Thank you. We've checked the sensor chip registers, but we can only find 2 fans spinning there. Are you sure your motherboard can monitor the 3rd fan properly? Can you see it having a meaningful RPM value reported in the BIOS Setup (UEFI Setup) ?
  17. Fiery
    We've done test runs, and so far we haven't found a solution. So far our conclusion is that Windows 11 simply discontinued granting low-level write access to drives
  18. Fiery
    Thank you for your feedback!
  19. Fiery
    Yes, we've updated the packages to roll the hotfix out ASAP.
  20. Fiery
    In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  21. Fiery
    Thank you! Can you please make a screenshot of the issue? I'm wondering if the popup error message appears after the Monitor Diagnostics window has already appeared, or it never appears.
  22. Fiery
    We haven't tried reaching out to them so far. We assumed it can be done on our own. We'll try to contact them.
  23. Fiery
    Thank you for your feedback!
  24. Fiery
    1) Please try to remove the file called AIDA64.MONDIAG.INI in AIDA64 installation folder. Let me know if it helps. 2) We will fix that in the next AIDA64 beta update.
  25. Fiery
    In the state where DIMM temps are gone, in AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
×
×
  • Create New...