Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    The issue will be fixed in the next AIDA64 beta update due in a few days from now. Regards, Fiery
  2. Fiery
    It's not because of the trial limitations. It's rather because your motherboard is not capable of monitoring VCCSA and CPU Cache voltage rails. What it can do is alter the voltage settings, but it is not monitoring I'm afraid.
  3. 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. In case you're running Windows 10, then you may have to enable the status bar first in AIDA64 / main menu / View. Thanks, Fiery
  4. Fiery
    Are you using your Kingston memory modules at DDR4-2133 or DDR4-2400 setting? If you're running at DDR4-2400 -- which is considered overclock with your CPU --, then try to up the command rate (also known as tCR or tCMD) from 1T to 2T. Also verify if the IMC is actually driving your memory modules at the rated voltage, as specified by Kingston.
  5. Fiery
    Those simple 1, 2 or 3 pixel width lines, without anti-aliasing don't look all that great IMHO And even if we did that the simple (easy) way, customizations on needle length (and/or dial diameter), needle colour and needle width would still be necessary -- of course for all 3 needles separately Users would also expect us to bundle various dial images (in multiple sizes, of course), and that could easily raise IP (copyright) issues. Not to mention the issues about frame updates: even with a digital clock many users complain about the irregular updating of the clock, ie. the update pace is not exactly following the clock's 1 second pace. The occasionally missed seconds would look even worse with an analog clock.
  6. Fiery
    It renders the image using a backbuffer in the system memory (RAM).
  7. Fiery
    I'm afraid we're not planning to do that. The problem is: it's not like any other sensor items where you can display a value using a fixed formatting method. Everyone would like to customize every bits of the date display, and the hardware monitoring module of AIDA64 doesn't support such deep customizations on a measured/detected value. It would indeed be nice, but the AIDA64 LCD/SensorPanel rendering engine wouldn't be capable of rendering a really nice analog clock, with a properly rendered needle. That's the reason behind not supporting classic analog gauges as well.
  8. Fiery
    Thank you for your help about test runs.
  9. Fiery
    Is your CPU or RAM overclocked, power limit unlocked or otherwise tweaked from their factory default settings?
  10. Fiery
    Windows 10 universal apps have the same limitations as Windows Phone 8.1 apps using WinRT API. The API itself does not expose any interface to let apps measure temperatures. WP8 based devices themselves -- based on Qualcomm SoCs -- do measure over a dozen of temperatures, and the Windows Phone kernel manages those temperatures in individual thermal zones, but sadly Microsoft didn't implement an API in WinRT to access the thermal zones I personally of course understand that there's a reason behind using a strong sandboxing environment, to assure the maximum security and stability of the system, but a read-only access to temperatures wouldn't hurt too much Same goes for clocks: Windows Phone 8.x and Windows 10 Mobile kernels can measure CPU and other clock speeds easily, but they don't expose those measurements to apps. BTW, we've issued a feedback to Microsoft, asking for the implementation of a WinRT thermal management API, but I don't think it would be get done before next year.
  11. Fiery
    I'm afraid only Samsung SPF digital picture frames are supported, and the AX206 based hacked firmware little frames like Pearl, e.g.: http://www.ebay.com/itm/NEU-lcd4linux-2-4-DPF-Coolstream-Dreambox-Enigma-Neutrino-Pearl-Display-/121723739706?hash=item1c574cde3a
  12. Fiery
    You can change the poll rate in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. Regards, Fiery
  13. Fiery
    We've implemented sensor support for Asetek VI based (NZXT Kraken X31, X41 and X61; Corsair H80iGT, H100iGTX and H110iGTX) water cooling devices in the following new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta It also supports multiple Asetek LC and Asetek VI based sensor devices, just as you've requested
  14. Fiery
    We've fixed the issue in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta
  15. Fiery
    Here's the first AIDA64 to support RAID member enumeration on Adaptec RAID controllers: http://www.aida64.com/downloads/latesta64xebeta Please note that it's not capable of measuring temperature of Adaptec RAID member drives just yet. It should come in the upcoming days though. Until then, please check if your drives properly appear on the Storage / ATA page now, and that you don't see any anomalies or instability while using this AIDA64 beta on your Adapec RAID system.
  16. Fiery
    Here's the mentioned new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    I suppose the issue is due to the differences between the Win7 and Win10 kernels. That may cause a slightly unstable BCLK clock. You can check the measured BCLK if you issue a CPUID & MSR Dump. Go to AIDA64 / main menu / View, enable the Status Bar, then right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, so we can check the output of all registers about clock measurement. Also, have you checked the BCLK and CPU core clock with other tools like CPU-Z? If it shows the same clocks, then it's not really the fault of AIDA64
  18. Fiery
    Edge and IE are two different software, and the don't disable or affect each other. You can see version number for both on the Computer / Summary page in AIDA64. We will fix the issues on the Licenses page in the next AIDA64 beta update Thanks, Fiery
  19. Fiery
    Thanks for the test runs, the improved SoundGraph LCD/VFD support module will of course be implemented in the next AIDA64 beta update, and also the next AIDA64 stable update. The stable update is currently scheduled to be rolled out in late September -- not written in stone though
  20. Fiery
    It means we don't need that reading on your system
  21. Fiery
    Thank you, that's fine too I've just dropped you a private message about this.
  22. Fiery
    I think those temperatures are quite nice and low
  23. Fiery
    Thank you. Can you please check what driver is installed for your device? Open Device Manager, double-click on the device named "SG Remote Control Device", select the Driver tab, and push the Driver Details button. Only the filename is important, the full path (directory) is not that much. I wonder if your device uses the driver called iMON_PAD.sys.
  24. Fiery
    Thank you. It seems your iMon is not like most iMon devices Most iMons have USB HID devices, and even though yours share USB ID with "regular" iMons, it works differently. Can you please send me a download link to the official drivers and software for your device? We have to check what driver does it have installed, to see what interface/API should we use to talk to the device. Also, drop me a private message in case you know another one for sale I've tried it on the 'bay, but with no luck...
  25. Fiery
    I think that device is already supported in AIDA64 v5.30 (latest version). Just enable SoundGraph iMon VFD support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD.
×
×
  • Create New...