Jump to content

Fiery

Administrators
  • Posts

    11546
  • Joined

  • Last visited

  • Days Won

    489

Everything posted by Fiery

  1. Please avoid posting multiple topics for a single issue. I've locked this topic, and replied in your original topic. Thanks, Fiery
  2. Please avoid posting multiple topics for a single issue. I've locked this topic, and replied in your original topic. Thanks, Fiery
  3. Please let us know what exactly the problem is about AIDA64. And in the future, please avoid posting multiple topics for a single issue. I've locked your other topics. Thanks, Fiery
  4. I'm sorry for the late response. 1) We'll add the pump RPM reading in the next AIDA64 beta update. I'm afraid we have no information on how to read the pump power value. We have a theory about which register may be used for that, but we would need a bit more data to verify our theory. Can you please post two different Aquaero Dumps, made at different pump power settings, like 40% and 60% or so? For both dumps please indicate the actual pump power value set, and also the pump power value as shown in Aquasuite. Thank you in advance! 2) It may be due to a temporary USB HID communication issue, or due to a collision between Aquasuite and AIDA64. Please try to close Aquasuite, and check if it makes it any better. Thanks, Fiery
  5. We're working on it
  6. The splash screen is only displayed when you've got no items on your LCD configured in AIDA64 Preferences, or when all the items are hidden. If you've already got a few items on your LCD (which I suppose you do), then try to select all items, and push the Hide button to hide them all at once. Then push the Apply button on the AIDA64 Preferences window, and the splash screen should be displayed. If you noted down the resolution to use, select all LCD items again and push the Unhide button to show them all at once.
  7. In case the Arx framework and/or the Arx Android app has some connection or application enumeration issues, then it's quite normal to see the issue on all phones you've got, not just on one of them. And as I've mentioned above, you may want to temporarily switch to the AIDA64 RemoteSensor feature which offers virtually the same benefits that Arx provides. Without the bugs, of course
  8. Thank you for the feedback. I'm afraid we have no information on how to read VRM temperature on your motherboard, so we cannot implement that at this time As for the missing voltages, we can check them, but please let me know exactly which voltages are missing, and what are their current configured values (or what values does the UEFI Setup measure for those rails). Vcore is measured following MSI's spec that they provided for us. If it doesn't provide meaningful values, then ignore it and focus on the CPU VID reading instead.
  9. I'm afraid the error is still not on our end, so we cannot fix it from AIDA64
  10. Thank you for the dump. Is this the one with the 7-inch touchscreen LCD? If yes, then I'm afraid it's not supported by AIDA64 right now, since we've got absolutely no information on how to handle that LCD. Do you have a software that could handle that? Apart from the Soundgraph iMON package?
  11. I've replied you in email. Regards, Fiery
  12. It should already work with the latest beta http://www.aida64.com/downloads/latesta64xebeta
  13. It depends on the actual protocol your LCD uses. In theory, AIDA64 is well prepared to support virtually any LCD devices that can display a bitmap image directly. It already supports over 50 different LCD protocols, and a wide range of connection options, including USB, WiFi, LPT (parallel), COM (serial). It would be important for us to understand what exactly needs to be done to push a bitmap image into your LCD screen, so please share any technical detail you've got on that. If it uses a proprietary protocol that you wouldn't wanna share with others, then please drop me a private message with your email address, and we'll continue discussing this in email. Thanks, Fiery
  14. We've checked it, and Winamp doesn't seem to support passing the currently played track title to other applications BSPlayer has something like that. But I'm not sure how useful would it be to show such details during a video playback. Song would be a different matter, but I suppose BSPlayer is used mostly for video playback?
  15. Please avoid posting a single issue into multiple topics. I've replied in your other topic. This topic is closed. Regards, Fiery
  16. I'm sorry, but what "theams" means? Regards, Fiery
  17. Ordering of System Tray icons is done by Windows itself. AIDA64 cannot use any ordering on them. Regards, Fiery
  18. Preferences settings are stored in the AIDA64.INI file that you can find in the AIDA64 installation folder. You can also use the Export button on the LCD Items page of the Preferences to backup your LCD settings.
  19. Which application do you use to play music?
  20. No problem, and thank you for letting us know about the root cause of the ads issue
  21. If you mean this site as this forum, then here there's no ads at all If you mean the main aida64.com website, then the ads are not that ubiquitous. The reason you may find yourself bumping into them all the time may be because you mostly visit the download page where the most ads are But if you navigate to other parts of the website, you'll see that ads are actually quite scarce.
  22. CPU Package temperature is read directly from the processor, as an absolute degrees Celsius temperature value. No TJMax is applied on it, no conversion is made on the readout. As it is read, it is displayed. Core temperatures are also read directly from the processor, as a relative value (distance from TJMax), in degrees Celsius. The TJMax value is read directly from the processor, and the core temperatures are calculated as: TemperatureResult = TJMaxValue - TemperatureReading If there's a discrepancy between the 2 different measurements, then the only one knowing the cause is the manufacutrer of your processor, Intel. We don't convert the values or alter them in any ways. All components of the formula is read from the processor, so in case the result seems wrong, one of the values provided by the processor itself must be wrong. But we have absolutely no control over that, and we shouldn't have it. BTW, especially on low-power Intel processors (like Broadwell-U and Broadwell-Y), the CPU tends to start throttling even when the core temperatures reflect a value 5 or more Celsius lower than TJMax. One conclusion might be that the core temperature measurement subsystem (Intel DTS) isn't all that accurate, and one shouldn't count on it to provide 1-Celsius or sub-Celsius accuracy Regards, Fiery
  23. I'm glad it worked out We've got many bug reports of missing Logitech DLLs, and in 99% of the cases a driver reinstallation fixed it up. Strangely, sometimes it has to be done multiple times to make it work
  24. It is Logitech's DLL, part of the Logitech G-Series driver package called LgLcdApi.dll. Try to reinstall the drivers, it should help.
×
×
  • Create New...