Fiery

AIDA64 can provide information on your PSU only if the PSU is capable of providing such measurement data. As far as I can tell from the XFX website, your PSU is not capable of measuring the mentioned data. Regards, Fiery

1) Is the GPU load all zero for only one of the GPUs, or for both? 2) What version of AIDA64 are you using? 3) What version of ForceWare drivers do you have installed? 4) What kind of operating system do you have? 32-bit or 64-bit? Thanks, Fiery

Thank you. I'm afraid it looks all fine, so the problem must be somewhere else. My best guess is that the monitoring module of AIDA64 collides with another application, process or service running in the background. Do you think you have any other software running in the background that may also poll sensors or the GPU? Such as AI Suite, Rivatuner, or such?

Can you please check what bit depth do you use for your Windows Desktop? Is it the default 32-bit?

That's an issue we've never seen before, it's quite interesting. Did it start to happen after you've performed an AIDA64 upgrade? Or did you change a hardware component and that triggered the issue? Thanks, Fiery

With the GPU monitoring enabled, 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. Thanks, Fiery

Thank you for the report, it's perfect in German. Try to disable GPU monitoring by right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules --> GPU. If it doesn't help, try to disable the other HWMon Modules as well, one by one, and see if any of them cures the issue. If none of those helps, and you've got Asus AI Suite installed, try to uninstall it, and see if it helps.

Thank you for the dumps. I suppose the issue may be the fact that your system has multiple PCI bus segments. We'll have to come up with a workaround for such situations. If possible, please export the following Registry path out to a .REG file: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI Rename the .REG file to .TXT, and attach it to a post. Maybe, but I'm not sure. It may worth a try. But please do the Registry export under Windows 7 or Windows Server 2008 R2. Thanks, Fiery

You can move the file to your flash drive manually, and it will be used by AIDA64 running from the flash drive.

We'll have to check how can that be rendered. Most likely it would be no problem to render it on the SensorPanel and on most external LCDs, but it may be difficult to achieve it with the HTML based LCD modules (Logitech Arx, RemoteSensor). We'll also have to check how can we combine that effect with the existing 3D effect.

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

AIDA64 is supposed to save the entered product key into a file called PKEY.TXT in the folder where you start AIDA64 (via its main executable module called AIDA64.EXE) from. Check if the user running AIDA64 has the right to write to that file on your flash drive. Regards, Fiery

Thank you for the feedback

Before the development of the Logitech Arx and RemoteSensor modules, AIDA64 already had a facility called External Applications. Many users use those tricks (like shared memory) to export the sensor values AIDA64 measures and get the values processed by their own software or solution. It is just as legal and fine as connecting to the AIDA64 RemoteSensor HTTP server with a native mobile app that you would develop. The only trick is: we cannot provide technical support for that app, since it's not our development, so you would have to deal with the users questions in the new forum topic you would maintain. We do however will support your efforts to make sure the RemoteSensor HTTP server can communicate with your app properly. BTW, it's a great idea to develop a native app. We're looking forward to giving it a try

That's absolutely incredible It looks great, and I can see that you've put a lot of efforts into producing custom graphic material.

Thank you, and Happy Holidays!

You can find the improved hot-plug device support in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta

Thank you for your help. Meanwhile, AquaComputer was super kind and sent us a set of gadgets to help our progress on the development of Aquastream XT and MPS support for AIDA64. We're already working on it, and will notify you here on the forum, and also in email once it is ready

I'm afraid command-line arguments will not work when AIDA64 is already running

For CDs 1x = 153 kiloBytes/sec. You can also refer to this page: http://en.wikipedia.org/wiki/CD_and_DVD_writing_speed Regards, Fiery

We'll work on that soon We'll also work on the ability to show not only current (actual) values on the SensorPanel and LCD, but also average, minimum and maximum values.

The "Super Business Edition" has already come out over a year ago We however simply kept the Business edition, and added the additional features. So now AIDA64 Business is the complete edition having all features of all editions in a single package: http://www.aida64.com/products/aida64-business http://www.aida64.com/compare-aida64-features

Thank you for the feedback As for $AIDAVERSION, are you looking for a string like "AIDA64 v5.00.3308" or "v5.00.3308" ?

I'm afraid we're not interested in hacking into the Corsair Link framework, like what SIV does. It would just cause collisions and unexpected, potentially fatal issues, as described e.g. here: http://forum.corsair.com/forums/showthread.php?t=133312 We'll have to wait for the 2nd generation Link implementation that Corsair promised to deliver with full 3rd party applications support and a proper SDK. Regards, Fiery

With HDD/SSD temperatures we'll revert back to the old scheme about hot-plug device support in the next AIDA64 beta update.