Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12569

  • Joined

  • Last visited

  • Days Won

    562

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you! If you could kindly also include the timing parameters and native resolution of those displays, we could add them with more details.
  2. Fiery
    Sadly since there's no 64-bit SDK DLL supplied by Razer for your keyboard, there's no perfect solution. You can either stick to AIDA64 v7.70 (latest 32-bit version) or use limited functionality with AIDA64 v8.xx (64-bit versions). By moving to the new 64-bit native binary at AIDA64 v8.00 release, we did our best to retain compatibility with as many old hardware as possible. Unfortunately we couldn't solve all issues that came up in relation to the 32-bit to 64-bit transition.
  3. Fiery
    Are you using AIDA64 v8.20 (latest version) ?
  4. Fiery
    Yes, as long as they are different AIDA64 editions. So for example you can use AIDA64 Extreme and AIDA64 Engineer in the same time. But since only one of them would be able to communicate with the AIDA64 kernel driver, you wouldn't be able to use both AIDA64 instances for hardware monitoring.
  5. Fiery
    1) AIDA64 v8.xx hides all LCD protocols that have no corresponding device connected to the computer. This is because the number of protocols became too large to handle and sort out. You can still do a right-click --> Show All on the LCD tabs to make all LCD protocol pages appear. 2) I'm afraid we are not aware of any external displays that would be 14.5" and would not act as an external monitor. Your best bet is to connect your device as a monitor and use the SensorPanel facility of AIDA64 with it.
  6. Fiery
    I'm sorry, but we do not deal with such displays that can be used as a secondary monitor. Theyt already work with SensorPanel.
  7. Fiery
    It's not easy to capture the power state where the memory frequency is at the "right" level since during the benchmarks we cannot measure memory frequency (or any other system parameters) in order to avoid affecting the benchmark results. And apparently as soon as the system gets to a state that's close to idle, the memory frequency is quickly lowered on your configuration...
  8. Fiery
    Thank you, we will fix the remaining issue in the next AIDA64 beta update.
  9. Fiery
    @Iceberg @Tualua @JaxJiang We've implemented advanced sensor support for Minisforum computers in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works.
  10. Fiery

    Temperature

    Fiery replied to artem3107's topic in Android Forum

    Zero and sub-zero temperatures are considered invalid readings by AIDA64.
  11. Fiery
    Thank you for the data! Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  12. Fiery
    After installing its corresponding device driver, your device (Win USB Display) actually acts as a secondary monitor under Windows. So there's no need to implement native USB display support for it, but you can simply use the SensorPanel facility of AIDA64 with your display.
  13. Fiery
    It's not possible to get it from Task Manager I'm afraid.
  14. Fiery
    That looks normal. I suspect the slow update rate is because WigiDash software does the updating of the display too slowly. Please note that unlike with most LCD protocols, WigiDash displays are updated through shared memory interface with their WigiDash software. So the actual communication with the display hardware is not done by AIDA64, but by WigiDash software.
  15. Fiery
    I've sent you a private message about this.
  16. Fiery
    It is sadly due to a firmware limitation of Turzx/Turing screens: when the layout you build is too complex, the rendered image can only be transferred in 2 chunks (2 steps). That causes flashing/blinking effect. If it bothers you too much, try to come up with a less complex layout, for example by using a simpler background image.
  17. Fiery
    No, since as far as we know, it's not possible to measure the actual GPU utilization on Intel GPUs.
  18. Fiery
    It depends on how the standard Android Battery API is implemented on your phone.
  19. Fiery
    In order to have support for your GPU, you need to upgrade to the latest AIDA64 version of 8.20: https://www.aida64.com/downloads/latesta64xe
  20. Fiery
    Thank you for your feedback!
  21. Fiery
    Yes, but the serial numbers there are detected using a different driver call.
  22. Fiery
    Yes, somehow the new native NVMe driver doesn't provide serial number at all, or provides a different serial number than the drive has got. We're not sure why that is, our best guess is that there's a driver bug that Microsoft has to fix up.
  23. Fiery
    Thank you for your feedback! We will fix the mentioned issue in the next AIDA64 beta update.
  24. Fiery
    @Benni231990 @FatBoyNL @Tomorrow @Miroslav Tuhársky We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  25. Fiery
    We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
×
×
  • Create New...