Fiery

Yes, feel free to post them all into this topic We'll then add them to the AIDA64 monitor database.

Thank you for the feedback.

AIDA64 follows industry standards by reading SMART attributes (incl. disk temperature attribute) via standard Windows API calls just like any other Windows software. In case WD implemented the power-saving features (the head parking) in a way that the head unnecesserily moves everytime the SMART attributes are read from the drive, then IMHO it is a serious hardware implementation flaw that should be fixed in a form of a firmware upgrade for the affected WD Green drives. However, the LCC can be minimized if you could adjust the polling frequency for the SMART disk temperature readout, hence we've decided to implement a new option in AIDA64 to help you fight the LCC issue easier. The polling rate is default 20 seconds, but you can raise it all the way up to 3600 seconds (1 hour) in 1 second increment. You can adjust the disk temperature polling frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Note: If you raise the polling frequency too much, AIDA64 will be able to detect a potential disk drive overheating situation much later than when it actually happens, so make sure to try to find a balance between 20 seconds and 3600 seconds Thanks, Fiery

I'm sorry for the delays. It took us a while to come up with a -- hopefully -- proper fix for the startup delays, and to thoroughly test it on multiple nForce RAID configurations. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented support for the new JMicron RAID drivers in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the dumps. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the dumps. We've tweaked a bit around the fan RPM measurement on Asus H55 and P55 boards. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented serial number indicator when multiple drives found with the same disk model ID. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1219sdk6ngm0yczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you. We've checked it with v3.06 drivers, and disabling the "Allow Program to Force Itself to Foreground on Display" option in the Logitech LCD Manager doesn't work at all. It must be a bug in the Logitech LCD Manager, so please report it to Logitech, so they can fix it.

Now we've tested it again with AIDA64 v1.50 and Rivatuner v2.24c, and having set the polling frequency in both applications at 1 sec, everything is updated at the desired 1 sec frequency. I'm not sure what may cause the 5 sec update frequency on your system

No, those configuration values are not written to the Registry.

What I meant to ask is: try to enable the "Time" item in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications, and then in the Registry watch if the STIME item is really updated at the rate you configured for the External Applications feature (which is 1 second in your case). That way you can verify if the Ext.Apps feature update frequency works as expected.

We currently have no plans about a fan control feature for AIDA64. Regards, Fiery

Have you verified the STIME (entry in the Registry / SensorValues) update frequency with AIDA64 v1.50? We haven't changed anything around the update frequencies between AIDA64 v1.20 and v1.50, so I don't have an answer to your question at this time

The triangle is not there on your latest screen shot, but it was there on the previous screen shot. You need to enable the Registry feature in the Preferences (Hardware Monitoring / External Applications), and then you can expand the AIDA64 key to see the SensorValues key (which is a child of the AIDA64 key).

That shot clearly shows that the AIDA64 key has child keys (the little triangle there). Just expand that to see the SensorValues key.

Have you tried to expand the "AIDA64" key in the Registry? The SensorValues key should be a child of the AIDA64 key

The Registry checking was about the update frequency issue, not for the Alerting issue. Maybe you got confused, or you've started confusing things now

You mean you'd like AIDA64 to display data collected by other software?

Yes, AIDA64 implements better support for SSD drives than any Everest versions But it cannot fix the lack of temperature sensing logic implementation in OCZ Vertex 2 drives

AIDA64 (the motherboard sensor chip actually) cannot and won't check for power connection, it only senses the RPM wire.

Next time it happens, when after the configured alert items disappear, can you please check out on the Sensor page whether the fans in question can be detected spinning by AIDA64? Also, when that happens please check the AIDA64.INI file, if the configured alert items are still there or not. I suppose it may be because for whatever reason AIDA64 stops being able to find the watched fans at its startup, so it treats them as unconnected fan headers Thanks, Fiery

AIDA64 shows the MTU size configured for each network adapter. In case Windows' network interface layer overrides the MTU size, then Windows may reflect the wrong MTU size for the network adapter(s). Since AIDA64 uses the standard network interface (MIB), when the MTU size is unexpected, then it's the fault of Windows network interface actually

When those items are not there in the Preferences, are those fans spinning then? Not spinning (0 RPM) fans will not be collected by the AIDA64 Hardware Monitoring module, because AIDA64 treats "0 RPM" fans as unconnected fans, hence it will not poll them. But when you have a fan already configured, when it stops AIDA64 will of course fire an alert.

1) Update Frequency: we've just verified the update freq for the AIDA64 External Applications feature, and it works as expected, we haven't found any discrepancies. In case Rivatuner handles something wrong, then I suppose it's a bug in Rivatuner and not in AIDA64. You can actually verify the update frequency of the Ext.Apps feature if you enable the Registry support (AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications / Enable writing sensor values to Registry), enable the Time item there, and then check out the published STIME value in the Registry at HKEY_CURRENT_USER\Software\FinalWire\AIDA64\SensorValues. 2) Fans: I'm not sure if I understand it, so please clarify. Do you have fans connected and spinning fine, but those fans sometimes disappear from the list of Alerting items in AIDA64 / main menu / File / Preferences / Alerting? Or you have the AIDA64 Alerting feature properly configured for those fans, but the actual alert is not fired when one of the fans stop spinning? Thanks, Fiery