Fiery

Please note that not all anti-virus software are capable of providing the known virus count to 3rd party applications like AIDA64. Approx. half of the anti-virus software that AIDA64 recognizes do not provide that information Regards, Fiery

At least a few hours for both tests. Ideally, 12 or more hours, if it's possible.

Renting is not an option, since we would have to re-measure the benchmarks in the future when a particular benchmark method gets updated. Not to mention the cases when new benchmark methods are introduced. So renting wouldn't work, and those companies you mentioned do not have an incentive to provide us with hardware. BTW, in the benchmark reference list of AIDA64 we do have a Haswell-E based system, so the platform itself is not neglected by us. And by not using the highest end CPU available for a particular platform, AIDA64 users have a better chance to beat the reference results

The FPU test, when used alone, is the most demanding stress testing method, since it uses AVX and FMA instructions to heat the whole CPU package up as much as possible, and puts the highest load on the CPU. It's not a diverse stressing though, since it focuses on the thermal stress, so we generally recommend to run the FPU subtest for a few hours, and in case the system can stand it without issues, then run a mixed test as well, by enabling all subtests (including FPU).

Thank you for your feedback

Ah, you mean the UEFI Specification release I'm sorry, that's an entirely different version number than the UEFI version that your motherboard currently has flashed into the firmware chip. I'm afraid we have no information on how to detect that property. In other words: it most likely means it's not possible to do that.

We've checked it, and the Spotify Windows client does not seem to offer a SDK that would allow AIDA64 to read song title information from Spotify Regards, Fiery

UEFI is the successor to BIOS. It's simply the firmware of PC motherboards. BIOS was first, and then it was phased out in favor of UEFI. UEFI ("BIOS") version for your motherboard is P4.00.

We usually recommend closing other processes, windows and if possible, background services as well, at least for the first run. After the first run is successfully finished, you can use different stress testing scenarios, like having multiple stress test software running in parallel. Regards, Fiery

I'm afraid we have no plans to support POP3 email checking at this time.

You have to use the Move Up button in the SensorPanel Manager to move the background image to the top of the list. The list is arranged as a Z-order, so the first entry is placed on the bottom of the Z axis, and the next one is placed on top of it (higher on the Z axis), etc.

UEFI version should be reported as BIOS version already. If you cannot find it on the Motherboard / BIOS page, then try to find it on the Computer / DMI page.

There was an unfortunate bug in AIDA64 Beta Build 3429. We've just rolled out Build 3435 that should fix it up: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works.

We've tested the AIDA64 LCD module with Yocto-MiniDisplay and Yocto-MaxiDisplay, and they both worked flawlessly. But those are quite little screens, compared to a photo frame. And they do not feature buttons to change pages.

We've edited the first post, thank you. How about using your cell phone or tablet display as a wireless LCD for AIDA64? http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/

AIDA64 uses an unofficial, non-documented interface to communicate with Samsung SPF devices. If it doesn't work on your device, then I'm afraid we cannot help you out Only one thing you can try: in case you have a complicated LCD layout, you can try lowering the JPEG quality, but about the 5-seconds issue I don't think that would help

You can enter symbols only when they are ANSI characters. AIDA64 doesn't support Unicode characters or Unicode strings.

The reference benchmarks list that you can find in AIDA64 only includes such systems that we have got in our R&D labs. Those systems are under our strict control to make sure the reference performance scores obtained on them are always dependable.

I'm glad you've managed to make it work

It is usually caused by a storage controller driver. Updating the driver sometimes helps, but not in all cases. If you want to disable RAID scanning, close AIDA64, go to AIDA64 installation folder, find AIDA64.INI file, and open it in Notepad. Then find the following two lines ... LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 ... and alter them to: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 In case you cannot find an AIDA64.INI file, then create one, and write the following 3 lines into it: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 Regards, Fiery

It looks great!

LCDsysinfo displays -- both the original version and the newer GOverlay -- is cheap for a reason. It is a very limited device that doesn't support direct bitmap image transfer/display via USB connection, and so it cannot be supported by AIDA64. Yes, it is possible to put AIDA64 measurements to LCDsysinfo displays, but only by using LCDsysinfo's own software solution that is a lot more constrained than AIDA64's own LCD module. What makes more sophisticated displays more expensive is the underlying microcontroller that drives the display and makes it possible to transfer bitmap images over USB. Without that, the communication protocol could only support basic commands like "Display a letter A at X=2,Y=1 position" or so. You can display fancy text that way, but not full-blown graphics. Make sure to check every screen shots and other material that you can find about LCDsysinfo online, including the screen shots for their companion software that you use to configure the display. Also check this review: http://www.techspot.com/review/704-lcdsysinfo-for-goverlay/ There's a slim chance that LCDsysinfo would still fulfill your needs, and I don't mean to bash those devices at all. I just wanna make sure you don't fall into the trap of a low price tag BTW, we do have one piece of most of the USB-connected LCD devices out there in our R&D lab, including all those mentioned in this topic. So we do have a first-hand experience on the capabilities and constraints of all the LCD devices that AIDA64 supports.

I don't know about the cheapest option for your specific requirements, but you've got the following options: - AlphaCool 200x64: may be difficult to source - Crystalfontz CFA835: $86 - Matrix Orbital GX Typhoon: $99.95 - picoLCD 256x64 Sideshow: $54.95 or $59.95 Maybe there's more, but those are the most well-known 5.25-inch form factor options that all work well with AIDA64. Note that even though Matrix Orbital GLK would technically work with AIDA64, it has a very slow update rate in gfx mode, so I wouldn't recommend that option at all. Matrix Orbital GX is a far better solution: it's got a very quick gfx update rate that works great with AIDA64.

Please note that we will revamp the active memory channels enumeration in the next AIDA64 beta build (due in a few days from now), to avoid showing confusing information on the Cache & Memory Benchmark panel.

Battery charge rate is only support by Android 5+ systems. It doesn't depend on the SoC model, but only on the Android version. Regards, Fiery