Fiery

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

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta It will import the string (REG_SZ) values named: Str1 Str2 .. Str10 And it will also import the 32-bit integer (REG_DWORD) values named: DW1 DW2 .. DW10 Let me know how it works

Please give us a few days to implement that. Once it's implemented, I'll of course send you the list of value names for the requested ten strings and the ten 32-bit integers.

No, the value names has to be fixed, and has to come from a pre-defined list of values, similarly to the previous environment variables solution. BTW, can we drop the environment variables solution and replace it with the Registry based solution?

Check this page: http://ss64.com/nt/reg.html

AlphaCool used to sell a 200x64 pixels monochrome display, but AFAIK it's not sold anymore: http://www.techbuy.com.au/p/82144/COOLING_MISCELLANEOUS_/Alphacool/25417.asp Mini-Box also has a picoLCD 256x64 monochrome display: http://www.mini-box.com/picoLCD-256x64-Sideshow-CDROM-Bay Aquaero 5 (256x64 pixels monochrome) is a nice multi-purpose device, although it's a bit expensive: https://aquacomputer.de/aquaero-5.html Also there's Matrix Orbital GX (240x64 pixels monochrome) that features a very fast USB protocol: https://www.matrixorbital.com/index.php?cPath=40 Then there's Crystalfontz CFA835 (244x68 pixels greyscale): https://www.crystalfontz.com/search.php?q=cfa835&submit=Search AIDA64 fully supports all those displays.

That could work, but IMHO Registry is a superior method. I personally never liked passing values via files. The best method would be using shared memory, to avoid putting a pressure on disk drives. Truth be told, for a developer, using shared memory is more difficult than just setting a Registry value or writing into a text file.

nMedia devices have character based (alphanumeric) displays. They do not support displaying bitmaps. What they do is a neat trick of defining custom characters, in order to show special visual effects. AIDA64 however does not support defining characters for any alphanumeric displays. Regards, Fiery

No, there's no issue about updating the values in the hardware monitoring module of AIDA64. If you check the Config / Environment Variables page, you can see that the changes are not committed in a way that AIDA64 could realize them. Probably using environment variables for such purposes isn't a good idea afterall. We could however pick another method. How about going for Registry? Like using the following path to import values from? HKEY_CURRENT_USER\SOFTWARE\FinalWire\AIDA64\ImportValues

Press Windows key + R (to Run a program), enter: sysdm.cpl On the top row of tabs, select Advanced. Then, near the bottom of the window, push the Environment Variables button.

Thank you. The issue will be fixed in the next AIDA64 beta update due later this month. It will also add more voltages, like DIMM, DDR VPP, PCH +1.0V, VCCIO, and VCCSA.

Thank you, the issue will be fixed in the next AIDA64 beta update due later this month.

What motherboard do you have? I suppose it's not the one in your signature, which shows a Sandy Bridge system

No, apparently not true For test runs we've had to use System Properties / Environment Variables to set the new AIDA64 specific environment variables.

I suppose something got revamped with a recent eScan software update that rendered the current anti-virus detection module of AIDA64 not working anymore about eScan. We'll fix it up and also add support for Zemana later this month.

Are you sure the same user has that variable set than who is running AIDA64? You can verify the list of environment variables in AIDA64 / Config / Environment.

Thank you for the info. Please try to edit the AIDA64.INI configuration file (which you can find in the AIDA64 installation folder), using a text editor like Notepad. Find the following line in there: LowLevelDellSMI=1 And change it to: LowLevelDellSMI=0 Let me know if it helps.

Don't worry, the 5 retries will be removed in the next AIDA64 beta update

You have to set a value for a particular item to make it appear among the other sensor items. It's not possible, since the name of the variable has to be fixed. And no, we do not want to add all possible values You can set an AIDA64-specific variables (A64IMP1..A64IMP10) to the value of another environment variable you would like to see there.

Does it work as you've expected?

What we usually do is put the laptop under heavy stress (like by using the FPU subtest of the AIDA64 Stability Test), watch -- well, hear -- the fans as they spin up (or as the single fan spins up), and then check if the exhaust ports really let hot air get out of the laptop chassis. In many cases, especially when the laptop is over 1 or 2 years old, dust can gather up inside the exhaust ports and that would prevent hot air from escaping the laptop chassis. And when that happens, all components of the laptop get overheated, and usually the system acts weird like throws BSoD or powers off.

Try to update the BIOS to the latest stable one, and then restore all settings to the factory default. Maybe you've used excessive overclock for either the CPU or the RAM, and that made your system unstable. Regards, Fiery

Also, I've just sent you a private message about this issue

Thank you. Your system seems to be equipped with a proprietary sensor chip or Embedded Controller chip that is currently not supported by AIDA64. Quite frankly, we don't even know the name of the chip, since it doesn't appear at any of the place where try to find such a chip Do you have any software that can show you the readings you miss from AIDA64?

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 --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery