Fiery

Do you have any tools, made by Lenovo or a 3rd party, that could display the fan RPM? Or maybe you can see that reading in the BIOS Setup? Just because the fan has got 3 wires, it doesn't mean the RPM is really monitored by the onboard Embedded Controller chip.

The mentioned new AIDA64 beta update is available for download 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

We've implemented support for Enermax Digifanless USB sensor protocol 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

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic. Under Windows 10 you may have to enable the statusbar first in main menu / View.

Yes, both is possible, as long as we can easily find the window and read the window title (case #2), or when it's easy to understand/interpret the shared memory content (case #1). With shared memory a documentation would help a lot

The original DPS-G is fully supported by AIDA64, but we're not sure if Thermaltake uses the same protocol for the newer DPS-G PSUs. You have to try AIDA64, and you will see whether it works. If it doesn't work, we can try adjusting the existing code to suit the new PSU family. I have to stress the fact that I cannot make actual promises about this: PSU sensor support is a difficult issue that we may or may not be able to solve. In most cases manufacturers do not implement an API or SDK, and refuse to provide the necessary documentation on the PSU USB protocol. We may still be able to figure out what to do to read the sensor values, and in many cases we can indeed do it.

It should be there. http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html

Thank you for the feedback. I understand the issue of potential firewall blocking our network access, but it shouldn't lead to crashing AIDA64. In fact, the relevant code of AIDA64 uses standard Win32 internet API calls, and it's well protected against fatal errors and exceptions. I suppose the protection against that malware is so strong that it causes the underlying internet API crash or return some garbage data to AIDA64. BTW, I've removed the ....aida64.com URL from your post, I hope you don't mind

I think you could see the same issues on the HW Monitor page of the BIOS Setup. Which would indicate this is actually a problem with the onboard sensor chip that simply cannot measure RPM for fans connected via a splitter cable.

Thank you. It seems the external IP address detection causes the crash on your system. It's a strange anomaly, we haven't yet seen such an issue before. Maybe you've got a firewall software on your computer that prevents AIDA64 from detecting the IP address?

Thank you for the test. I've sent you another private message Let's hope at this time we can get to the bottom of this.

The issue will be fixed in the next AIDA64 beta update due in a few days from now Regards, Fiery

Thank you, but we've got 2 major issues with that. First, you quote the option being named "RemoteAPi: Deprecated Api" -- it doesn't sound like an active development API Second, using a HTTP client for such purposes would be a big overhead and we wouldn't want to go down that path. We would be happy to interface through a DLL API though, if there's one.

It is possible, as long as you can come up with a detailed specification on how to handle the proposed DLL. E.g. calling convention, string type (Ansi or Unicode), image format (raw bitmap is okay? or PNG? or both?), picture parameters (24-bit RGB? or 32-bit ARGB? or both?)

As far as I know, there's no JDownloader API that a 3rd party application could support, and there's no SDK either. If there's one, please let me know where can we check it out Thanks, Fiery

If you use classic Intel SATA RAID, then AIDA64 will be able to show RAID members just fine.

I can't promise to deliver a working solution in a few days, but we'll do our best to make it happen soon

Thank you for the info. We ordered a Corsair RMi PSU today, to help us figure out how the RMi protocol works. I'll post updates on our progress into this topic.

Thank you for the data, and apologies for the late response. In the past few weeks we've been trying to figure out how the Digifanless HID protocol works, but without an actual test hardware we've failed to solve it. So we had to order a Digifanless PSU today. Hopefully once it arrives, we'll be only a few days away from finding out how it works and implement the protocol in AIDA64. I'll post updates to this topic.

If it's possible, please discuss such traces and reverse-engineering matters in private message or email.

Thanks a lot! I've just sent you a private message about this.

Upgrading to Win10 could raise new issues, but the particular issue this topic is about was already there with Win7, so Win10 doesn't make a difference now. And please try to be more patient about certain questions

Thank you for the test. So you mean there was no new file created on your Windows Desktop?

Do you have the Corsair RM PSU connected directly to a USB port header or an actual USB port? Or you have it connected to a Corsair Link Commander device? If the former (direct USB connection), then please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic. Please make sure to use AIDA64 latest version (5.50) to perform that dump. Thanks, Fiery

Thank you for the test. This seems to be a tough nut to crack If it's possible, please do the following: 1) Upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta 2) After upgrading to this new version, restart Windows to finalize the upgrade 3) Go to AIDA64 installation folder, and a create file (could be an empty file) named ENABLE_HWMONINIT_LOG.TXT 4) Start AIDA64, go to Preferences / Hardware Monitoring / Sensor Icons 5) If it crashes there, then please open the new file that was placed on your user desktop named hwmoninitlog.txt in e.g. Notepad. Scroll to the end of the file, and copy-paste the last few lines into this topic. Those lines should tell at exactly which point the sensor item enumeration code crashes. Thanks, Fiery