Fiery

Vertical bars are already supported. Just specify a smaller bar width than bar height, and it will automatically be rendered as a vertical bar.

That would make configuration a hell of a job, so no, I'm sorry, we wouldn't want to do that. You can put those values as regular text output or bars to see the value in a greater resolution. Gauges are more for the show, and less for representing accurate readings.

We've done more test runs under Win10. It seems our 800P (and I suppose your device too) has a firmware issue that prevents it working 100% reliably under Win10. After Windows shutdown and booting the PC up again, it works just fine. But, if we do a Windows restart or put the PC to sleep, the motherboard no longer sees the SPF connected via USB. So the device will not be present among other Windows devices, and so it's not a driver issue at all, and not related to AIDA64 either. The solution may be to disconnect the device from the USB port and connect it again after a system restart, or to power-cycle the frame to get it working again. The good news is: as soon as we can get our 800P to be seen by the motherboard and Windows again, as a connected USB device, it works 100% reliably. So the only problem is when it disappears from the USB bus after a system restart or sleep, but once it is recognized again by Windows, it works just fine. I'm not sure if this issue can be fixed by a firmware update, but it may worth a try to contact Samsung about it.

It would be possible, but AIDA64 already has hundreds of options, so we try to stay away from adding even more, if possible. IMHO it would be annoying if you would have to wait for AIDA64 up to a minute after you've connected your SPF device. But it's a good idea to limit the polling frequency, so we may go for 5 seconds or 10 seconds. It should be a good compromise between too frequent polling and long waiting for AIDA64 to pick the newly connected device up. It would be quite annoying, since then you would quickly find yourself beyond the 5 minutes limit, and then you'd have to restart AIDA64 -- just like now. We will do a few test runs to see how quickly we can poll for new device arrivals. If it can be done in a few milliseconds, then frequent polling will not be an issue on modern PCs afterall.

As I've said above, the LCD module doesn't support hot-plug at all, so we have to hack it into the LCD framework on a case-by-case basis. We prefer not to do that, since in some cases it could cause unnecessary stress on the system to keep polling for the arrival of the LCD device. Just imagine you have the SPF support enabled in AIDA64, the LCD update frequency set to 500 millisec (or even lower), you keep using your SPF happily, but then one day you sell the SPF or just put in the drawer, and you forget about leaving the SPF support enabled in AIDA64. If hot-plug is not supported, this isn't an issue, since AIDA64 only checks for the presence of the device once per session. So if you never use the SPF device again, but you leave it enabled in AIDA64, it will just do the scan once, right after you start AIDA64. On the other hand, when hot-plug is enabled, and you forget about having the SPF support enabled, and you never connect your SPF device anymore, then AIDA64 will keep scanning the libusb0 bus twice or even more times a second, in an endless loop. It may not cause all that high of a system load on a modern PC, but IMHO it's still something you should avoid. If you're a power-user who knows exactly what he's doing, this of course will not be a problem So to sum up: hot-plug is great, but we prefer not to implement it, unless multiple users request it

Those temperatures are just fine for a properly built + overclocked system like yours. You should run the AIDA64 System Stability Test for at least an hour, but a few hours is even better. If you try to challenge the stability of your configuration, then have all subtests enabled. On the other hand, if you try to challenge the thermal solution (cooling setup) of your system, then only have the FPU and GPU tests enabled. Those will drive your CPU, motherboard and GPU to the highest temperatures in the same time, so you can see an absolutely worst case scenario about thermal stress that way. If it's stable, then why not?

It's because AIDA64 only detects Samsung frames at its startup, and if it can't find any, it will simply give up and wouldn't try to find it again. In other words, it doesn't support hot-plug feature for Samsung frames right now. We'll fix that in the next AIDA64 beta update

