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

Of course you can use that feature. So if you set it to once a day, such users who log on to their computer multiple times a day will only have one report created every day. By using the /SILENT command-line option, the system tray icon of AIDA64 will be hidden.

The only potential issue I can see about your command-line is the space characters in the shared folder name. Try to rename the folder called AIDA64 Business Edition to something simpler, e.g. aida64business. The rest of the command-line seems just fine. If it still doesn't work, then check if you provided the necessary write permissions to the \\server\report folder for your network users.

I'm afraid that's currently not possible with AIDA64.

That's the usual behavior of modal windows. When you minimize the modal window, the whole application gets minimized, and when you restore the application, the modal window is still minimized, so only the main application window is restored.

You need to purchase as many licenses as many computers you want to audit. If you have a network with 100 computers, you need to have 100 licenses of AIDA64 Business Edition.

Please try to disable automatic launching from Logitech drivers (using Logitech LCD Manager), and instead rely on the built-in auto-startup feature of AIDA64 that you can activate in AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup. Regards, Fiery

Thank you for the feedback

You can further improve the panel by using transparent PNG images for logos, e.g. try to replace your Core 2 Extreme badge with the following image: http://www.aida64.com/files/image_intlogo_core2_extreme.png

The easiest way to catalog AIDA64 reports for such a use is to create CSV reports in folders named by the creation date. Example command-line: \\server\share\aida64folder\aida64.exe /R \\server\share\aida64reports\$DATE\$HOSTNAME /CSV /AUDIT /SILENT /SAFE Then you can simply point the Audit Manager (of AIDA64 Business Edition) input folder into the \\server\share\aida64reports folder, and it will load the last reports (the current audit). To list the changes between audit snapshots -- ordered either by username, hostname or date -- you can use the Change Manager feature (of AIDA64 Business Edition). You should use the input folder again as \\server\share\aida64reports, and it will list and indicate any hardware or software changes across all your networked computers. You can limit the Change Manager to list only the changes occured in the past 7 or so days if you want. As for real-time alerting, AIDA64 Business Edition has such a feature, but you need to have AIDA64 running in the background all the time to use that feature (AIDA64 / main menu / File / Preferences / Alerting). Regards, Fiery

When pressing the New or Modify button in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD, the window has 4 layouts, selectable with the "Item Type" dropdown list near the top-left corner. First layout is for the Sensor Item, which is the more complex, less-intuitive way to configure your LCD items. Second layout is the new Simple Sensor Item that offers the same level of customizations as the old LCD module. Third and fourth are the Static Label and Image that lets you add labels and pictures to your LCD. If you want to configure your LCD without hassling with the complexity of the Sensor Item layout, just select the Simple Sensor Item from the dropdown list. Later on, if you decide you want to give the more complex method a try, e.g. to add bars to your LCD, then you can reconfigure any of the LCD items from Simple Sensor Item into Sensor Item.