Fiery

You're right about those points. We'll work on the Alerting module to make it more flexible and more usable in the upcoming weeks. I'll let you know in this topic once the "facelifted" Alerting module is available. Thanks, Fiery

Do you mean when the user on the remote computer receives your message, he presses the Reply button, and then AIDA64 closes the message window without enabling him to type in his reply? Or when he presses the Reply button, AIDA64 crashes and the whole application closes? Thanks, Fiery

I'm glad it worked out Thank you for letting us know.

Software running under Windows have no control over the order of the System Tray icons. Windows places them there, and it decides the order. Regards, Fiery

I'm afraid it's now Intel's task to fix their drivers. We keep reporting them the bugs we find in their Rapid Storage RAID drivers, but due to the way their huge corporate is organized, it takes multiple bug reports to start things rolling in their development labs. So you'll also need to report this to them. You can refer to the CSMISAS interface that we (and also other software like HD Sentinel, HWiNFO32) use to enumerate individual drives of Intel RAID arrays. As for connecting the DVD burner to the JMicron SATA controller: that would definitely help. Just make sure to switch the JMicron controller to IDE mode (not RAID or AHCI mode) in the BIOS Setup. Then you can re-enable the RAID SMART support in AIDA64 -- but make sure to do some more test runs with that setting too.

You're right, that is not normal. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Thanks, Fiery

100 MHz clock is reported because at idle your GPU is running at PCI Express nominal clock speed (100 MHz) to save power. It is a common power management technique of nVIDIA IGP GPUs. 1) That is a pure coincidence. All modern GPUs are equipped with a 400 MHz capable RAMDAC, but that doesn't mean it has any relation with the GPU core clock at all. 2) GPGPU device properties reflect the capability of the GPU, and not the actual speed it is running at. The actual speed is 100 MHz at idle, as reported on the GPU page. 3) IGP chips (like nVIDIA Ion) usually use the system memory as frame buffer and texture memory, and so it makes no sense to display memory speed or memory properties on the GPU page. Instead, AIDA64 shows the system memory type and clock rates on the Computer / Overclock and Motherboard / Motherboard[/b] pages. You can also have the system memory clock speed and timings displayed on the Sidebar Gadget. Regards, Fiery

I suppose this is once again caused by the buggy Intel RAID driver Please try to disable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability, and try to burn a few DVDs in test mode. Make sure to use the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip Let me know how it goes. Thanks, Fiery

Please try to re-enable SMART operations, but disable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability. Make sure to use to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip Let me know if it helps to eliminate the lagging. Thanks, Fiery

Thank you, we'll do test runs, but in order to do so, we need to narrow it down a bit. Please let us know more about the system in question: 1) CPU model, motherboard model 2) Storage controllers in use 3) Any RAID arrays defined? If yes, then exactly on which controller, how many drives, what drive models? 4) Any external disk drives connected? (USB, FireWire, eSATA) 5) On which controller do you have the DVD burner connected, and what DVD burner is that? 6) Video card(s) model Thanks, Fiery

Well, that's a hard question actually. In theory, the special temperature readings should be available by reading simple Embedded Controller registers, without any further software aid. But we suspect the readings are zero until a software enables them -- and that software may just be the Thermal Radar. So what I'd like to ask you to do is: install Thermal Radar, start it, check the readings in there, close it (you don't need to actually uninstall it), and then launch AIDA64, and issue the Embedded Controller Dump. You may also want to check the temperatures on the Sensor page after the EC Dump, since if our theory is right, they will be there. In case our theory fails, the other theory may be that you need to have Thermal Radar installed and running to let 3rd party software (like AIDA64) access the special temperature registers. We'd love to personally test both theories out in our labs, but we unfortunately have no Sabertooth P67 mobo in our "test fleet", but only a vanilla P8P67 that offers no such special temperature readings. Thanks, Fiery

Thank you. For some reason all special temperature registers are zero in this case. Please try to launch Thermal Radar, check the temperatures there, close it, and issue a new Embedded Controller Dump. Maybe Thermal Radar initializes the Embedded Controller to enable the special temperature readings. Thanks, Fiery

AIDA64 already supports DIMM TS temperature sensing for memory modules. However, you need to enable that feature in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. In case it doesn't work on your system, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full), and copy-paste the full results into this topic. Thanks, Fiery

Thank you for the feedback

1) Please copy-paste the full content of the Computer / Sensor page into this topic. 2) Also, 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. Thanks, Fiery

Using the beta I linked, please copy-paste the full content of the Computer / Sensor page into this topic. Also, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

Thank you for the feedback

I'm sorry to hear about your issues about the purchase. While I cannot say that we don't have refused orders, in most cases they're caused by either suspicious clients, or simple user mistakes (e.g. failing to enter the proper security code). I'm not sure why Cleverbridge was unable to fix it for you, but what I can tell you based on our previous experiences: they're a much better company than their competitors we've previously dealt with. I'm not gonna say any names, since I don't mean to bash any other e-commerce providers. In case of such an issue to happen in the future (if you decide to give AIDA64 another chance), you may want to try paying with PayPal on Cleverbridge. Most of our individual (non-business) customers prefer to pay via PayPal, because they reckon it is more safe than direct credit or debit card payment methods. If you use PayPal, you can still pay via credit card, but the actual payment process is performed by PayPal instead of Cleverbridge. Regards, Fiery

Thank you for the data. We've fixed the incorrect voltage readings. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

Asus Sabertooth P67 is fully supported by the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Thank you for the screen shot. We've implemented support for the new temperatures. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip 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 data. We've fixed the sensor readings for your motherboard. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1339qs1d0nycgrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

You can use the Sensor Icons feature (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Sensor Icons) to display sensor values on System Tray icons. Regards, Fiery

Yes, AIDA64 configuration settings are completely OS independent. Regards, Fiery

Nothing changed about startup configuration between AIDA64 v1.50 and v1.60. I think the problem is that you try to hide the main window, and also you want to hide the AIDA64 System Tray icon. You can only do one of them, but not both combined. That limitation is because if you could hide both the main window and the System Tray icon, then you may end up "losing" AIDA64 -- not being able to restore the application in any ways.