Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11190

  • Joined

  • Last visited

  • Days Won

    475

 Content Type 

Posts posted by Fiery

    Scheduled tab not working

    in Bug reports

    Posted

    Scheduled tab now is displayed correctly, but I can't use the double click feature to modify task properties.

    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.

    However, not all scheduled tasks are shown (for example all complete Windows tasks are missing).

    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.

    Adding more supported products and codecs

    in Brainstorming

    Posted

    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

    Computer shuts down when under heavy load (Acer Aspire 8930)

    in Hardware monitoring

    Posted

    I find odd is this bit of text here from the AIDA64 report "100 MHz (original: 800 MHz)" I'm seeing this all over the report... is this normal?

    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.

    Shared Memory C# StructLayout

    in Hardware monitoring

    Posted

    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.

    AIDA64 v1.85 crash (ULPS)

    in Bug reports

    Posted

    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.

    AIDA64 v1.85 crash (ULPS)

    in Bug reports

    Posted

    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.

    ... without a windows server domain

    in Network audit, change tracking, SQL databases

    Posted

    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.

×
×
  • Create New...