Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12419

  • Joined

  • Last visited

  • Days Won

    551

 Content Type 

Everything posted by Fiery

  1. Fiery
    It means we don't need that reading on your system
  2. Fiery
    Thank you, that's fine too I've just dropped you a private message about this.
  3. Fiery
    I think those temperatures are quite nice and low
  4. 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.
  5. 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...
  6. 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.
  7. Fiery
    Thank for the data. Please check if the motherboard temperature changes (when Dell SMI support is disabled), or it shows a constant (fixed) value. Thanks, Fiery
  8. Fiery
    Yes, they will be added back as Virtual Memory in the next AIDA64 beta.
  9. Fiery
    I personally found reading out those big characters from a close distance quite a bit of a challenge. Even from a distance it's not quite as easy as I would have hoped. Truth be told, I was using a BlackWidow Chroma, and not a G910, since our G910 still hasn't arrived. Maybe the G910 is better in this regards, we'll see when it gets here...
  10. Fiery
    We've renamed that to Virtual Memory on the Motherboard / Memory page, and removed the corresponding items from the hardware monitoring module. http://forums.aida64.com/topic/2913-memory-commit-limit-double-available-ram/
  11. Fiery
    The latest AIDA64 beta may fix the occasional scrambled picture issue after a hot-plug situation: http://www.aida64.com/downloads/latesta64xebeta
  12. Fiery
    We've implemented the requested new sensor items in the latest beta version of AIDA64 Extreme available at: http://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
  13. Fiery
    Thank you, we've fixed this issue in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery
  14. Fiery
    Thank you, we've fixed this issue in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery
  15. Fiery
    You're using an old AIDA64 version. Only the latest release (rolled out 2 days ago) of v5.30 implements full support for Windows 10: http://forums.aida64.com/topic/2920-aida64-v530-is-out/ Regards, Fiery
  16. Fiery
    Does your Windows user have the right to write files into the installation folder of AIDA64? I suppose that may be the problem. Open the installation folder of AIDA64, and check if there's a new file created there called PKEY.TXT, after you've entered your product key. As for the temperature readings, that issue is not related to whether you're running a trial version or not. Make sure that your Windows user has got administrative privileges. Without such privileges a Windows software like AIDA64 cannot perform low-level hardware access, and without low-level hardware access it's not possible to access sensor chips or read chipset or GPU information.
  17. Fiery
    Thank you for letting us know about the resolution
  18. Fiery
    Yes, but as you can see, none of those match or even get closer the values you provided above (66 Celsius). The first column is the Motherboard temperature, the second is the CPU temperature, and the third is the Aux temperature. What AIDA64 does on your motherboard is exchange the Motherboard and Aux temperatures, but it doesn't alter the CPU temperature reading.
  19. Fiery
    AIDA64 stores the LCD layouts and all other settings in the AIDA64.INI file. That's all you have to back up.
  20. Fiery
    You need to download the Strike7 SDK from: http://www.madcatz.com/downloads/strike7/ Then copy the 32-bit Strike7API.dll file from the latest Strike7 SDK ZIP package into the AIDA64 installation folder. In the Strike7 SDK ZIP package you can find that file in the API/Win32 folder. Let me know if you did that, and it still fails to work.
  21. Fiery
    Thank you. Those registers do not seem to contain a valid CPU temperature reading though. Can you please start SuperODoctor, close it, and then create and copy-paste a new ISA Sensor Dump? Maybe SuperODoctor reconfigures the sensor chip. BTW, we haven't touched the CPU temperature measurement code about your motherboard, so both old and new versions of AIDA64 should display the same reading. The only difference may be due to another software possibly reconfiguring the sensor chip, or a BIOS update re-adjusting something about the sensor chip.
  22. Fiery
    Please avoid posting a single issue into multiple topics. I've replied in your other topic.
  23. Fiery
    Note that certain USB devices fail to report the connection speed properly. What is the USB device in question? Please avoid posting a single issue into multiple topics. Please keep posting in English. This is an English language forum, and I'm afraid we cannot speak Russian. Thanks, Fiery
  24. Fiery
    Yes, that's an intriguing idea, and kind of similar to my idea #2 above Problem is: we've checked it on a BlackWidow Chroma keyboard, and it doesn't seem to work all that well. The main issue is that the keyboard matrix is not a regular matrix, so it's not like a real matrix of LEDs. You would have to look at the keyboard from several meters of distance to make up the displayed characters, and even then it's not just a simple glance. It would be much easier if the keyboard buttons were arranged in a regular matrix, like this: Fortunately the rest of the ideas seem to work fine, so all we have to do now is implement the whole thing in a new hardware monitoring module
  25. 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. Using that data we can see what's going on about the various temperature inputs provided by the sensor chip of your motherboard Thanks, Fiery
×
×
  • Create New...