Fiery

AIDA64 still implements full support for Win95/98/Me and Windows NT 4.0. It has a Win2000 icons style which has 16-colour icons as well as 256-colour icons. We consider that a pretty solid support for those obsolete operating systems. Please note that the combined percentage of Win95 + Win98 + WinMe + NT4.0 users out of the total AIDA64 users base is less than 0.01%. It means we cannot afford to put more development resources into such obsolete systems, but instead we need to focus on the current Windows variants, and for the upcoming Windows 8 and Windows Server 8. Regards, Fiery

Please also attach or copy-paste an ISA Sensor Dump. Thanks, Fiery

Thank you for the feedback. We have a product cycle that dictates 5 or 6 stable releases per year. The next stable releases is currently scheduled to mid- or late May.

I'm sorry for the mixup. Here's a new AIDA64 Business Edition beta update: http://www.aida64.com/downloads/aida64businessbuild1907d3cjh4swzlzip

Thank you for the feedback

That issue has already been resolved in the latest AIDA64 release: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

What version of AIDA64 are you using? Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1906y8rltnhfczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1906y8rltnhfczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

1) Do you have AIDA64 running on your remote computer(s) and accepting incoming connections? 2) You need to use the /R option to create a report of your local computer. To create a report of one or more remote computers, you need to use the /RMTREPORT command-line option instead. Regards, Fiery

No problem

Please note that that only applies to pre-Fermi (pre-GTX480) cards. On Fermi and Kepler architecture cards (GeForce 400, 500, 600 Series) it is recommended to leave the nVIDIA GPU SMBus access through nVIDIA ForceWare option enabled, since it should guarantee that no collision occurs with other software reading GPU sensor information.

You can disable automatic updates in the Preferences / General, and manually check for updates in main menu / Help. Please note that the daily (or weekly, or monthly, whichever you configure) checking for updates only downloads a small amount of data. The "big chunk" of data only downloaded if you opt to perform the update. Regards, Fiery

EIST = Enhanced Intel SpeedStep Technology, so you have it disabled in the BIOS. What I meant to say above is that even though the BIOS doesn't populate the ACPI tables, it leaves the EIST bit enabled in the processor. For EIST to work properly, you need to have the EIST bit enabled in the processor, and also populate the necessary ACPI tables. Without the ACPI tables the operating system (Windows) cannot know how to switch between performance states. In your case the ACPI entries are missing (I guess), but the processor EIST bit is still enabled. It means the processor could switch between EIST states, but without operating system support it will not. So it still means the EIST feature is not utilized, even though the processors "thinks" it is enabled.

I'm not sure why the Event Log shows that info. But AIDA64 detects EIST state using the industry standard method, documented by Intel. It goes via CPU MSR (Model Specific Register) 1A0. I suppose your processor has that bit enabled for some reason, but the BIOS removed the EIST-related ACPI entries to effectively have EIST disabled under Windows. It's a small discrepancy in the BIOS. Of course in an ideal world the BIOS should also take care of disabling the EIST bit in MSR 1A0 Regards, Fiery

Please make sure to use the last, most recent license key we've provided. In case things might get mixed up even by doing so, please drop me a private message and we'll sort it out Thank you for your continuous support.

Thank you. We've started working on adding SAPI support. I'll drop a message into this topic once a new AIDA64 beta with SAPI details is available for download.

Yes, I'm afraid that could be a collision between GameGuard and AIDA64. Have you tried to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability? Please note that you need to restart AIDA64 after altering the Stability options, and you need AIDA64 v2.30 (latest version) to use that option. Do you experience similar issues when running other monitoring software like HWMonitor or GPU-Z? Thanks, Fiery

We haven't noticed any such issues on our own GTX680 card, although it's not made by EVGA, but is a Gigabyte GV-N680D5-2GD-B. We also haven't yet received any bug reports about GTX680 cards yet. I'm not sure whether this RSoD is related and limited to EVGA's own GTX680, or is it a ForceWare issue. We have been experiencing weird issues with ForceWare 296.xx drivers on some of our older GeForce test cards, so quite frankly, I wouldn't be surprised if the RSoD would be a ForceWare bug. Especially since AIDA64 reads almost every bit of GPU details and GPU sensor information via ForceWare driver calls on GTX480 and later GeForce video adapters... Please note that you can disable GPU sensor support in AIDA64 latest version (v2.30) in main menu / File / Preferences / Stability. That way you would of course lose GPU sensor readings, but maybe it would help to get rid of the weird RSoD issue, and you could still continue using the other sensor readings offered by AIDA64. BTW, do you have the option nVIDIA GPU SMBus access through nVIDIA ForceWare enabled on the same Stability page in the Preferences? Thanks, Fiery

On several ASRock motherboards there are more fan headers on the motherboard, controller and monitored, than the available sensor chip cooling fan registers. On such motherboards ASRock solved the issue by connecting two fans to a single fan register, using a fan mux switch. That effectively means a 3rd party application can read only one of the fans that are muxed on the fan register. On your particular motherboard there are 7 fans connected to 5 fan registers, hence two fan pairs are muxed. One of them apparently is Chassis Fan 1 which is muxed with Chassis Fan 2. In order to use AIDA64 without starting ASRock Extreme Tuner you will have to connect all fans to a non-muxed fan connector, or use the other member of the muxed pairs. I guess by moving your fan from Chassis Fan 1 connector to Chassis Fan 2 would fix this up in your case. BTW, the other muxed fan pair on your motherboard is CPU Fan 1 and CPU Fan 2, so you gotta be careful about using the fan there. The "safest" fan headers, the ones where you don't have to worry about muxing are Chassis Fan3, SB Fan1 and Power Fan. I hope this helps you to use AIDA64 to its full capabilities without relying on other software Regards, Fiery

It would require a separate hook module for DX9, DX10, DX11, OpenGL, etc. I'm afraid it's simply too much efforts for us this time.

A "key from a friend" usually means a pirate license key. A license that you purchase you wouldn't normally pass on to any friends You don't have to renew your license every year, since the usage period is unlimited. You will however be able to upgrade to new AIDA64 releases only until the maintenance period of your license expires. You can use the last version you are entitled to upgrade to for an unlimited time. The maintenance limit for the base license (which costs USD 39.95) is 12 months. You can purchase a longer, 2-year or 3-year license for USD 59.95 and USD 79.95 respectively. It is recommended to renew your license or purchase a longer maintenance license if you tend to change the hardware in your computer frequently. That way, if you can keep your AIDA64 installation fresh and up-to-date, you can assure it always supports your latest hardware components. Please note that a single AIDA64 license can be used on up to 3 computers by a single person. It means, if you have a desktop computer and a notebook as well, you can use AIDA64 on both computers with the same license key, and you don't have to purchase 2 licenses.

You have an illegal (pirate) license entered. Please consider purchasing a valid license from us, or remove AIDA64 from your computer. Only with a valid (legal) license you can use the fully automated internet update feature. Regards, Fiery

Your license key is written into the PKEY.TXT file. But, please note that at an update both your license and configuration settings (AIDA64.INI file) will be retained. Regards, Fiery

We don't use the Copy Debug Info to Clipboard feature that much. We prefer AIDA64 users to create separate ISA Sensor Dumps and/or SMBus Dumps, and those dumps are not localized. And actually, for us it's not that much of a problem to receive reports, report segments or page dumps in foreign languages. We'll add the requested new line to the language modules