Fiery

What motherboard, video card(s) and Windows version do you have?

I was just asking because we've revamped the SMTP module to unlock support for Yandex and other mail services in AIDA64 v5.97. So you need that version or an even newer one to have proper SMTP support with SSL/STARTTLS.

Do you have an Asus motherboard?

We're not planning to implement such a feature in our Android app. But since the current report layout is quite clear and easy to post-process, it's quite possible to write a script that would convert it to a HTML file with the layout of your choosing.

Please 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. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

We're not that skilled in using PowerShell, but maybe someone else can help you out reading this.

Are you using the latest AIDA64 version of v6.00?

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. Thanks, Fiery

Please upgrade to AIDA64 v6.00 first. If the issue persists, 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. Thanks, Fiery

You need to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability to enable CLC support.

I guess the issue is due to lack of permissions. In other words, the update process (AIDA_UPDATE.DLL) has no rights to overwrite the old AIDA64 main binary file (AIDA64.EXE) and replace it with the new one. What you can do is either dig down deeper and find out why the update process has no rights to do that, or download the AIDA64 v6.00 portable ZIP package, and extract it to the existing AIDA64 installation folder (C:\Program Files (x86)\FinalWire\AIDA64 Extreme). Let it overwrite any existing files. Your settings and your license will both be retained that way. If you're concious about keeping your settings, I recommend you to periodically backup the AIDA64.INI and PKEY.TXT files that you can find in the AIDA64 installation folder.

What kind of POS device are you using, and what protocol did you select in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / POS?

No, it's not possible, especially on iOS.

All measured voltages are listed on the Computer / Sensor page. But please note that not all motherboards are capable of measuring DIMM voltage or QPI voltage.

What we've just rolled out with AIDA64 v4.60 is only the first wave of new LCD and VFD devices. If you consider interface, protocol, controller and all other variables, there are literally hundreds of different LCD/VFD devices out there. We're already working on a number of new devices (Acer Idea 500, AX206-based firmware-hacked DPF, ct-Mausekino, Cwlinux, Futaba MDM166A, picoLCD, SoundGraph iMon UltraBay LCD, Sure Electronics, Trefon, Yoctopuce, etc) that will be added during the next few weeks, and then a lot more is coming. We're collecting ideas on which displays to support next, so feel free to let us know what display you've got, or what display you want to see being supported by AIDA64. Make sure to state display manufacturer, display model, interface (USB, serial, parallel, I2C, etc), and if possible, show us the device you've got by posting a link to the product page or a hardware review. If your unsupported LCD/VFD uses USB connection, please post a USB dump of it: right-click on the bottom status bar of AIDA64 v4.60 --> System Debug --> USB Dump. Copy-paste the full results into this topic. Regards, Fiery

I guess your SMTP settings are incorrect.

The above mentioned beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta

We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've contacted Asus and asked them whether it's possible to access the OLED screen of their device directly. We'll see what they have to say about this... I'll let you know in this topic once we have an update.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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. I can give you a proper answer after studying that dump. It's because the delay occurs either somewhere in the sensor code, or inside the Odospace API. Thanks, Fiery

State #0 should display the state where the range is zero, so it shows for example 0 RPM or 0 degrees Celsius. State #15 should display the state where the range is at its maximum. So it shows like 5000 RPM (if your cooler can spin up to 5000 RPM) or 100 degrees Celsius (if you deem your thermal readings will never exceed that value). All the other states should show an intermediate step. Since State #0 = 0%, and State #15 = 100%, for example State #5 should show the range as if it was 33%.

Please let us know more about the issue you're facing with AIDA64. Please also note that this is an English language forum, so please post your questions in English.

We've added support for Samsung SPF Digital Photo Frames. It works with the following models: SPF-72H SPF-75H SPF-76H SPF-83H SPF-85H SPF-85P SPF-86H SPF-86P SPF-87H SPF-105P SPF-107H 700T 800P 800W 1000P 1000W The following models are not supported at this time: SPF-72V SPF-83V SPV-105V The following models do not support Mini Monitor Mode, and so AIDA64 cannot use them as an external LCD: SPF-71E SPF-71ES You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Samsung. For the most stable operation it is recommended to uninstall Samsung Frame Manager and Mini Monitor drivers, and install our own Samsung SPF LibUsb driver instead: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip Our driver can directly communicate with the device, without interfering with Samsung's drivers or the Frame Manager software. Alternative solution is having the appropriate Samsung SPF Windows drivers installed (part of Samsung Frame Manager software), but that usage scenario is not guaranteed to work properly. Notes: - If the device disconnects after a few seconds, enable the option Send keep-alive packet in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Samsung - AIDA64 will switch the device from Mass Storage Mode to Mini Monitor Mode if necessary. That transition could take up to 10 seconds. When the switch takes place, and there's Samsung Frame Manager software installed, Windows Aero may get disabled by Samsung Frame Manager's Mini Monitor feature - AIDA64 has a built-in facility to prevent collisions with Samsung Frame Manager. In case it fails to work, and AIDA64 frames collide with Samsung Frame Manager frames, then terminate the process called "sam_controller.exe" via Windows Task Manager, or uninstall Samsung Frame Manager - If Samsung Frame Manager is installed, but its Mini Monitor feature is not used, it's recommended to disable the Samsung Monitor device in Device Manager / Display Adapters. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Futaba MDM166A VFDs and Yoctopuce OLEDs are also supported now by the latest AIDA64 beta. Regards, Fiery

AIDA64 has never implemented a SHA2 benchmark...

Thank you. I guess the issue is due to the number of fans your card has got. Based on the product photo we assumed it has only got a single fan. Maybe Fan 2 in your card's case reflects the pump RPM for the onboard liquid cooling?