Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11200

  • Joined

  • Last visited

  • Days Won

    475

 Content Type 

Posts posted by Fiery

    block size is inconsistent

    in Benchmarking, system performance

    Posted

    In auto mode AIDA64 tests all block sizes, and selects the one block size that provides the best scores. In many cases the results for various block sizes will be very close to each other, resulting in selecting a different block size. If you're certain about which one is the best block size to use, then simply avoid using the auto setting B)

    Regards,

    Fiery

    "New" LCD features break old configured pages

    in General Discussion

    Posted

    Thanks for the Info Fiery. But yeah I am going to agree with Xyrax. Its current state makes it WAY more complex than it has to be.

    So far a handful of customers reported similar findings. It's a relatively low number, but we're committed to provide a software to suit everyone's needs, so we'll implement the "Simple Sensor Item" in the next AIDA64 beta release due in a few days.

    I would certainly prefer the old method or at least be able to use the new Import feature that would perhaps adjust old configs to the new method?

    That import feature is already there, and automatically imports the old settings into the new LCD module. Problem is: due to the fundamental difference between items placement and label-value-unit relations, there's no way to attain the same looks with the new LCD module. However, by implementing the "Simple Sensor Item", accurate items importing will also be possible.

    Please keep your old AIDA64.INI file (it includes your old LCD settings) if possible, so when you upgrade to the next AIDA64 beta, your old settings will be automatically imported and the old LCD looks will be retained.

    Your changes put some limitations on things that result in it being impossible for me to get my display back to the way it looked without using some workarounds that shouldn't be neccasary. For example, my up time used to be displayed with the label to the left of the value (e.g. 'Up Time 8:01:23'), now I am forced to have the label to the right of the value unless I want to use a seperate static label meaning one more element to tweak whenever I make changes to the layout.

    It is still possible to display it the way you want. You just need to adjust the "Total width" parameter to move the label and value closer to each other.

    Shared Memory C# StructLayout

    in Hardware monitoring

    Posted

    There's no struct involved at all, since AIDA64 publishes sensor readings in shared memory as a single long string (set of characters), using XML format. You can simply read the full shared memory into a character variable, and display it or post-process it.

    Regards,

    Fiery

    AIDA64 v1.85 crash (ULPS)

    in Bug reports

    Posted

    Then it is related to the infamous ULPS feature of Catalyst drivers. It shuts down the secondary GPU (or GPUs) when you're not in a 3D game or application. However, that feature may cause a system lockup sometimes. You can try disabling Multi-GPU support (in AIDA64 / main menu / File / Preferences / Stability), but in most cases that doesn't help. It's best to completely disable the ULPS feature by setting all occurences of EnableUlps to 0 (zero) in the Registry, using the Registry Editor application (REGEDIT.EXE). You need to restart your computer after altering the EnableUlps values in the Registry.

    Regards,

    Fiery

    AIDA64 v1.85 crash (ULPS)

    in Bug reports

    Posted

    1) Does it also crash when you go to the Computer / Sensor page?

    2) Does it also crash when you go to the Display / GPU page?

    3) Did everything work well with the previous AIDA64 release? (Version 1.80)

    4) Please let us know more about your system configuration: motherboard model, CPU type, video card(s) model, Windows version?

    Thanks,

    Fiery

    Upgrade from new 1.80 to 1.85

    in General Discussion

    Posted

    AIDA64 licenses are time-limited and not version limited. Hence your AIDA64 license entitles you to upgrade to any new AIDA64 releases until June 18, 2012, including the today release of AIDA64 v1.85 of course. Once that date (June 18, 2012) comes, you will still be able to use the last version you are entitled to upgrade to, for an unlimited time. By extending your maintenance period (in June 2012 or later) you can continue upgrading to new AIDA64 releases for 1 or 2 or 3 more years.

    Regards,

    Fiery

    "New" LCD features break old configured pages

    in General Discussion

    Posted

    In AIDA64 v1.85 we've applied the advanced configuration options of the previously announced SensorPanel feature, and its new approach of "per-pixel" level adjustments to the LCD feature as well. We've implemented an automatic migration to move the old LCD settings into the new LCD module, but since the new LCD solution is a completely different approach in many ways, the automatic migration is not 100% bullet-proof. So after upgrading to AIDA64 v1.85, you'll need to re-adjust your LCD items in order to attain the previous looks of your LCD display with AIDA64.

    I'm sorry for the inconvenience the revamped LCD module caused for you, but we had to do that revamp to provide such features that we introduced with the SensorPanel, e.g. configurable colour bars. Once you learn how you can precisely adjust each LCD item with the new AIDA64, you'll see that you can do a lot more with the new LCD than with the old one.

    In case you still want to stick to the old LCD module, please let us know, since we're currently gathering users feedbacks about this migration. If we get a number of statements about prefering the old LCD configuration over the new one, we may tweak the new LCD module to provide the old "simple LCD item" configuration as well. And so you could have a sort of "best of both worlds": a simple item that you can configure at ease, and an advanced LCD item configuration if you want to step further.

    Regards,

    Fiery

    AIDA64 v1.85 is out!

    in General Discussion

    Posted

    The new AIDA64 release revamps the Logitech LCD module to support multiple LCD devices with enhanced configuration options, and adds preliminary AMD “Trinity” CPU optimizations as well as OpenGL 4.2 graphics device support.

    sensorpanel.jpg

    New features & improvements

    - Advanced multi-device Logitech LCD support

    - Preliminary support for AMD Trinity processors

    - Improved support for Socket FM1 motherboards

    - Temperature, fan speed, voltage correction

    - GPU details for nVIDIA GeForce 510, GeForce GTX 580M

    - OpenGL 4.2 support

    [ Press Release ]

    [ What's new in AIDA64 v1.85 ]

    [ Download ]

    LCD and Program Temperature Readings are frozen (and impossible) after sleep.

    in Bug reports

    Posted

    FYI, in the latest AIDA64 beta releases we've completely revamped the Logitech LCD support, so you have to recalibrate all items, especially their placement. We've basically applied the same improvements that we introduced as the SensorPanel feature on the Logitech LCD feature. It enables you to display bars and to use a more precise items placement -- but on the other hand it requires a bit more efforts to recalibrate your old settings.

    Stress test help

    in Benchmarking, system performance

    Posted

    1) If you would like to stress your system to reveal a potential hardware flaw or instability, then enable all tests in the System Stability Test window, and press Start. Let it run for a few hours. If it doesn't display any error messages, Windows also runs fine, and your computer doesn't reboot, doesn't lockup and doesn't shut down, then your computer is considered very stable.

    2) If you rather want to stress your system from a thermal point of view, to reveal potential cooling issues, then only enable the FPU test in the System Stability Test window, and press Start. Let it run for a few hours. Watch the temperature graphs, where the motherboard temperature should stay below 55-60 Celsius, and your CPU temperature should stay below 80 Celsius. In case you have an Intel processor, then should also watch the bottom graph where the Throttling activity should stay at 0% all the time. If the Throttling graph shows any non-zero activity, it means your processor is overheating. In case your computer restarts, shuts down, locks up or throws a BSoD while running the thermal stress test, then your computer is overheating.

    Regards,

    Fiery

×
×
  • Create New...