Fiery
-
Posts
11199 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Fair enough. But how about doing a check and warning AMD crossfire folks that going any further may lock your system up?
I have to agree to disagree with your answer.
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.
-
This bug is BS because you have to disable a power saving feature to get the software to work or disable crossfire. I am using version 1.60 and would upgrade if I was assured this issue has been fixed..
Thank you.
Please stop blaming us. I've further explained in the other thread where you posted similar comment.
This thread is closed.
-
I got another suggestion. You could pull out the second gpu just to use their software! Its unacceptable to disable a key system power saving feature just to use this software. I can't believe they haven't fixed this issue at version 1.85 already!
I say AMD/ATI users ban AIDA64 until they fix this issue!
BS.
Edit: Why I'm pissed: Risking data loss due to an unexpected reboot is not pleasant...
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.
-
new question: what encoding does the xml use? ASCI UTF8? etc?
Plain old ASCII
-
we are buying the 10 licenses can also be used in preference / scheduled time (once a day).
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.
Its hiding the systray icon?By using the /SILENT command-line option, the system tray icon of AIDA64 will be hidden.
-
Hello, I am not able to collect the audit information from the network, you can help me please. I am using this command line:
\\server\AIDA64 Business Edition\aida64.exe /r \\server\report\$HOSTNAME /CSV /AUDIT /SAFE /SILENT
shared folder on the server xp, and AIDA64 and report folder
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.
-
One more thing, is there any way to schedule automatic comparing of report files and notify by mail or other means about detected hardware changes?
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.
-
Please confirm that for this to work AIDA64 Business Edition for 5 nodes is sufficient?
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:
-
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
-
Well I guess I have to ask how to get it to use the old style with the new Beta?
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.
-
Thank you for the feedback
-
Thank you for the feedback. It should be okay with Catalyst 11.9 as well
We've switched from dynamic DLL linking (of OPENGL32.DLL) to static linking. Most software utilizing OpenGL use static linking, but so far AIDA64 had no problem with dynamic linking. Apparently Catalyst 11.8 has a bug that only comes up when OPENGL32.DLL is dynamically loaded. -
We've implemented the Simple Sensor Item in both the SensorPanel and the Logitech LCD module. The old LCD settings are imported into Simple Sensor Items, retaining the old layout 100%.
Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild1604bxs0dft5lnzip
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 done quite a bit of testing today, and we've been able to fix the OpenGL issue with a workaround:
http://www.aida64.com/downloads/aida64extremebuild1604bxs0dft5lnzip
Let me know how it works.
Thanks,
Fiery
-
We've done quite a bit of testing today, and we've been able to fix the OpenGL issue with a workaround:
http://www.aida64.com/downloads/aida64extremebuild1604bxs0dft5lnzip
Let me know how it works.
Thanks,
Fiery
-
We've already done some test runs about this issue, and it seems it's due to a bug in Catalyst 11.8. No other drivers seem to be affected. In the OpenGL detection part of AIDA64, the OpenGL32.dll module throws an exception when wglCreateContext is called. Quite a weird issue...
-
Thank you for the bug report. We've already done some test runs about this issue, and it seems it's due to a bug in Catalyst 11.8. No other drivers seem to be affected. In the OpenGL detection part of AIDA64, the OpenGL32.dll module throws an exception when wglCreateContext is called. Quite a weird issue...
-
Thank you for the feedback
-
Either you implement a XML parser, or simply process the long string, to convert it to a format that you need. It's not a real, complex XML string, just a dumb XML-like format
-
AIDA64 Extreme Edition doesn't support command-line parameters. Would you need to disable collecting product keys with AIDA64 Extreme Edition?
Shared Memory C# StructLayout
in Hardware monitoring
Posted
NUL character is used to indicate the end of the string.