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
    It is usually due to a background process or service that uses system resources, and causes AIDA64 to "race" for L2 cache usage. Try to close as many background processes and stop as many services as possible. Alternative solution is to measure the L2 scores 10 or 20 times, and ignore the lowest 50% of the results.
  2. Fiery

    Vulkan API

    Fiery replied to Displax's topic in Android Forum

    We've recently rolled out AIDA64 for Android v1.37 app update that implements full Vulkan support. The enumerated Vulkan devices appear on the Devices page. Please note that even the latest Android N Developer Preview 3 doesn't include a Vulkan-ready nVIDIA ForceWare video driver. It would however work fine with Nexus 5X, Nexus 6P and Nexus Player. As for Samsung's Galaxy S7 and S7 edge, those devices seem to implement a strangely named Vulkan library (libvulkan_sec.so) that may not be suitable for us to use as regular Vulkan library. We'll have to check it in more details, or wait for the next S7/S7 edge system update to find out why the library is not named as libvulkan.so on those devices.
  3. Fiery
    We've just checked it, and it still works fine under both Win7 and Win10, running the latest AIDA64 version. Make sure to check if your firewall software is properly configured, and that you're using the right TCP/IP port.
  4. Fiery
    Thank you for the feedback
  5. Fiery
    Thank you for the feedback
  6. Fiery
    The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery
  7. Fiery
    The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery
  8. Fiery
    DMI generation is indicated for the underlying hardware, hence it shows its capabilities, as opposed to showing its current operating mode. We've implemented System Agent clock measurement in the latest AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works
  9. Fiery
    We've checked it, and it still works for us, under both Windows 7 and Windows 10. What Windows version are you using? Do you still have both NICs listed properly on the Network / Windows Network page in AIDA64, with their respective download/upload rate shown there too?
  10. Fiery
    AIDA64 is already localized to Spanish.
  11. Fiery
    You're right, it would work if we implement conditional rounding of electrical current and power readings. It will be featured in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.
  12. Fiery
    Sensor Icons cannot indicate electrical current or power values, due to limitations on the number of digits the icons can display. Regards, Fiery
  13. Fiery
    Please check post #9 on the first page of this topic
  14. Fiery
    Yes, it must be a collision between AIDA64 and Corsair Link Software. Are you using the latest beta version of AIDA64 (v5.70.3854), and also the latest version of Corsair Link Software? (v4.2.3.41) We're now in discussion with Corsair, trying to figure out the best way to synchronize their software with our software. From now on, you will see constant improvements on both sides, so soon the collisions will be gone. Till then, make sure to enable automatic updates to AIDA64 beta packages (AIDA64 / main menu / File / Preferences / General / NetUpdate), and also keep Corsair Link Software up-to-date.
  15. Fiery
    RemoteSensor port is set in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. I mean the firewall software that's running on your Windows computer. In your firewall software you have to make sure to open the TCP/IP port you use for RemoteSensor. Otherwise the firewall software will block the RemoteSensor network traffic.
  16. Fiery
    Are you sure your phone uses the same IP address range (e.g. 192.168.0.xxx) as your main computer? Do you have the TCP/IP port that you use for RemoteSensor open on the firewall software running on your computer? Maybe you not only changed the router but also switched firewall software? Localhost doesn't count about firewall issues
  17. Fiery
    We don't have plans to enable that, since you can achieve the same goal by using the SensorPanel: You can have the System Stability Test and SensorPanel windows open next to each other.
  18. Fiery
    The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.
  19. Fiery
    It should be possible to turn the device on in mini-monitor mode, or change the operation mode while it's on, using the buttons of the SPF device. Once the device is switched to mini-monitor mode, you should be able to install the SPF drivers we've put together. BTW, when you start AIDA64 and enable Samsung SPF LCD support, and it detects a SPF device in mass-storage mode, it should initiate the transition into mini-monitor mode, to ease the process of installing the driver. However, for your device maybe that transition cannot be initiated by a Windows software
  20. Fiery
    CPU IA Cores and CPU GT Cores temperatures are read from the CPU, and not from the iGPU. Hence, it's quite possible that the CPU provides the iGPU (GT Cores) temperature even when the iGPU is disabled. The iGPU may be disabled, but its thermal sensor would still continue to operate. You can verify if the iGPU is really disabled by checking the list of GPUs on the Display / GPU page in AIDA64. Regards, Fiery
  21. Fiery
    Ever wondered how big the new nVIDIA Pascal GPU family would turn out to be? Here's the whole list of Pascal SKUs, with their respective PCI device IDs. Enjoy! Note: The list contains a few Maxwell IDs as well, in order to clarify the difference between GMxxx-A and GMxxx-B PCI device regions. Note #2: GM200-B may have been a second iteration, an optimized variant of the original GM200, but never reached the market. Could have been a plan B in case Pascal slips to late 2016 or 2017. [...] 15F0 Graphics Device [GP100GL-A] 15F1 Graphics Device [GP100GL-A] [...] 1725 Graphics Device [GP100-B] 172E Graphics Device [GP100-B] [...] 1B6F Graphics Device [GP102-B] [...] 1B80 GeForce GTX 1080 [GP104-A] [...] 1C02 Graphics Device [GP106-A] [...] 1CC2 Graphics Device [GP107-B] [...] 1D01 Graphics Device [GP108-A] [...] Click for the full list of PCI IDs here.
  22. Fiery
    We've contacted Corsair to ask for their assistance on this issue. I'll let you know in this topic once we have an update to this issue
  23. Fiery
    We don't have a list of affected devices. Refer to the following forum topic, especially the last few pages: https://forums.aida64.com/topic/2424-new-lcd-device-support-samsung-spf-digital-photo-frames/page-16
  24. Fiery
    Thank you for the feedback and your kind words
  25. Fiery
    That's great news, thank you for your feedback!
×
×
  • Create New...