We'll try this, although in theory it should work flawlessly. The important thing to learn about Samsung frames is that they have 2 distinct working modes. The default mode is the Mass Storage Mode, during which you can access the built-in memory of the frame to copy photos to it. In that mode you cannot transfer images to the frame to get displayed directly. You have to switch the frame into Mini Monitor Mode to do that. In these 2 modes the frame uses a different USB device ID, so Windows will see the frame as if it was 2 different physical USB device. You don't need to install a driver for the Mass Storage Mode, since it uses the built-in Windows driver for mass storage devices. But, once the frame transitions into Mini Monitor Mode, Windows will not find a proper driver for it, and you have to install the AIDA64 libusb0 driver to make it work with AIDA64 -- and in theory any other software that may handle Samsung frames in Mini Monitor Mode via libusb0 API. You only have to install the libusb0 driver once. The next time you restart your computer or power-cycle the frame, it will switch back to the default Mass Storage Mode, but once you start AIDA64, it will transition the frame into Mini Monitor Mode, and a few seconds later you should see it working as expected. There should be no need to install the driver again and again, since once the frame transitions into Mini Monitor Mode, Windows should be able to pick up the previously installed libusb0 driver from its driver store. I'm not sure however whether it's a good idea to install the .INF file via right-click context menu. It may be best to right-click on the installer_x64.exe --> Run as administrator. Or, go to the Windows Device Manager, find the unknown device, right-click on it --> Properties --> Driver --> Update Driver, and select the folder where you've got our libusb0 driver uncompressed into.

By default AIDA64 will use the IPMB driver if installed. If not, it will use KCS, and if it's not available, finally it will try to use SSIF. All those interfaces handle IPMI directly, not via network, so they're local interfaces. In theory I guess it may be possible to develop a special IPMB driver that works via TCP/IP, but I'm not sure if anyone did that already or not.

I'm sorry, but that didn't answer my question. If you have problems explaining the issue in English, then please post it in your native language, and I'll try to figure it out using Google Translate. Please describe the issue with as much details as possible.

1000P should work similarly to 800P. If it's possible, please let me know the exact steps you perform to try making your SPF work with AIDA64, and the unexpected results that you get. We will perform the same steps on our Win10 test system, and try to reproduce the issue.

Thank you, we'll check it out

Thank you for posting your solution.

We've added support for Jack Trowbridge's Noteu v1 LCD, as described at: http://www.noteu.co.uk http://www.kickstarter.com/projects/jackt/noteu-facebook-email-paypal-at-a-glance You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Noteu. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Saitek X52 Pro and Pro Flight Instrument Panel displays are also supported now by the latest AIDA64 beta. Regards, Fiery

Where do you get this error message in AIDA64? Do you click on a particular page in the left page menu, and then the error message comes up?

I'm afraid that's not possible. But, here's a new AIDA64 update that now implements support for all 4 rotation options (0 degrees, 90 degrees, 180 degrees, 270 degrees) for AlphaCool and Samsung SPF LCDs: http://www.aida64.com/downloads/latesta64xebeta

Here's a new AIDA64 update that implements support for all 4 rotation options for Samsung and AlphaCool LCDs: http://www.aida64.com/downloads/latesta64xebeta

We've tested it with our Samsung 800P device and Windows 10 Pro Insider Preview Build 10159 64-bit, and found no issues. Our libusb0 driver installed and operated just fine. All you need to do is: 1) Connect your 800P to the USB port of the motherboard, wait for Win10 to install the default mass storage driver (just like for any other flash drive or card reader) 2) Start AIDA64, enable Samsung LCD support. The device will be switched to mini-monitor mode, and you'll see that Win10 will try to find a driver for it, but will fail. Press the OK button on the AIDA64 Preferences window. 3) Close AIDA64, install our libusb0 driver via Device Manager. 4) Start AIDA64 again, and it should work now. You only have to perform those steps once, as the initial installation of the device.

It is listed as Installed RAM on the System page in the AIDA64 for Windows Phone app. Regards, Fiery

Thank you for the feedback. We're doing more test runs, and we may remove the keep-alive option and always send the packet at frame initialization. We'll use a combobox (drop-down list) to let you select one of the 4 rotation modes.

Zen will have a hard time competing against Broadwell-EP, which will also debut 2 or 3 quarters before Zen. We'll see

As far as I know, AlphaCool displays only support backlight on/off setting, but no brightness or contrast adjustment

Thank you

Yes, we can. That 20-core test system of ours is bottlenecked by the memory subsystem. Even though the 20-core system has got let's say 4.7x more processing power, it's only got 1.75x more memory bandwidth than the system your screen shot was made on. Speedup is only linear in such benchmarks that do not rely heavily on the memory subsystem, like FPU Julia.

It's unfortunately normal. When the key is stored on a VLM server, AIDA64 will show the quoted key as it is stored in the local Windows Registry. Regards, Fiery