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 may have been a temporary failure of our download server.
  2. Fiery
    I've just checked it, and they're there: http://www.aida64.com/downloads Try to press a Ctrl+F5 to completely refresh the page and all its elements. Regards, Fiery
  3. Fiery
    The normal gauges are not compatible with the RemoteSensor and Logitech Arx modules. That's why we had to replace them with the arc gauges.
  4. Fiery
    Yes, you can simply import an exported SensorPanel layout into your LCD layout editor, and vice versa, since the files are compatible. The only thing you have to be careful about is importing a multi-page LCD layout into the SensorPanel, since the SensorPanel supports only a single page.
  5. Fiery
    Sad to hear that it doesn't work with either driver I've moved your device to the "not working" category in the opening post. I'm confused though, since it seems to work in some cases, while on a similar (or almost similar) device it fails to work. Maybe the issue is related to a certain hardware revision or firmware revision? Hard to tell, we have very limited knowledge about SPF variants
  6. Fiery
    I'm afraid that's not possible. What you could do is build a panel that features most of the basic building blocks you usually put on your panels, and export it to a file that you back up. Then, the next time you start building a panel, you can start off by importing that "base" panel to accelerate the process of building up the new panel.
  7. Fiery
    It's not easy to diagnose such issues without any specific numbers Please let me know the clock configuration for both your CPU and IMC (memory), and also the Memory Read, Memory Write and Memory Copy scores you've got via AIDA64.
  8. Fiery
    Do you use the Samsung Mini-Monitor driver, or our LibUsb driver?
  9. Fiery
    AIDA64 for Android uses standard Google AdMob interstitial ads from day one. Since the ads are provided by Google, our app has no control over the quality of the ads. We feel the best way is to use Google's ad service under Google's own operating system (Android), and let's hope they have full control over the quality of the ads they push to Android apps You can experience no ads at exit when you exit the app too quickly, or when the ad is not yet loaded from the internet, or when Google AdMob fails to provide an ad to display. Regards, Fiery
  10. Fiery
    Please note that not all anti-virus software are capable of providing the known virus count to 3rd party applications like AIDA64. Approx. half of the anti-virus software that AIDA64 recognizes do not provide that information Regards, Fiery
  11. Fiery
    At least a few hours for both tests. Ideally, 12 or more hours, if it's possible.
  12. Fiery
    Renting is not an option, since we would have to re-measure the benchmarks in the future when a particular benchmark method gets updated. Not to mention the cases when new benchmark methods are introduced. So renting wouldn't work, and those companies you mentioned do not have an incentive to provide us with hardware. BTW, in the benchmark reference list of AIDA64 we do have a Haswell-E based system, so the platform itself is not neglected by us. And by not using the highest end CPU available for a particular platform, AIDA64 users have a better chance to beat the reference results
  13. Fiery
    The FPU test, when used alone, is the most demanding stress testing method, since it uses AVX and FMA instructions to heat the whole CPU package up as much as possible, and puts the highest load on the CPU. It's not a diverse stressing though, since it focuses on the thermal stress, so we generally recommend to run the FPU subtest for a few hours, and in case the system can stand it without issues, then run a mixed test as well, by enabling all subtests (including FPU).
  14. Fiery
    Thank you for your feedback
  15. Fiery

    UEFI

    Fiery replied to XORROR's topic in Brainstorming

    Ah, you mean the UEFI Specification release I'm sorry, that's an entirely different version number than the UEFI version that your motherboard currently has flashed into the firmware chip. I'm afraid we have no information on how to detect that property. In other words: it most likely means it's not possible to do that.
  16. Fiery
    We've checked it, and the Spotify Windows client does not seem to offer a SDK that would allow AIDA64 to read song title information from Spotify Regards, Fiery
  17. Fiery

    UEFI

    Fiery replied to XORROR's topic in Brainstorming

    UEFI is the successor to BIOS. It's simply the firmware of PC motherboards. BIOS was first, and then it was phased out in favor of UEFI. UEFI ("BIOS") version for your motherboard is P4.00.
  18. Fiery
    We usually recommend closing other processes, windows and if possible, background services as well, at least for the first run. After the first run is successfully finished, you can use different stress testing scenarios, like having multiple stress test software running in parallel. Regards, Fiery
  19. Fiery
    I'm afraid we have no plans to support POP3 email checking at this time.
  20. Fiery
    You have to use the Move Up button in the SensorPanel Manager to move the background image to the top of the list. The list is arranged as a Z-order, so the first entry is placed on the bottom of the Z axis, and the next one is placed on top of it (higher on the Z axis), etc.
  21. Fiery

    UEFI

    Fiery replied to XORROR's topic in Brainstorming

    UEFI version should be reported as BIOS version already. If you cannot find it on the Motherboard / BIOS page, then try to find it on the Computer / DMI page.
  22. Fiery
    There was an unfortunate bug in AIDA64 Beta Build 3429. We've just rolled out Build 3435 that should fix it up: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works.
  23. Fiery
    We've tested the AIDA64 LCD module with Yocto-MiniDisplay and Yocto-MaxiDisplay, and they both worked flawlessly. But those are quite little screens, compared to a photo frame. And they do not feature buttons to change pages.
  24. Fiery
    We've edited the first post, thank you. How about using your cell phone or tablet display as a wireless LCD for AIDA64? http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/
  25. Fiery
    AIDA64 uses an unofficial, non-documented interface to communicate with Samsung SPF devices. If it doesn't work on your device, then I'm afraid we cannot help you out Only one thing you can try: in case you have a complicated LCD layout, you can try lowering the JPEG quality, but about the 5-seconds issue I don't think that would help
×
×
  • Create New...