Fiery

Here's the previously mentioned new AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild2232nwj7tfz9dlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

We've got the SDK, and ordered a DeathStalker Ultimate keyboard from the local Razer distributor. They said delivery is only expected early next year, so please expect the actual development of this feature to commence only in Q1 2013. I'll let you know in this topic how things develop around this feature request.

What version of G15 drivers do you have installed? What sort of Windows operating system do you have installed? (Win7 64-bit maybe?)

AIDA64 uses the SiUSBXp.dll module of Asetek water cooler drivers to access sensor readings for the liquid cooling device. It's a fairly simple communication protocol, but it has a drawback: we have no control over the actual data readout. In other words, this is not a low-level interface that provides direct access to hardware registers, but a simple high-level interface of "tell me the temperature and fan speed" -- and that's it. Therefore, we cannot fix such reading issues from our software If the mentioned Asetek module intermittently fails to read the values, we cannot fix that from AIDA64 I'm afraid. Another explanation of that issue may be a background process or driver that also polls the Asetek LC sensors, and that polling sometimes collides with AIDA64. Do you have any other monitoring software running in the background? Regards, Fiery

It's not entirely helpful, since as far as I can see, there's no direct download for the SDK. But now we've registered into RazerZone forums in a hope that there's someone there who can help us. We've also sent another email to Razer to request permission to access the SDK. Let's hope one of those channels would lead to results this time.

Thank you. It was due to a typo in the EDID block of your monitor. It will be fixed in the next AIDA64 beta release. Regards, Fiery

It's clear now, thank you. We'll fix that in the next AIDA64 beta release.

We've cheched the drive utilization, and it shows the percentage of used space as expected. Can you please check it again? We'll think about the MegaBytes issue, and try to come up with something that is "best of both worlds" (where both = MB and GB).

Thank you, fingers crossed here

We've implemented the new hardware monitoring items to let you monitor drive space status. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2227fh3yxq0knmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've implemented a new option on the Preferences / Hardware Monitoring / Logging page to let you adjust the frequency of new log file opening. Previosuly it was 24 hours fixed, now it is 24 hours by default, but you can lower it to 1 hour if you wish. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2227fh3yxq0knmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Razer products don't seem to feature an open SDK like G15/G19, so I'm not sure what can we do to make AIDA64 work with it. If you could convince Razer to help us about it, then we'd be happy to implement support for DeathStalker. BTW, about a year ago we've contacted Razer about implementing support for the multi-touch LCD screen of Blade gaming laptop in AIDA64, but we haven't received any meaningful answer from Razer. So based on that, we have to assume they prefer to deal with game software developers...

We've checked OpenGL ES 1.0, 1.1, 2.0 and 3.0 spec, and quite frankly, it's not obvious to us which exact extensions are required by each OpenGL ES release. We've collected the following requirements for OpenGL ES 1.0 and 1.1, but couldn't find the relevant list for 2.0 and 3.0. Maybe you can help us about that? * OES 1.0 * GL_OES_byte_coordinates GL_OES_compressed_paletted_texture GL_OES_fixed_point GL_OES_read_format GL_OES_single_precision * OES 1.1 * GL_OES_matrix_get GL_OES_point_size_array GL_OES_point_sprite

Please try to issue an ISA Sensor Dump, and let us know if it makes AIDA64 freeze. If it doesn't, then please issue a SMBus Dump (Full) dump, to see if it causes a freeze.

What version of AIDA64 are you using? What motherboard and video card(s) do you have? Thanks, Fiery

Try to rename AIDA64.* files to Everest.* Maybe AlphaLCD is looking for a process called Everest.exe?

Thank you. Please try to disable Toshiba TVALZ sensor support in AIDA64 / main menu / File / Preferences / Stability. Let me know if it makes any difference.

AIDA64 Yes, it does. Yes, you can. There's no deactivation procedure. You can just remove it from the "old" computer, and install it on the "new" computer. Please note that a lot of computer enthusiasts (overclockers, gamers, guys and gals assemblying systems for themselves and their friends & relatives, etc) use AIDA64 due to its easy installation, upgrading and portability. We've designed the licensing scheme to make it easier for them to move AIDA64 from one configuration to another. We do have quite a few customers who literally swap their system once a month -- or change/upgrade a hardware component every week. For them it's essential to be able to drop an AIDA64 installation when a computer moves out, and install it on their new or updated computer once it's in. Thank you for your support Regards, Fiery

It is modular already of course, but the more modules and more items we put in, the slower it gets afterall. The performance hit is not huge, but we're trying to minimize the number of items to make sure it stays swift. In the next AIDA64 beta we'll try to come up with a solution that would be suitable for most users. BTW, dynamic measurement units are not supported by AIDA64, so that's not an option I'm afraid.

We've checked it, but so far we couldn't find the necessary Windows API call that could be used to detect the location setting. We'll keep looking

That's not really an option, since we want to avoid inflating the number of hardware monitoring items. The more items we define, the slower the whole monitoring module will get...

The dates in the report header and Summary page are intentionally left at a fixed format, to enable post-processing the report files. So regardless of the regional settings, you can always identify the report creation date. Regards, Fiery

Quite frankly, we are not in a position to be able to put all pieces of the puzzle together about the dark secrets of AMD memory controllers What I can tell you for sure is that: 1) DMI info is never 100% reliable, so it shouldn't be considered at all as a verification of memory controller working modes 2) You processor is definitely Revision C 3) Since you are familiar with AMD BKDG's, here's how AIDA64 detects ECC and ChipKill ECC modes: IsECCSupported:=reg_F3xE8 Shr 3 And 1<>0; IsChipKillECCSupported:=reg_F3xE8 Shr 4 And 1<>0; IsECCEnabled:=(regF2x[1,0]90 Shr 19 And 1<>0) And (reg_F3x44 Shr 22 And 1<>0); IsChipKillECCEnabled:=IsECCEnabled And (reg_F3x44 Shr 23 And 1<>0); Based on that, and the PCI registers output at the end of AIDA64 reports, I hope you can put the pieces together

Can you please tell us more about this system? Motherboard model, CPU type, any external disk drives connected? Is it running Win7 64-bit?

Yes, definitely. Although data representation is not as straightforward as you might imagine What sort of monitoring item would you prefer? 1) Free space amount in MegaBytes -- may be a huge number for a 2+ TB partition... 2) Free space amount in GigaBytes -- may be marginally useless for small partitions (or for small capacity flash drives) 3) Free space percentage of total partition space