Fiery

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

Please contact ABSEIRA for further assistance about AIDA64 Business Edition setup in Group Policy environment: info AT abseira.com (replace AT with @) Thanks, Fiery

\\share\reports.mdb looks a bit odd. Are you sure that's the UNC path you want to use? Also, make sure to provide your network users write permissions to the reports.mdb file. The rest of the settings and parameters you quoted seem fine and accurate.

Please read the AIDA64 Business Edition Setup Guide. http://www.aida64.com/files/AIDA64_Business_Edition_Setup_Guide.pdf It will provide you with all the answers and guidelines to deploy AIDA64 Business Edition in your organization. Regards, Fiery

I suppose the message comes up when AIDA64 tries to enumerate the local disk drives. Do you have any removable disk drives (apart from optical drives) in your system? Such as floppy drive, ZIP drive, tape drive, or a card reader. If yes, then try to insert a media in the drive, and see if it makes the error message come up or not.

In such special case the lowest number of nodes (5) would be suitable. Extreme Engineer has no remote capabilities. Regards, Fiery

"5 nodes" means your network has 5 computers, including workstations and servers. If your network has 50 computers, then in theory you would need a Business Edition license for 50 nodes. I'm not sure however, why would you only use it on 3 or 4 computers. Can you please explain? In most enterprises AIDA64 Business Edition is uses on every workstations and servers, to compile a network audit for the whole enterprise. Such companies however, that only wants to use AIDA64 for troubleshooting hardware and software issues will buy the AIDA64 Extreme Engineer license. AIDA64 Extreme Engineer is licensed per engineers, so if you have e.g. 2 network administrators in your company who would use AIDA64, then you need 2 Extreme Engineer licenses. For more information make sure to contact ABSEIRA, our worldwide distributor for corporate products: http://abseira.com Regards, Fiery

Can you please check if you experience the access violation issue with Build 2320? http://www.aida64.com/downloads/aida64extremebuild2320tjb6lpwyzxzip We've implemented CPU Throttling monitoring in Build 2317, so if 2313 works fine but 2320 fails, then there's a chance CPU Throttling monitoring causes the issues. Thanks, Fiery

We've tried AIDA64 on our Sapphire HD6850 that we've overclocked from the default 1.150V Vcore to 1.168V using Sapphire TriXX 4.6.0 (latest version). On this particular video card AIDA64 reports the default Vcore (VID) as "GPU Core" voltage, and reports the actual Vcore used by the GPU as "GPU VRM" voltage (via the onboard CHL8214 VRM). Since on CHL8225 and CHL8228 chips we do the same method of voltage measurements, I'd expect the same behavior from AIDA64 there as well. BTW, we use ADL_OverDrive5_CurrentActivity_Get call from ADL to measure VDDC that we report as "GPU Core" voltage. On CHL8214 we report register 0x8D as "GPU VRM" voltage. On CHL8225 and CHL8228 we report register 0x8B as "GPU VRM" voltage.