Fiery

We will implement support for up to four EVE2/EVE3 displays in the next AIDA64 beta update. I will post a message into this topic once the new beta build becomes available for download.

Are you planning to use more than four EVE LCDs in the same time?

Thank you for the data. The issue will be fixed in the next AIDA64 beta update. I will post a message into this topic once the new beta build is available for download. Till then, I hope you're having a Happy New Year too!

Thank you for your feedback

Multiple LCD devices from the same kind is supported for several protocols (AlphaCool, Aquaero, Crystalfontz, Cwlinux, EastRising, EVGA, LCDInfo, Phidgets, picoLCD, Razer, Saitek, Trefon, Yoctopuce) already, but not for the Matrix Orbital EVE. We can implement that, but first we need to check whether it's possible. Let me know if you're committed to that setup, ie. you want to get two EVE displays.

We've made it possible in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've figured it out. It's actually working, but you need to add the USB LCD Page to the list of available pages on your Aquaero device. The way to do it is: open Aquasuite X, in the left menu select aquaero --> Information pages --> Information pages --> in the Available sreeens drop-down menu select Miscellaneous --> grab the page called USB LCD page (in the left column) and drag & drop it into the right column (called Displayed screens). Now you have the page that displays AIDA64 LCD data among the pages you can choose from on your device.

Thank you! On the Motherboard / SPD page not even one memory module is displayed correctly? As for the BCLK, somehow AIDA64 is unable to use the PM Timer on your motherboard to measure APIC Clock (which equals to BCLK). Please post a screenshot or a copy-paste of the FACP sub-page of the Motherboard / ACPI page of AIDA64, so we can check what's reported there.

The full list of current IID's are in the AIDA64 Business user's manual. We do not have more IID's defined, and we do not associate an identifier to the other lines displayed in the reports simply because they're thousands of lines. We can extend the list of IID's by a sensible amount if you have specific requests. It shouldn't be hundreds though, since that would again defeat the idea of IID's and slow down the operation of the AIDA64 Audit Manager and Change Manager. If you have such IID requests, please send me your email address, company name and AIDA64 product key in private message, and I will contact you in email for further details.

Please 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. 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 --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Such monitors that you can connect to your PC using a DSub, DVI, HDMI or DisplayPort port, should be able to work as a secondary monitor and as an extension to the Windows Desktop. In which case you can use the SensorPanel module of AIDA64 to display sensor readings on any of the connected monitors.

As I've mentioned in email, we're already working on the bug fix. Please give us one or two days to investigate this rather strange and erratic bug.

I'm afraid we have no Supermicro X11 motherboards among the over 100 test motherboards we use daily to check out whether AIDA64 performs well on them. In case Supermicro could send us one sample of such a motherboard, we can work on it of course.

RComment is always filled with the Computer Comment (a.k.a. Computer Description) value that you can set in Windows / System Properties / Computer Name.

LCD exporting takes all LCD pages and writes them to the export file. If you open the .RSLCD files using Notepad for example, you can see that each page content is between similar tags like this: <LCDPAGE1> ... page content ... </LCDPAGE1> If you have multiple RemoteSensor layouts created, and you always used Page 1 in those layouts, and exported them to separate .RSLCD files, you should have LCDPAGE1 tags (and only those, not LCDPAGE2, LCDPAGE3, etc) in all those files. Problem is: when you import a layout, it will wipe your current layout, all pages of it, and import the page (or pages) from the .RSLCD file you select. Currently it's not possible to import a .RSLCD file into a page of your choice, so even if you alter the files to have different LCDPAGEx tags, you will only be able to import a file into a specific page but the rest of the pages will still be blank. What you can do to overcome this limitation is to combine the .RSLCD files into a single .RSLCD file where you use multiple page tags and put the relevant content between them. For example: <LCDVER>200</LCDVER><SWVER>6.20.5321 Beta</SWVER> <LCDBGCOLOR>16777215</LCDBGCOLOR> <LCDPAGE1> ... page content coming from one of your .RSLCD files ... </LCDPAGE1> <LCDPAGE2> ... page content coming from another one of your .RSLCD files ... </LCDPAGE2> <LCDPAGE3> ... page content coming from the 3rd .RSLCD file ... </LCDPAGE3> That way you can combine your .RSLCD layouts to exactly the page assignment of your choice.

IMHO it should be fairly easy to do that without altering AIDA64. For example, you can add the ISequel field to the Item table, and use a script to scan the table for multiple instances of "Monitor Name" and fill the ISequel fields accordingly. You only need to do it once, for those lines where ISequel is not yet filled in, so it shouldn't be a constant resource-hogging process to be running on your SQL server.

You can use the /LOCATION command-line option to pass your custom location and make AIDA64 write it into the RLocation field of the Report table. Example: AIDA64 /R null /DATABASE /HW /LOCATION MainHQ

It's not possible to cherry-pick from the reference results I'm afraid. And when it comes to "similar systems", it's not easy to decide which one is similar to the current system. You could go by CPU vendor, number of cores, CPU socket, CPU clock, etc.

The current way is fine for us.

RLocation was defined to help companies with multiple sites/locations manage their data. It's intentionally left empty so you can fill it up if you need that field for each report/computer.

The background (automatic) report creation process is designed to not slow the computer down. In case your users have difficulties using their computers while the report is being created in the background, then I suppose those PCs must be very old and very slow anyway. Is that the case? BTW, you can use the /IDLE command-line option to change the process priority of AIDA64 to idle, which could help to improve user experience during automatic background report creation.

It's not possible to assign an IID for everything that AIDA64 puts into the reports simply because then the number of IID's would be 100 times more than right now, and that would slow down the processing of reports by the Audit Manager and Change Manager modules of AIDA64. We keep adding new IID's on a case by case basis, per customer request.

It's completely logical, because the target report file in that case would be a text file with the .ADO extension. In that file AIDA64 will put an error message in case the report cannot be inserted into the database. Due to e.g. SQL misconfiguration or such. If you don't want to have that output, you can specify a non-existing filename that cannot be created anyway, like C:\?

It'd be best for you to put all Event Logs records into your database and then use SQL queries to filter them to your preferences.

We do not have plans to enable such filtering for the Event Logs page. You seem to be a corporate user of AIDA64, so once you've collected the reports you can filter them by using any criteria you wish, using e.g. SQL queries.