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's a good idea indeed. The problem is that the current Alerting module can only check for changes against a pre-defined value. So you could set an IP (if there was such an alerting item defined), and when the current one differs from it, then an alert could be fired. But, the current solution wouldn't be able to recognize the new IP then and check for changes against it from then on. So first we need to make the whole thing more sophisticated by implementing a simple "change" alert trigger, besides the current "above X" and "below Y" triggers. Although that one wouldn't be suitable for the rare case when the IP changes while AIDA64 is not running...
  2. Fiery
    We'll check how to do that. We haven't really dealt with such a bar style yet on the basis that in our opinion it would make the visual impact of the SensorPanel a bit "too much", a bit like a parrot
  3. Fiery
    The basic issue is that even with EC traffic, such high latency is not supposed to occur. Other users with Asus motherboards having an EC chip do not see such anomalies. So it must be something about your computer IMHO. Maybe you've got another software running in the background that collides with the EC register readout activity of AIDA64?
  4. Fiery
    When you offer tons of flexibility in designing a visual layout, it's a great challenge to come up with a UI that is both easy-to-use and easy-to-navigate. It's a bit like sitting in a Boeing 737 cockpit and complaining about the unfriendly layout of the dashboard
  5. Fiery
    I'm pretty sure that activity is not related to the clean AIDA64 build that you can download from our website. Your AIDA64 copy may be infected or otherwise altered (cracked, hijacked, etc). Basically there are 2 distinct internet activities that AIDA64 performs between the user's computer and our servers. The first one is related to the auto-update feature, and should happen in the frequency you choose in AIDA64 / main menu / File / Preferences / General / NetUpdate. You can completely disable the auto-update check there, if you wish. The other activity only happens if you have the External IP Address sensor item placed on your OSD Panel, SensorPanel, LCD, log file, or used as an External Applications item. That activity is repeated every 15 minutes while you keep AIDA64 running. It simply pings our servers to obtain the external IP address of the user's computer. The repeat frequency is set to 15 minutes in order to avoid putting too much pressure on our servers.
  6. Fiery
    Without EC (Embedded Controller) support, you'd lose some of the sensor readings you may have places on your LCD layout. So it's not a good idea to disable EC support as long as you'd prefer to have all sensor readings.
  7. Fiery
    Thank you! It seems the issue is that the HDD serial number fields aren't properly populated, and AIDA64 filters out 2 drives you've got due to similar serial numbers. We'll fix the issue in the next AIDA64 beta update due in cca. a week from now. I'll drop a message into this topic once the new build is available for download.
  8. Fiery
    SensorPanel works similarly to the LCD module. You can place an image on the panel that has the full size (dimensions) of the panel to make it the background image. If you're looking for something else, let me know where did you get stuck exactly.
  9. Fiery
    Looks stunning, great job!
  10. Fiery
    Thank you, we'll try to keep it up
  11. Fiery
    If your display appears in Windows as a regular monitor, and you can extend your Windows Desktop over it, then you can simply use the AIDA64 SensorPanel module instead of the LCD module
  12. Fiery
    Thank you for the feedback. We've checked the RAID Dump, and it looks normal, all 8 drives can be found in that particular dump. So the issue must be somewhere else. Please also post an ATA Dump and SMART Dump, so we can check how AIDA64 slots the drives into those modules.
  13. Fiery
    I'm not sure if a hidden (into a right-click context menu) option to hide the serial numbers would be any more of a help than just asking them to use MS Paint to put a big black box over the serial number (or use the eraser tool) But, in case you find it useful for your own purposes, we'll add the Show Drive Serial Number option to the right-click context menu on the SMART page.
  14. Fiery
    Holy cow
  15. Fiery
    Awesome, thank you!
  16. Fiery
    When does the mentioned error message pops up? Before you select the file where you want to export (save) your settings into, or after that? If after, then please let me know where you want to save the file, and whether you've tried to use different paths with the same result. It's not a problem to duplicate custom gauges.
  17. 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. Also right-click on the bottom status bar of AIDA64 main window --> 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
  18. Fiery
    That is not really ignorance, but more a failed understanding of how AIDA64 memory bandwidth benchmarks work. Even hardware manufacturers (I won't name drop here) fall into that trap from time to time. What's important to know about our memory bandwidth benchmarks is that even though they are multi-threaded, it doesn't mean that they will always utilize all available cores or logical processors (threads) to measure bandwidth. We use a clever automatic calibration process that finds the optimal number of CPU resources to attain the highest possible memory bandwidth scores. The whole UMA vs. NUMA score issue would look different if AIDA64 always utilized all 16 cores (or 32 threads) of AMD Threadripper processors.
  19. Fiery
    I'm glad you could resolve it, because we couldn't find out what's wrong on our end. We've tried to replicate the issue, but the only idea we came up with -- and even that one was a weak one -- is that your internet connection to our server (that provides the external IP info) is very slow for some reason. As for alerts: the existing AIDA64 Alerting module doesn't support changing label colours when an alert is fired. You can have a warning message box popped up, your computer shut down or an audio alert fired (played).
  20. Fiery
    In our opinion that information is very helpful, especially when the system has multiple drives of the same model. Why would you want to hide that information?
  21. Fiery
    Thank you. We've fixed the issue in 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 how it works.
  22. Fiery
    Thank you for the dumps. We've fixed the issue in 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 how it works.
  23. Fiery
    No, it's not. But here's the one that is https://www.aida64.com/downloads/latesta64xebeta
  24. Fiery
    We haven't noticed it yet, and no other US based AIDA64 users complained yet. We've asked our ISP, but they also haven't found any issues. So it could have been (it could be) something under the ocean or such
  25. Fiery
    "Waiting for Sync" is not displayed by AIDA64, so the issue must be in either the Android platform (about email submittal), or in the email app you use to send the report out.
×
×
  • Create New...