Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    The requested feature will be implemented in the next AIDA64 beta update due in a few days from now
  2. Fiery
    Thank you, the issue will be fixed in the next AIDA64 beta update due in a few days from now.
  3. Fiery
    Merci
  4. Fiery
    Yes, of course I'll send you a download link soon. Thank you. Can you please provide direct fix for the following 4 lines, for the whole expressions? It would help us to fix the issues in the French language module. NIC1 Download Rate=NIC1 Télécharger taux NIC1 Upload Rate=NIC1 Téléchargement taux NIC1 Total Download=NIC1 Télécharger Total NIC1 Total Upload=NIC1 Téléchargement Total I think I'm right about feeling that the last line is not accurate either
  5. Fiery
    Thank you. The CPU fan RPM is read incorrectly because of a BIOS bug. We've checked, but there's no different method in the ACPI BIOS to read fan RPM on your system, so we cannot do anything at this time. Unless of course Asus manages to fix the BIOS of your notebook. But I don't think such a minor issue is something they would deal with As for the GPU, its fan is not controller by the GPU itself, that's why the GPU fan duty cycle is fixed at 100% in AIDA64. We will remove that unnecessary reading in the next AIDA64 beta update.
  6. Fiery
    Yes, you can. AIDA64 doesn't require internet for anything but its automatic internet update feature. It certainly doesn't require internet to push the measured system or sensor values to your mobile device via RemoteSensor or Logitech Arx
  7. Fiery
    I think it's more about Win10 and the way it handles USB devices. We've also seen that issue coming up sometimes after restarting Win10. You can try connecting the SPF to a port that belongs to another USB controller, or try to use a USB hub. But I'm not sure if any of those would help I'm starting to feel like we would be better off by purchasing a dozen of very affordable 8 or 10-inch Android based tablets, connect it to the USB port, and develop a special firmware that would kick the Android out and replace it with our own solution for SPF-like usage Too bad there's no considerable market (ie. thousands of guys interested) for such a special "AIDA64 Hardware".
  8. Fiery
    I hope it will work out. In your case I'm not at all sure about the 500KB limit. It may be lower, like 448KB, but it's not easy to calculate those limits without actually counting the displayed pixel lines on the LCD in the SPF random mode And we don't want to specify a too low JPEG size limit, since then AIDA64 may force you into a position of using too low JPEG quality resulting in low quality displayed images Of course it's still possible to define a JPEG quality manually, but even if you define 99%, the limiter will cut it back to fit the JPEG in the file size limit.
  9. Fiery
    Let me know about your long-term experiences about the current solution. We may have to lower the 256KB limit by a few KB's to make it more stable. But it's a good sign if the glitches become rare.
  10. Fiery
    No, for a WiFi network to work you only need a WiFi router or AP. If you have a WiFi router, and you don't connect it to the internet, your local network will still work fine, and you can establish a connection between your PC and mobile phone/tablet via WiFi. Please don't mix local network (LAN) and internet. They're very different things.
  11. Fiery
    No. WiFi can work without internet. When you use AIDA64 RemoteSensor in your WiFi local network, the data doesn't go on or through the internet at all, but stays inside your local network (ie. your house or office).
  12. Fiery
    No internet is required for RemoteSensor, but only WiFi LAN access The Bluetooth solution would require a native app on each supported platforms though. While RemoteSensor only requires a web browser which all platforms have built-in.
  13. Fiery
    As I've said above: your motherboard doesn't seem to be able to measure motherboard temperature. It's a hardware limitation, and has nothing to do with any software.
  14. Fiery
    Do you mean using the Bluetooth connection between your PC and your mobile phone or tablet? It sounds only a bit more convenient than the existing RemoteSensor feature: http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/ Regards, Fiery
  15. Fiery
    Thank you for the feedback BTW, next time you perform an upgrade, you don't have to clean anything or remove any old files. Just download the new ZIP package, and extract it to the existing installation folder of AIDA64. Let it overwrite any existing files. That method will retain your existing settings and your license as well.
  16. Fiery
    Using the new beta, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the results into this topic. Before you do that, make sure to enable the status bar in AIDA64 / main menu / View Thanks, Fiery
  17. Fiery
    Yes, we've removed the temperature reading, since your motherboard doesn't seem to be able to measure motherboard temperature. That 110 Celsius was just a bogus reading, due to an unconnected temperature input on the sensor chip.
  18. Fiery
    We've implemented automatic JPEG image size limiter for SPF-83H and SPF-105P devices in the following new beta update to AIDA64 Extreme: http://www.aida64.com/downloads/latesta64xebeta We've set the following limits so far: - 800P/800PE [04E8-2038] (our own device): < no need to limit JPEG size > - SPF-75H [04E8-200F] (our own device): 400 KB - SPF-83H [04E8-200D] (Xixou): 256 KB - SPF-105P [04E8-201B] (Spaljeni): 500 KB - SPF-107H [04E8-2036] (Mrshilov): 604 KB There's a slim chance those limits are still a bit higher than the actual limit used by the SPF firmware, so please let us know if you still experience image corruption or device disconnection issues while using the latest AIDA64 beta.
  19. Fiery
    Thank you for the data. We've implemented sensor adjustments for your motherboard 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. Let me know how it works
  20. Fiery
    We've fixed it up 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. Let me know how it works
  21. Fiery
    Do you have Gigabyte GA-Z97X-UD5H or GA-Z97X-UD5H-BK motherboard? You can check your motherboard model on the Motherboard / Motherboard page in AIDA64.
  22. Fiery
    I know You can still enable it from main menu / View Or, you can press Ctrl+D on the main window to get to the debug menu. Edit: Thank you for the data. Rough calculations say the JPEG image size limit is 256 KB on your SPF-83H device. We'll add that to the next AIDA64 beta update that is rolled out in a few hours from now. After upgrading to that, make sure to deactivate random image mode via the AIDA64.INI file, and feel free to set the JPEG compression quality to 99. The image size limiter should be able to calibrate the right file size on-the-fly.
  23. Fiery
    Thank you, but we need the file that was put on your Windows Desktop. It must be there Its filename is SPF LCD Random.jpg. Please also post a USB Dump to let us know about the USB device ID of your SPF. I suppose it will be 04E8-200D In the next AIDA64 beta we'll add the USB device ID to the Preferences / Hardware Monitoring / LCD / Samsung page to ease the job of bug hunting.
  24. Fiery
    We've never had such a setup (ie. using RAID in a mobile computer, or using an ODD drive bay to install a secondary HDD/SSD in a notebook), so I can't really comment on it. But maybe other users of this forum can help you out with suggestions. Regards, Fiery
  25. Fiery
    It's built in AIDA64 latest beta. You don't have to, or can activate it, it works automatically. But it can only work on such devices where we can test and set the actual limit in the AIDA64 code. The only way to find that out is to put a very large JPEG image on the display (that's where the random pixel JPEG image comes into play), and check out how much of the file is properly displayed. If e.g. a 1024x600 pixel random JPEG image is for example 1100 KB sized, and your display can show 47% of it, then we have to set the JPEG image size limiter for your particular device to 1100*0.47 = 517 KB. We've already done that to three SPF variants, but your device may be a 4th that the limiter module doesn't yet cover.
×
×
  • Create New...