Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you for the feedback. I'm afraid we cannot make it move any faster than the current rate. But you can double-click on an item and change the X,Y coordinates manually to a different value to move them faster to a different location on your LCD. Yes, we've had to change the way AIDA64 handles hot-plug devices, because the old solution wasn't suitable for fans that are frequently stopped and started spinning again, especially in water-cooled systems. Also, it could have been a bit unexpected to see an old item to appear again, for example if you connected an external drive that was not connected for a while.
  2. Fiery
    Here's the download link for the mentioned AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta
  3. Fiery
    We've fixed the issue in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  4. Fiery
    AFAIK OCZ Vertex SSD drives -- just like many other SSDs -- do not feature a tempeature diode. Regards, Fiery
  5. Fiery
    If you open the SensorPanel Manager (from the right-click context menu on the SensorPanel), in it you can select multiple items and move them together in any direction. You can also modify, hide, restore, and delete the selected items easily using the SensorPanel Manager. Regards, Fiery
  6. Fiery
    Thank you for the feedback
  7. Fiery
    I'm glad it worked out. May I ask what motherboard do you have, and what SATA controller do you have the Pioneer drive connected to?
  8. Fiery
    I've sent you a private message and an email about this
  9. Fiery

    Force close

    Fiery replied to delevic's topic in Bug reports

    Thank you. I suppose one of the software on your system added an improper (or odd) entry to the list of Windows Scheduled Tasks, and that causes the issues. Do you have an idea about what software would it be? If not, can you please start Task Scheduler and check the list of scheduled tasks? Maybe you can find the one that is only present on the first computer, but not on the second computer?
  10. Fiery
    It's quite puzzling, since as I've checked it now, we haven't done any major revamping about strorage device support recently, ie. between v4.70 and v5.00. One thing you can try is disable RAID member enumeration in AIDA64 / main menu / File / Preferences / Stability, in case you have no RAID arrays in your system. Maybe by having that option disabled, AIDA64 v5.00 will work properly on your computer.
  11. Fiery
    So you mean AIDA64 v5.00.3300 Stable works fine but v5.00.3303 Beta fails to work? It would be quite odd, since we haven't changed anything about storage devices between those builds. Are you sure the issue is related to AIDA64?
  12. Fiery
    You need to use Fraps to measure frame rates for DirectX games. When you have Fraps running, you can use the Fraps item among the hardware monitor items in AIDA64. AFAIK currently there's no software that could measure frame rates for Mantle games.
  13. Fiery
    It looks great, thank you for the feedback I love your creative solution about the concentric arc gauges
  14. Fiery
    Quite frankly, I think the way it works now is the logical way. Since when it shows zero as volume on the bar graph, that's the truth: muting effectively means 0% volume The negative value is shown just to indicate that the volume is not rolled down to zero percent, but muted with a non-zero volume in use before the muting. But when it comes to the resulting volume, the bar graph is right
  15. Fiery
    When you enable Logitech Arx LCD support, do you get any error messages in red colour? Or you get the "Arx Init OK" green message?
  16. Fiery
    I think you misunderstood my post. We are working on direct handling of Aquastream and MPS devices actually. We prefer talking directly to the hardware, instead of relying on other software to collect the same data.
  17. Fiery
    Thank you for the feedback
  18. Fiery

    Force close

    Fiery replied to delevic's topic in Bug reports

    What kind of Windows do you have installed on the problemous computer? Thanks, Fiery
  19. Fiery
    I'm glad it works fine, thank you for the feedback
  20. Fiery
    We'll soon implement a control string feature for Static Labels, as explained in the second half of the following forum topic: http://forums.aida64.com/topic/2610-logitech-arx-control-lcd-for-smartphones-and-tablets/ And as I've requested in my last post there, please post your ideas on other control strings. Please avoid posting *.* there Just focus on the values that you really and definitely want to see on your LCD. We cannot add hundreds of values just because they might come useful one day, but we definitely can add a lot more than the initial set of 7 options.
  21. Fiery
    We'll add the following 7 control strings for Static Labels in the next AIDA64 beta update due next week: $CPUMODEL $DXVER (DirectX version) $HOSTNAME $LOCALIP $MOBOMODEL $OSPRODUCT (Windows product name) $USERNAME Please let me know if you have more ideas on such control strings. They will be detected once per session, so they must be fairly static (constant) values.
  22. Fiery
    Thank you for the feedback. As for the master volume issue, I'm not sure if I understand the actual problem. I've just tried it with a master volume bar graph (the way I see it on your screen shot), and it reflected -36% as a value after muting the volume, and the bar graph itself showed no value, so it basically showed no volume (0%). I would think that's the proper way to show the volume. I used 0-100% range for the bar graph. Or maybe you mean the graph, and not the bar graph? As for the uptime under Win8, yes, it is the way it works with Win8.x, and AFAIK it's not possible to fix it from a software. If you're too bothered by that, then you may have to disable the fast shutdown feature of Win8.x.
  23. Fiery
    The macros would be a fixed, pre-defined set, so you would have to choose from them, by clicking on the "V" button next to the dropdown list. You wouldn't have to create, open or maintain any text files or any other files. As an example, if you would want to put a label on your LCD with a caption of your local IP address, in the Label field on the Static Label configuration panel you would write: $LOCALIP And then, when the LCD is rendered, AIDA64 will not display "$LOCALIP" on the label caption, but instead it would replace the $LOCALIP text with the actual local IP address of e.g. 192.168.0.123. Other such macros could be: $CPUMODEL $MOBOMODEL $HOSTNAME $USERNAME $OSPRODUCT (Windows product name) $DXVER (DirectX Version) etc. You could also combine those macros in a single label, so you can specify the caption as e.g. "$MOBOMODEL / $CPUMODEL"
  24. Fiery
    1) We've implemented two new hardware monitor items, Time (HH:MM) (means Time without seconds) and UpTime (HH:MM) (means UpTime without seconds). 2) We've implemented a new bar option called "Right To Left" to let you change the direction of bar graphs. It's right below the "3D effect" checkbox, and will change its label automatically to "Top To Bottom" in case you configure a vertical bar Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works ----- As for your idea about macros, well, that sounds like a very flexible but also very complicated method. We will have to find something in between. Maybe something like a dropdown list of macros for the Static Label's label field. The list of macros would be like "$LOCALIP", "$CPUTYPE", etc. That way it wouldn't require us to add more dynamic hardware monitor items, and the labels wouldn't have to be updated more than once per session, so it wouldn't put any additional overhead on either the main computer or the mobile device. What do you think?
  25. Fiery
    We've implemented increased accuracy for temperature measurement and temperature display in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta You can change the default zero decimal digits for temperature readouts (which is the legacy method) in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Note that the increased display accuracy will be reflected in all AIDA64 modules, including the Computer / Sensor page, RemoteSensor, Logitech Arx, LCD, SensorPanel, OSD Panel, Sidebar Gadget, Logging, etc. Except for the Sensor Icons where there's no room to display the decimal digits. As for the actual measurement accuracy, it is not available for most sensor devices, so don't be surprised to see a lot of "37.00 Celsius" or "32.00 Celsius" temperature readings. It is of course available for the Aquaero and Aquaduct Let me know how it works
×
×
  • Create New...