Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Frequently Asked Questions about the RemoteSensor LCD feature: Q: Does it work on Amazon, Android, BlackBerry OS, Chrome OS, Firefox OS, iOS, MeeGo, Windows Phone, or Windows RT mobile devices? A: Yes, on all of them. Basically any device would work that has got a modern web browser. In case your web browser doesn't display the LCD layout properly, then try to find another, preferably more modern web browser. E.g. on Android v2.3 devices the built-in Android Browser fails to work, but Firefox will work fine. Q: Does it work with Internet Explorer? A: Yes, but only with IE 9.0 and later versions. Q: Is it possible to use it over the internet? A: It is designed to be used in a WiFi network, but it is also possible to use it over the internet. You have to take care of opening the relevant TCP/IP port on your router or firewall though, and if necessary, configure port forwarding too. It is not recommended to use it via a cellular data network (e.g. GPRS, EDGE, 3G, or LTE) connection though, due to the frequent network traffic. Q: Does RemoteSensor support multiple pages? A: RemoteSensor supports only one physical page, but you can use a larger page size than your actual mobile device display resolution, and use swipe scrolling to change between virtual pages. The way it works: let's say you've got a 980x1440 pixel resolution, as reported by the web browser of your mobile device. You configure 980x2880 as Preview Resolution in AIDA64, and you will basically have two pages on top of each other. You can use 980x5760 resolution to have 4 pages, etc.
  2. Fiery
    The collision may or may not happen, since AI Suite background service does have a poll rate. If it is polling the sensors when AIDA64 launches, a collision would occur. If it is between two polls, AIDA64 will launch fine. And since AIDA64 is a process (application), but AI Suite background service is a NT service, there's no way to set their start order. Unless of course you delay AIDA64 launch by 30 or 60 seconds after the user logon.
  3. Fiery
    Thank you for the feedback. As for SPD, both your memory modules have a working SPD chip. Otherwise, the module would not appear on the Motherboard / SPD page in AIDA64 Your TwinMOS module however has the SPD manufacturer ID field and part number fields both set to zero, so it's basically not filled. It doesn't cause an actual issue, it prevents the proper identification of memory module model name.
  4. Fiery
    Please note that AI Suite II, even when you don't use it (when you don't have any of its windows open), it is still using its background service to monitor and poll the motherboard sensors. Even after uninstalling AI Suite, it tends to leave its background service behind and active. Most likely the background service collides with AIDA64 low-level detection module. Note that AIDA64 detects and then caches a lot of hardware information at its startup, and it's crucial that no other software would collide with it when it starts up. Most other diagnostics, monitoring, overclocking and tweaking software (like AMD OverDrive, CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan) are synchronized with AIDA64 and each other, but Asus refuses to implement the necessary and standardized synchronization technique. If they would, such collisions would never occur with other software...
  5. Fiery
    Strike7 API has quite a few weird issues. Sometimes implementing a workaround fixes it, but the major problem lies in the SDK that Mad Catz designed. Please report the issue to them, and we'll also ping them to find out how can we work together to fix this issue, and also the touch-related other problems. Thanks, Fiery
  6. Fiery
    Hard to diagnose such issues remotely My best guess would be that the low-level hardware detection module of AIDA64 collides with another diagnostics, overclocking, tweaking, or monitoring software. Or, a wild guess: maybe your security software kills the AIDA64 process due to it making some "funny" things like talking directly to the hardware.
  7. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3242kwn2zf6gyqzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. That should fix the fan RPM calculation issues. Note that the sensor chip of your motherboard is only capable of measuring no more than 3 fans. Hence, the 4th fan (NB fan) is not measured, but only powered.
  8. Fiery
    We've added graphs and gauges to both the Logitech Arx and RemoteSensor LCD module in the latest beta release of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta Note that the new gauges featured in these modules are called arc gauges. They do not have the same look & feel as the classic AIDA64 gauges (featured in the SensorPanel), but they offer much more flexibility.
  9. Fiery
    It looks great We've added graphs and gauges to both the Logitech Arx and Web Server LCD module in the latest beta release of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta Note that the new gauges featured in these modules are called arc gauges. They do not have the same look & feel as the classic AIDA64 gauges (featured in the SensorPanel), but they offer much more flexibility.
  10. Fiery
    I've just sent you a private message about this Regards, Fiery
  11. Fiery
    Our contact at Logitech says that they will look into it.
  12. Fiery
    Most notebooks can only control fan speeds, based on temperature readouts, but monitoring the current fan speed RPM is not supported. Are you sure your notebook is capable of measuring its fan speed(s)?
  13. Fiery
    Thank you. I've sent you a private message about this.
  14. Fiery
    Thank you. That indeed looks quite odd. What update frequency did you select for the OSD Panel? When the OSD Panel gets "confused", do the date and time items (at the bottom) drop out?
  15. Fiery
    We've recently revamped the OSD Panel and SensorPanel window positioning scheme, so make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3237vy9hqdrx7czip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. BTW, in the Registry you can set SensorPanelPosX and SensorPanelPosY to change the position of the SensorPanel.
  16. Fiery
    We haven't got any programming information on those devices. We've sent a request to Aquacomputer, hopefully they would help us out. I'll post updates on this issue into this topic.
  17. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic. Thanks, Fiery
  18. Fiery
    Thank you for the test runs. It means one of the MSR register readouts cause the DPC latency spikes on your system. On your processor AIDA64 requires a lot of MSR readouts to detect/measure various values, like CPU multiplier, CPU BCLK (FSB), NB (uncore) clock, memory clock, CPU power measurement, etc. Not easy to get rid of the MSR readouts, you would lose too many vital information then
  19. Fiery
    Thank you. Since the Memory Timings and Memory Speed drop out, the issue may be related to your Haswell-E CPU. Is your CPU overclocked or otherwise specially tweaked? Can you see the drop outs only when the CPU is idle, or only when it is under heavy load? Can you see the drop out of the Memory Clock or DRAM:FSB Ratio items as well? BTW, we've tried to reproduce the issue on our own Core i7-5820K based test system, but without a luck. Maybe it's because our test system is not overclocked or tweaked from default settings...
  20. Fiery
    I've forwarded your request to them. However, please note that providing backwards compatibility in Android could be quite complicated and burn a lot of resources. Most Android developers focus on the latest & greatest few iterations of Android, and only provide backwards compatibility if it can be accomplished without too much overhead.
  21. Fiery
    Are you running the latest version of Logitech Gaming Software? (v8.57.145) If yes, then please report the issue to Logitech. As for graphs and gauges, as I wrote in my previous post, they are under development. We're planning to roll out gauges next week, and graphs a bit later on.
  22. Fiery
    Arx only supports a single set of applets, but it supports showing the same applets on multiple devices. So the layout you make with AIDA64 can be viewed on a phone and a tablet at the same time, but it has to be a single layout. You can however use e.g. Arx for your phone and the AIDA64 RemoteSensor for your tablet, or vice versa
  23. Fiery
    Thank you for the feedback. It's a bit odd that something was using port 8080, but then again, so many background processes and services are running under Windows these days...
  24. Fiery
    1) What kind of items keep dropping out and then appear again? CPU Clock, CPU Multiplier? Or one of the temperatures? 2) Do you have any other hardware monitoring modules enabled, besides the OSD Panel? 3) Do you use Correction? (main menu / File / Preferences / Hardware Monitoring / Correction) Thanks, Fiery
  25. Fiery
    Sounds like it may be an issue related to your local (software) firewall, like Windows Firewall. In case your firewall software fails to pop up a warning message about AIDA64 trying to use the configured TCP/IP port for network traffic, you will need to add it manually to your firewall settings.
×
×
  • Create New...