Fiery

AIDA64 uses fairly regular Dell SMI calls to measure fan speed and temperature readings on Dell and newer Alienware systems. If you suspect AIDA64 may stop your system from utilizing its fan control logic properly, then please try to disable Dell SMI sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. If that solves the issue, then we will completely disable Dell SMI calls on Alienware M17xR4 systems. So please let us know how your tests go on the replacement system. Thanks, Fiery PS: I'm not sure if Dell SMI calls are the actual problem, since we've only activated them on M17xR4 at AIDA64 Beta Build 2105. So both AIDA64 v2.20.1800 and v2.30.1900 should have the Dell SMI calls not utilized on M17xR4, and so there should be no difference in their behavior...

Thanks Sensor readings will be fixed in the next AIDA64 beta release.

Thank you. I'm sorry to bug you more with dumps, but it seems this board has 2 different sensor chips, 1 more than what we've expected So please also submit a SMBus Dump (Full) dump.

Thank you. Please also copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic.

Please submit an ISA Sensor Dump Thanks!

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2232nwj7tfz9dlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

No. We only plan to make a full blown version in native 64-bit.

I'm afraid we haven't been contacted, and we haven't been able to find another source of ordering such an enclosure

We used to have plans for a native 64-bit main binary module for AIDA64, but due to many difficulties involving the 32-bit --> 64-bit change, Ansi --> Unicode change, and the compiler change (to Delphi XE3), we had to postpone its development due to development resources constraints. We need to focus more on improving the existing features and existing benchmark methods of AIDA64 before we can make the big step of moving to a 64-bit main binary. I'm afraid I cannot provide you with a release date for that, since it may be well in the future (2014? 2015?)

Thank you. I'm afraid we haven't been able to figure out the cause of the sluggishness on your system so far If it's possible, please try to disable the HWMon Modules one-by-one, and let me know which module you reckon could be behind the slowness. You can disable HWMon Modules in the right-click menu on the bottom status bar of AIDA64 main window.

Thank you for the feedback

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.