Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    524

 Content Type 

Everything posted by Fiery

  1. Fiery
    I'm afraid for that you need to draw your own gauges at this time. I'm not sure what to do about the gauges, since there are quite a few high-res monitors out there and so we would have to come up with at least 3 new (and bigger) stages for each gauge which would inflate the number of gauges considerably -- as well as inflate the size of the AIDA64 distribution package...
  2. Fiery
    Locking only works by pixel position. So if you regularly change your monitors, it may be annoying having to readjust the SensorPanel position. Unless you make your SensorPanel monitor in a negative position (e.g. left to your main display as seen in the monitors layout in Windows Settings) in which case if you change your other monitors, the SensorPanel monitor should have the same negative pixel positions.
  3. Fiery
    Yes, it's possible. Safari can connect to the RemoteSensor module of AIDA64.
  4. Fiery
    If you run AIDA64 using the SYSTEM user, you may indeed run into such issues. I'm not sure however how to get around it. You may need to use an additional solution to enumerate those software.
  5. Fiery
    I cannot tell you that unless I know a bit more about the actual hardware interface and implementation. First of all, since you're planning to use a 800x480 colour display, the minimum amount of data to be transferred in each cycle would be 800x480x2 (16-bit colour depth) bytes, which is 750 KiloBytes. It means the protocol cannot be classic serial, since it would be too slow to update a frame. You would have to come up with a high-speed USB solution either via USB bulk transfer or HID. I'm not sure if connecting the Arduino is possible using such a high bandwidth USB connection. BTW, rather than reinventing the wheel, why don't you simply pick up a BeadaPanel? Same resolution colour screen than WF70A2SIAGDNN0:
  6. Fiery
    I'm afraid we have no skills in Arduino development, so I cannot help you about that
  7. Fiery
    I can there are 2 possible solutions to your issue/idea: 1) You can either implement an existing protocol on your side, which would mean emulating a protocol that already exists as an external LCD module in AIDA64. This would be the fastest way to get there, considering that it wouldn't require adjusting AIDA64 to make it happen. 2) Or, you can desing your own protocol, write a proper SDK or protocol spec, and we can add your protocol to the external LCD module of AIDA64 as a new protocol. Designing your protocol however would need to take into account what's possible to accomplish at the AIDA64 side, performance considerations, etc. If you can tell me more about your capabilities, the actual display type (pixel resolution? color depth?) and connection interface (USB? HID? connection performance? Serial-to-USB bridge? SPI-to-USB bridge?) you'd like to use, I will be able to provide you with more meaningful feedback.
  8. Fiery
    If anyone knows about the necessary API calls to dock a window onto to Windows Taskbar, please send me a private message
  9. Fiery
    Thank you! I've sent you a private message about this issue.
  10. Fiery
    I'm afraid we've never dealt with either the 64-bit aspects of the SDK or the .NET or C++ development side of it.
  11. Fiery
    BeadaPanel perhaps: https://forums.aida64.com/topic/5149-beadapanel-lcd-device-support/ Also, when it comes to external LCD displays, we keep recommending just picking up a nice 2nd-hand LCD monitor, connect it to your PC via DSub, DVI or HDMI, extend your Windows Desktop onto it, and then you can use the SensorPanel on a large colour display and enjoy the heck out of it
  12. Fiery
    Try to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Then go to the Computer / Sensor page to verify if the case fans appear there properly.
  13. Fiery
    Check this package: http://users.aida64.com/strike7_api_1_1.zip
  14. Fiery
    With laptops it's usually difficult to measure such values. But, we can try to figure out how it works if you could help us a little bit. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  15. Fiery
    Thank you for your feedback!
  16. Fiery
    CPU utilization is measured by the operating system. The CPU itself cannot measure that.
  17. Fiery
    The 2 fan speed settings are used by the older Asetek VI protocol only. They refer to the fan speed (fan duty cycle) setting of up to two Asetek VI based devices. As long as you don't experience any issues with the default settings, you don't need to alter those options in the AIDA64 Preferences.
  18. Fiery
    When they can be detected, the PCI and AGP clocks are shown on the Motherboard / Motherboard page. As for how the PCI and AGP clocks are driven, it depends on the FSB logic (FSB strap) the motherboard uses. If it has a different strap for 266 MHz FSB than for 200 MHz FSB, then no overclocking of the PCI and AGP clocks should be used when you switch from 200 MHz FSB to 266 MHz FSB. In other words, at 200 MHz FSB the PCI clock should FSB/6 (FSB clock divided by 6), and the AGP clock should be double the PCI clock. If the right FSB strap is used by the motherboard, at 266 MHz FSB the PCI clock should be FSB/8, and the AGP clock should still be double the PCI clock. To rule out the possibility of AIDA64 detecting the wrong clock frequencies, try to check the same information using other software like CPU-Z, HWiNFO and SIV as well.
  19. Fiery
    They should be there, on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD / OSD Items page. Try to scroll down a bit to find them
  20. Fiery
    AMD processors have only a single thermal diode, so per-core thermal measurement is not possible. When a software shows per-core thermal readings for AMD CPUs, the temperature values will be identical across all cores. As for the DIMM voltage and perhaps other measurements missing, try to switch the option Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes.
  21. Fiery
    I'm afraid we're not skilled in overclocking and fine-tuning, but hopefully someone else can chime in and help you out.
  22. Fiery
    Thank you. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  23. Fiery
    The above mentioned new AIDA64 beta build is now available for download: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  24. Fiery
    Thank you!
  25. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
×
×
  • Create New...