Jump to content
AIDA64 Discussion Forum

Leaderboard


Popular Content

Showing content with the highest reputation since 10/07/10 in Posts

  1. 4 points
    Some new gauges. LOAD and IDILE. If some like it, leave coment and i sent you on you email. I have for LCD and sensor panel in ( Large and medium sizes ) in png
  2. 4 points
    Hi guys I'm new here on forum, so... My name's Pav, i'm from Navan (Ireland).Today i've created my first sensor panel MIDNIGHT(based little bit on sunj's work. Thanx man ). Hope you like it. preview: And on my desktop: MiIDNIGHT.sensorpanel
  3. 3 points
    Got a bit carried away with XCOM2 and hunting down a (possible) memory issue...
  4. 2 points
    New Text Version, uses on Desktop > text_v2.sensorpanel Adapted to 5 Inch Dispaly with 800x480 Pixels > PiDisplay.sensorpanel PiDisplay.sensorpanel text_v2.sensorpanel
  5. 2 points
    Ok cool I'll see what I can come up with for ya we can fine tune it later on ...
  6. 2 points
    This is a real layout GA-Z77X-UD5H. Panel size 1000x792 GA-Z77X-UD5H.2015-11-20.sensorpanel I have layered .psd file.
  7. 2 points
    This is the sample SensorPanel used in AIDA64 2.50 what's new page. This utilizes the new gauges and graphs. 250release_sample.sensorpanel
  8. 2 points
    THX, it's a great Feature ;-) My Actual LCARS / BW setting, 1024x600 to Display on a GalaxyTab 7" via iDisplay:
  9. 1 point
    Havent seen any like this before, hopefully this gets some creative juices flowing. I think the use of urls is very under used. Might not be practical depending on pc/screen layout, but my pc is right beside my monitor, so its nice to have a little extra screen space. 3rd pic shows all clickables. Been tweaking this for a few weeks, links open on sensor display resized like the Netflix window(in 2nd pic). links included: Almost everything is linked to a function related to the pic: Buttons -security cam, voip phone ,chrome, discord, games library, task manager window=weather app key = lock pc speakers/headset = switch sound output and open mixer keyboard = emails door= powerdown lcd = change between multimuniter setups
  10. 1 point
    Hi! Last year, I was looking for a display to show different information on my home theather computer. I wanted a display to fit in a 5" 1/4 bay and no LCD technology as I don't want backlight that lights all my room when I watch a movie (high contrast required). Then I discovered the 3.2" monochrome OLED display ER-OLEDM032 based on SSD1322 chip. Support in Aida64 was implemented by Fiery. It looks great! Infinite contrast of OLED technology is perfect. 4 different models exist for 4 different colours. Blue: Green: White (what I chose): And yellow: Dimensions: 4 protocols are available. Protocol to be used is set using bridges on the display PCB. 6800 8-bit parallel 8080 8-bit parallel 3 wires SPI 4 wires SPI 6800 and 8080 are obsolete as we don't use anymore parallel port. I chose 4 wires SPI rather than 3 wires SPI because communication speed is a bit higher. To convert USB to 4 wires SPI, I used a FTDI UM232H-B-WE breakout module based on chip FT232H. Here is the schematic of connections between USB breakout module and OLED display:
  11. 1 point
    On Asus AM4 systems it's safer with the Asus WMI sensor support enabled. Without it concurrent access by AIDA64 and the motherboard BIOS can cause collisions that may just end up in fan duty cycles messing up. Please note that even though the new Asus WMI ACPI interface was invented and designed to avoid those collisions that plagued the Asus AM4 platform since the very beginning, the interface is poorly implemented in multiple Asus motherboards. It is also not implemented all across the board. So while it's a great thing in theory, in practice it causes a lot of headaches. All you can do is put more pressure on Asus to fix this issue in a future BIOS update.
  12. 1 point
    Make sure to upgrade to the latest beta version of AIDA64 Engineer available at: https://www.aida64.com/downloads/latesta64eebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  13. 1 point
    It is detected using various detection methods and built-in hardware databases. It's not possible to edit that string.
  14. 1 point
  15. 1 point
    Actually, the AIDA64 app doesn't need to be unconfined (even if it has some special permission) so you can upload it to the OpenStore without requiring a manual review, so without the need to publish the source code (but if you changed idea and want to publish, it's welcome ) and choosing a proprietary license (as said by @mateo_salta) Thanks
  16. 1 point
    We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems. The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component. Most likely that component is used for GPU profiling. And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable. We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted. Here's the new AIDA64 beta build that includes the workaround: https://www.aida64.com/downloads/latesta64xebeta
  17. 1 point
    Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  18. 1 point
    I've sent you a private message about this issue.
  19. 1 point
    It's due to the difference in motherboard and CPU as well.
  20. 1 point
    It's not supported yet. We've just ordered a unit, and we'll implement support for the Commander Pro protocol as soon as it arrives. I'll let you know in this topic once a new AIDA64 beta -- with the protocol implemented -- becomes available for download. It shouldn't take more than 2 weeks approx.
  21. 1 point
    Thank you, I'm glad things are going in the right direction
  22. 1 point
    If the drive has a very smart controller that desperately tries to hide the fact that the capacity is less than the advertised value, then for a while the Random Write + Verify test may not report any issues. Especially when the performance is that freakishly low With such an underperforming drive you would have to let the Random Write + Verify test run for at least 2 days to draw any meaningful conclusion. Good old fraudulent pendrives which perform adequatly (like 20-30 MB/s) are usually caught by the test in a matter of minutes, sometimes few seconds only. But it's always best to let the Linear Write + Verify test to complete to 100%, since that's the only sure way of knowing that the drive can be filled 100% with data, and all data is fully retained (stored) by the drive.
  23. 1 point
    Here is mine, made to match some desktop gadgets I like to use. sensor.sensorpanel
  24. 1 point
    Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://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
  25. 1 point
    Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps
  26. 1 point
    this is my first try at this. haven't got around to labeling everything yet, but i made this one for my remote lcd panel. does anyone know if a lower update rate will impact system performance for remote lcd? as in like 500ms?
  27. 1 point
    Thank you. The lack of proper sensor readings is due to the fact that AIDA64 is unable to use its kernel driver. That could be because the kernel driver file (KERNELD.X64 or KERNELD.X86) is missing, or your Windows user has no administrator privileges, or a Windows prevents to elevate the security privileges of AIDA64.
  28. 1 point
    Thank you! We don't have any presets available, but you can use some of the SensorPanel layouts other users posted to: https://forums.aida64.com/topic/667-share-your-sensorpanel/
  29. 1 point
    I'd start with: 1) Update motherboard BIOS to the latest one 2) Set memory module timings to a more relaxed setting, dictated by the classic SPD block rather than the XMP (Extreme Memory Profile). If that still doesn't help, then I'd try it with 2T Command Rate (tCR or tCMD) setting as well. If none of those help, it could still be a faulty memory module, a dying motherboard or a faulty PSU. Not easy to diagnose such issues though If you have a chance to borrow a reliable PSU, it would worth checking that too. Regards, Fiery
  30. 1 point
    Then I suppose the issue is that AIDA64 sets the fan speed to its default value (or the one you configured as Asetek fan speed), but then Corsair Link software will override that when it is running in the background. That's a collision that we cannot avoid on our end, and is caused by the improper USB API that some Asetek-6 based water coolers use. The problem is that you cannot detect water cooler temperature and fan RPM reading without altering the fan duty cycle (%) setting So you have to send a duty cycle value in order to get sensor readings back.
  31. 1 point
    Please don't mix PCH and PCH Diode temperatures. The first one comes from the onboard sensor chip, if it supports that readout. The latter comes from the PCH (chipset) itself, if it supports it. The latter doesn't need motherboard-specific support, so we cannot add it. Your PCH either supports the readout or not, and your BIOS either configures the PCH thermal controller properly or not.
  32. 1 point
    That's because AIDA64 currently supports "only" up to 14 misc fans We'll expand that to 20 fans in the next AIDA64 beta update
  33. 1 point
    I don't think so. What could happen is a faster battery discharge when you keep AIDA64 running in the background to monitor your notebook. Monitoring hardware uses a few percentage of CPU load, and that causes higher overall system power draw than without it.
  34. 1 point
    The mentioned new AIDA64 beta update is available for download 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
  35. 1 point
    Hi, The Portuguese language needs improvement and it will be better with the AO 1990 that is more than in use now. Eg., Max. Visible Display Size=Tamanho de visão máximo -> Tamanho de visualização máximo Picture Aspect Ratio=Relação de aspecto da imagem -> Formato da imagem Viewing Angles=Ângulos de Visão -> Ângulos de Visualização Input Connectors=Conectores de Entrada -> Conetores de Entrada Embedded=Embutido ?!?!?!? -> Integrado or Incorporado ATA Device Features=Características do Dispositivo ATA -> Funionalidades do Dispositivo ATA Track-to-Track Seek=Busca pista por pista --- Busca?!?!?!??! Max. -> Máx. Por favor -> Por favor, etc... Regards, MS
  36. 1 point
    The issue will be fixed in the next AIDA64 beta update due in a few days from now Regards, Fiery
  37. 1 point
    That only means the Strike7 SDK causes a crash in its DLL, and that pulls AIDA64 main process down with itself I'd be happy to help you out, but at this point we both are at the mercy of Mad Catz. If they could try this out and find the issue in their SDK and fix it up, that would of course fix this whole thing. Or, if they can find an incompatibility between their SDK and AIDA64, then we would be happy to work with them to resolve it. The main problem is that we cannot reproduce the issue on our own Strike7 keyboard. If we could do that, things would probably be a bit easier. Please try to put a bit more pressure on Mad Catz, as a customer who's having issues using their product.
  38. 1 point
    It depends on the actual protocol your LCD uses. In theory, AIDA64 is well prepared to support virtually any LCD devices that can display a bitmap image directly. It already supports over 50 different LCD protocols, and a wide range of connection options, including USB, WiFi, LPT (parallel), COM (serial). It would be important for us to understand what exactly needs to be done to push a bitmap image into your LCD screen, so please share any technical detail you've got on that. If it uses a proprietary protocol that you wouldn't wanna share with others, then please drop me a private message with your email address, and we'll continue discussing this in email. Thanks, Fiery
  39. 1 point
    It is Logitech's DLL, part of the Logitech G-Series driver package called LgLcdApi.dll. Try to reinstall the drivers, it should help.
  40. 1 point
    Nice 1st post, thank you And you've got quite a fleet of PCs
  41. 1 point
    1) Do you have 2 or 4 processor sockets populated? 2) Do all processors have DDR3-1333 memory installed? So every processors use the same memory configuration? In case you have 4 processor sockets populated, and every processors use the same DDR3-1333 memory configuration, that would mean you've got 16 memory channels total, each running at DDR3-1333 speed, which would mean a total memory bandwidth of 166.6 GBytes/sec. Hence the results could well be accurate The confusion may come from the fact that AIDA64 (the main application itself) only supports up to 32 processor threads, so it cannot show you all processors on the Cache & Memory Benchmark Panel. However, the multi-threaded memory benchmarks support up to 64 processor threads, so it can utilize all 48 processing threads you've got in your system (if you have all 4 processor sockets populated, each with a 12-core Magny-Cours CPU). Regards, Fiery
  42. 1 point
    Thank you. I think the reason why we cannot find the sensor readings is that your motherboard has an IPMI BMC chip, and the sensor readings are only available via IPMI Sensor calls. Problem is: via direct IPMI KCS interface AIDA64 doesn't seem to be able to communicate with the BMC chip. Do you have an IPMI driver installed? If not, can you please try to install one? Maybe with the IPMI driver installed, you would be able to see the IPMI Sensor readings on the Computer / IPMI page.
  43. 1 point
    To make AIDA match the look of my Windows 8 box, I have spent some time designing a sensor panel. Here is the result (click here to download the sensorpanel config file).
  44. 1 point
    In such special case the lowest number of nodes (5) would be suitable. Extreme Engineer has no remote capabilities. Regards, Fiery
  45. 1 point
  46. 1 point
    Thank you. If you have a chance to borrow two identical DDR3-1333 modules from a friend, then it would worth checking out whether it makes a difference. If you cannot do that, then it may worth playing around with the memory modules, because there may be one or two weak ones amongst the 4 modules you've got installed. Try removing two, and check out if it changes anything. If not, then try replacing the two installed modules with the ones you removed previously, etc. Make sure to have the 2 modules always placed in the DIMM slots that makes the chipset operate optimally (dual-channel; first DIMM slots usually). I apologize for not being able to provide better ideas on troubleshooting. Remotely it's usually quite difficult But what you did so far (installing a better CPU cooler and a new PSU) were both good steps in trying to hunt down the cause of the hardware issue.
  47. 1 point
    Yes, that's our suspicion too. We already have a theory about where the Shared Memory feature piles up the handles, but it's not easy to reproduce and verify it. We'll work on it in the upcoming days, collect feedbacks from other beta testers as well, and hopefully we can fix it up soon.
  48. 1 point
    That's a neat layout
  49. 1 point
    The gadget requires AIDA64 to be running. You can hide AIDA64 main window by double-clicking on its System Tray icon. Regards, Fiery
  50. 1 point
    Hey, I know this thread is somewhat old, but I was looking to start a thread where everyone posts their sensorpanel display; apparently this one was already here, so I figured I would just join the party. I have had Aida 64 for some time, and have been using the OSD. I somehow caught wind of the sensor panel just last night (I didn't know about it), and after a few hours this is what my display looks like (this is my left monitor). I'm quite happy with how it came out, and I thought I would share.
×
×
  • Create New...