Fiery

Thank you for your support

Have you checked that AIDA64 auto-launch is still disabled in Logitech LCD Manager? Alternatively, you can have the option in AIDA64 ("Load AIDA64 at Windows startup") disabled, and let Logitech LCD Manager to launch AIDA64 at Windows bootup.

That's a normal to have the user associated to both those groups.

That solved the APIC clock measurement. It should solve the clock and multiplier issues too

On Windowx XP and Windows 7 systems we can see only a single entry. Do you use Windows 7 or Windows Server 2008 or Windows Server 2008 R2? Your computer is not logged into a domain, is it?

The problem is due to AIDA64 not being able to measure APIC clock because you use an ACPI table virtualization patch. Such patches are used by Windows activator utilities to emulate a SLIC table. You need to have a legal Windows 7 copy to get APIC clocks back.

AIDA64 Business Edition supports CSV, XML and SQL database reporting. AIDA64 Extreme Edition only supports TXT, HTML and MHTML report formats. Regards, Fiery

Apparently since Windows Vista such feature is no longer available in the Task Scheduler API. So we'll remove the double-click hint in the next AIDA64 beta release. It's normal. We chose not to display system tasks, because it would make the list of scheduled task very long, and would make finding non-system tasks rather difficult.

We've checked AnyDVD and CloneDVD, and they protect product keys with encryption. We'll check the rest soon.

1) Nero and Photoshop is already supported. But modern software products may encrypt their license keys, effectively preventing AIDA64 to collect them. 2) We'll check the rest of the requested software 3) Audio codecs are enumerated via acmDriverEnum Windows API call. Video codecs are enumerated via ICInfo Windows API call. I guess K-Lite fails to register the installed codecs properly, and so those API calls do not see the installed codecs. Regards, Fiery

Are you sure you have any opened files? Please note that in that case "opened" means the file is accessed from across the local network.

Yes, it's normal. Your video adapter lowers its clocks when you're not running a 3D application (like a 3D game). You can use AIDA64 System Stability Test to stress your system and check if it is overheating under heavy load. Go to AIDA64 / main menu / Tools / System Stability Test, enable only the "FPU" test, and press the Start button. Watch whether the lower graph (Throttling) shows any non-zero percent activity.

Thank you for the feedback. Regards, Fiery

We've fixed that in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1611kb6wjk2msdzip 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 fixed that in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1611kb6wjk2msdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1611kb6wjk2msdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

You're right, listing scheduled tasks may not work in some cases under Windows Vista and Windows 7. We'll fix that. I'll drop a message into this topic once a fixed AIDA64 build becomes available. Thanks, Fiery

Yes, we do have plans about such new hardware monitor items. I'll drop a message into this topic once the requested feature becomes available in AIDA64. Thanks, Fiery

1) Does the clock measurement in AIDA64 work properly if you close CPU-Z and any other software that also measures CPU clock? 2) Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. Thanks, Fiery

Please note that the shared memory content doesn't have a fixed length, so the number of characters is dynamically changed depending on the shared memory content. We indicate the end of string by the NUL character. If you use a char* or PChar sort of variable, then it should be easy to handle a zero-terminated string.

NUL character is used to indicate the end of the string.

We could display that in many cases (not just with CrossFire/ULPS), since there're numerous pitfalls while performing hardware detection. And as I've stated above, our workarounds work in most cases, just not in all cases. It's not easy to decide in which case shall we display a warning.

Please stop blaming us. I've further explained in the other thread where you posted similar comment. This thread is closed.

Please choose your words more carefully. It's not our fault that AMD implemented the ULPS feature in a way that causes issues to 3rd party software vendors like us and many other guys who work on diagnostic and monitoring software. We've talked to a software/firmware developer who works close to AMD about this, and even he admitted the way AMD implemented ULPS in their drivers is very unwise. It simply turns off the secondary GPU when it's not used, and a simple MMIO readout -- a standard Windows method to read registers from various type of hardware -- causes a hard lock on the computer. Please note that I'm talking about readout, not writing to any registers. If you know what MMIO is, how Windows kernel drivers work, and what should happen when a system component goes to sleep, then it should be obvious to you that how ULPS works is clearly unacceptable. We've tried to implement workarounds, in fact, we did implement 3 different workarounds to overcome the ULPS nightmare, but they don't work in some cases. If you want to blame anyone or ban anyone, it should be AMD Catalyst developers, and not AIDA64 or any other 3rd party applications. BTW, nVIDIA wisely invented and then keeps maintaining, improving and extending a special interface called NVAPI, that allows 3rd party developers to safely communicate with the GPUs, including SLI configurations. It's a fast an efficient way to access the GPU, to measure clocks, temperatures, voltages and other properties. AIDA64 implements support for NVAPI to avoid any potential issues that would be caused by direct communication with video hardware. AMD on the other hand implemented their own solution called ADL (in their Catalyst driver suite), which is very slow and inefficient way of talking to their hardware. We simply cannot use that in AIDA64, because it would make it impossible to read clocks, temperatures and voltages in real-time, with a frequent update period. If AMD would have implemented ADL properly, we could use it to avoid ULPS issues. Don't get me wrong, we love AMD's video adapters. We just hate their drivers and the way they implemented ULPS. And it's quite frustrating when someone puts the blame on us. That's all.

Plain old ASCII