Fiery

The DeLock 61854 box has arrived, and we've already put it under heavy test runs Problem is: it doesn't seem to work properly when connected to USB 3.0 ports (of an Etron EJ168 xHCI controller of a Gigabyte GA-Z68XP-UD3-iSSD motherboard), even though we use everything "by the book", with the bundled blue USB 3.0 cable, under Windows 7 64-bit SP1 + all patches installed. Windows can see the VIA VL700 USB 3.0 bridge chip itself, but cannot see the drive that is inserted in the box. When connected to a USB 2.0 port, the box works just fine, and we haven't found any disconnection or dismounting/remounting issues. We've tested it with both a 2.5-inch SSD and a 3.5-inch 7200rpm HDD. We'll continue testing with different USB 3.0 controllers and different motherboards. Meanwhile, can you please let us know what sort of USB 3.0 controller do you have the MediaSonic box connected to?

Thank you for the info. We've tried it with several card readers that were lying around in our labs, and also with quite a few notebooks and HTPCs, but none of them produced an error message with AIDA64. Can you please send us a bit more info on your card reader? The most interesting one would be the USB hardware ID that you can find either in the Device Manager, or on the Devices / USB Devices page in AIDA64. Also, if possible, please post a screen shot of the error message. Quite frankly, the last time we saw such an issue about polling removable media drives was under Windows NT 4.0 and was about Zip drives -- quite a long time ago. BTW, the disk size and free disk space detection code in AIDA64 are (or let's just say: designed to be) exception proof, and so the calls shouldn't produce any Windows error messages or popups, even when there's no disk or media inserted in the removable media slots. It's not the code in AIDA64 that is designed improperly, but there must be something else that causes the issues on your system. We will do everything we can to make sure the issue is fixed, so you can be assured to purchase a flawless product.

Most notebooks (including your HP 4530s) aren't capable of reading out cooling fan speed RPM values.

Thank you for the info. Then I'm afraid we can't do much, unless Asus reveals the method of reading sensor registers out. We've tried every methods known to us, but none of them matches this very interesting motherboard

That is unfortunately due to the UEFI BIOS failing to emulate the classic system BIOS and video BIOS blocks Thanks for the feedback!

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.

Once we implemented the multiple SensorPanels feature, we'll also implement a facility to let you switch between them easily. Regards, Fiery

Thank you, you've got quite a special board We cannot find most of the sensor readings in either dumps so far. Please also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. We hope that dump will help to move forward about this issue.

The new memory bandwidth benchmarks will be multi-threaded, and feature some state-of-the-art tricks as well. They are still not ready yet, they are not mature enough. We need to have 100% confidence in them to switch from the old (and very reliable, very mature) set of memory benchmarks.

AIDA64 OSD Panel cannot be displayed during a full-screen 3D game. We currently have no plans for such a feature. Regards, Fiery

If you want to set up a different solution for starting AIDA64 at Windows bootup, then I think it'd be best to disable the Load with Windows facility in AIDA64, and manually create a new scheduled task in Task Scheduler. Just make sure to name it differently to how AIDA64 calls its own entry, otherwise AIDA64 will remove your task. Service-client solution is not planned at this time.

Many AIDA64 users (including me, actually) have card readers in their desktop or mobile computers, and so far we haven't got any similar bug reports to yours. So we need to find out what's different in your system. Please let us know what motherboard, card reader and operating system do you have. We'll make sure to fix this issue, so you could use AIDA64 without any such error messages.

We still need a SDK for this keyboard...

Thank you. The bug will be fixed in the next AIDA64 release due next week

Do you know a software that can display that info? I'm not entirely sure it can be detected, at least for Direct3D...

If there's no uninstall shortcut in Control Panel, then I guess you deployed AIDA64 via its ZIP package. In that case you just need to remove the files and folders for AIDA64. For a full cleanup, start Registry Editor, and remove the complete AIDA64 folder under: HKEY_CURRENT_USER\Software\FinalWire Regards, Fiery

I'm sorry, but we have no short-term plans for such a feature for AIDA64, but in the long run we may consider it as an addition. Regards, Fiery

Yes, it's already on its way to us, but ****zon isn't fast Sadly in local stores noone had Delock #61854 or the Mediasonic K32-SU3...

1) 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. 2) 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. 3) If it's possible, make a screen shot or photo of the PC Health Status (or HW Monitor) page of the BIOS Setup, showing all temperature, voltage and fan speed readings. It would be a great help for us to have those reading as a reference, so we can calibrate AIDA64 sensor readings accordingly. Thanks, Fiery

AIDA64 v2.80 supports one QVGA and one monochrome Logitech LCD screens in the same time, as long as the Logitech driver properly handles both screens. If you can configure both screens individually with Logitech LCD Manager, then AIDA64 should also be able to handle both screens. What Logitech drivers do not support is having 3 or more LCD devices, or 2 devices of the same type. So two QVGA LCDs is a no-go.

Please describe the issue more detailed. What exactly do you do, and what happens? Thanks, Fiery

Thank you for your suggestions, I think they're both great ideas, so we'll try to implement them soon. Regards, Fiery

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

It will work the same as now, but instead of 16 logical processors it will support 32. When it comes to CPU utilization measurement, it makes no sense to skip the virtual cores, since their utilization impacts physical cores as well.

When you say "render mode", what exactly are you looking for? Screen resolution and bit depth perhaps? Thanks, Fiery