Fiery

1) Do you experience the same lockup on other systems as well, or it only happens on this particular notebook? 2) Does the lockup happen when you go to the following AIDA64 pages in the left page menu? - Computer / Summary - Computer / Sensor - Motherboard / CPU - Motherboard / SPD - Motherboard / Chipset - Display / GPU Please let us know which page(s) cause a similar lockup. We need to narrow it down to a specific module of AIDA64, so we can start investigating from there. Thanks, Fiery

Thank you for you comments Quite frankly, we didn't implement Windows 7 icons, because in most cases AIDA64 displays icons in their 16x16 pixel version, and in 16x16 most Windows 7 icons look a bit pale (all gray and blue) and too similar to each other. We find Windows 2000 and Windows XP icons easier to identify, and more colorful, especially in 16x16 version. We wanted to wait until someone asks for Win7 icons, but now that you have, we may give this another thought As an optional feature it may work out well. I'll let you know in this topic when we implemented this feature. Regards, Fiery

Thank you. I can see three 1.5TB WD drives, and three 2TB WD drives there. Can you please clarify what drives do you have in your system, and how are they organized into RAID array(s), and if there're separate, individual drives as well?

AIDA64 is named that way, because the performance-oriented modules (the benchmarks and the System Stability Test) are ported to native 64-bit (x86-64), and it also has a 64-bit kernel driver to perform low-level hardware access. AIDA64 benefits from 64-bit x86 extensions where the difference between 64-bit and 32-bit really matters. The main module, the application itself (AIDA64.EXE) is still 32-bit, but since the beauty of x86-64 capable processors is that they provide virtually no performance hit from running 32-bit applications under 64-bit operating systems, this is not really an issue or drawback. This way, compatibility with legacy (32-bit only) processors and legacy (32-bit) Windows installations is fully retained. Regards, Fiery

It is still fully supported. You need to enable the Sidebar support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar. Then you need to add the AIDA64 Gadget to your Sidebar (Vista) or Desktop (Win7) manually. Regards, Fiery

Thanks. Please start AIDA64, right-click on the bottom status bar of its main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Maybe we already have a RAID member enumeration method that can be used for this controller as well Thanks, Fiery

Thanks! That looks identical to our TMS-200 test device. Have you tried closing the TMS application? Unfortunately the hardware implementation of TMS-200 doesn't provide a way for 2 (or more) applications to access the TMS-200 device simultaneously

Thank you And in the future please feel free to use this forum (or our Support Ticket System) to submit your questions or potential bug reports to us.

An upgrade license will be at least 25-30% cheaper than a new (full) license. BTW, I think I saw your email in our support system as well, so please check our reply in your mail box, because we've sent you a more comprehensive reply to all your questions you've submitted to us.

Do you mean a dedicated PCI Express connector MegaRAID SAS RAID controller card like this? http://www.legitreviews.com/article/1178/1/ Or you mean that RAID controller chip integrated on a motherboard? BTW, the Areca controller you mentioned should be already supported Thanks, Fiery

I'm glad to hear it is fixed now, because AIDA64 does indeed feature a Sidebar gadget that should work just as great as EVEREST's old Sidebar solution

Thank you for the feedback!

I'm not sure which page of our website do you mean, but if you meant the following statement ... http://www.aida64.com/free-upgrade-aida64 ... then I think you may have misunderstood it. If you request a free upgrade to AIDA64 now, and you're eligible according to the Terms and conditions, then you will receive a free AIDA64 license that can be used for AIDA64 v1.00 for 12 months. After that period, if you want to continue using AIDA64, or when you want to use a more recent version than AIDA64 v1.00, then you will need to purchase a full license. Not an upgrade license. Regards, Fiery

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

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

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Devices Dump. Copy-paste the full results into this topic. Based on that data we'll check why AIDA64 cannot pick up your TMS-200 device. Maybe you use a newer or older revision of TMS-200 than what we have in our labs. Thanks, Fiery

Thank you for the bug report. We've already fixed this issue. We'll release a new beta version of AIDA64 in a couple of hours, so please watch our Downloads page for the new beta chart to appear: http://www.aida64.com/downloads But we'll also post the link to the new beta package here, into your topic. Thanks, Fiery

AIDA64 supports the same hardware monitoring Sidebar/Desktop Gadget and OSD Panel features that EVEREST did. We do have plans about a completely new gadget/panel with fully customizable items placing, advanced visual appearance, and enhanced features. It will be implemented in an upcoming new release of AIDA64, perhaps v2.00 or v3.00

Thanks for the feedback

Thank you! I've checked in our system, and it seems you should have already received the free AIDA64 upgrade license

We've done a fair bit of testing, with positive results. However, in AIDA64 we've implemented more options on the main menu / File / Preferences / Stability page, so if things go wrong, you have a lot of options now to assure your system stability is not compromised by using the low-level monitoring features. We've also changed the way the Preferences opens, so now it doesn't scan all possible sensors right when you open it, but only when you click on a page where scanning is needed (e.g. Sensor Icons, OSD Items, etc). Hence now it's much easier to test out various Stability options when it's necessary. In the case ULPS still causes a headache, then the best solution we've come up with is disabling multi-GPU support (main menu / File / Preferences / Stability). That way you lose the readings for the secondary GPU, but for the primary GPU all data will still be available. Regards, Fiery

We may implement a 3D game support for the OSD, but only next year. It's not easy, since we gotta implement different hook modules for Direct3D 9, D3D 10/11, OpenGL, Vista/Win7, etc. Our short term plan is not boosting the OSD, but to develop a completely different, new feature that would offer a fully customizable placing, a bit like how you can place an item on any (X,Y) position on a Logitech G15/G19 LCD screen with AIDA64. Also, visually more appealing item variants (not just simple text), like customizable bar gauges that would indicate the status of a reading with different colour. Green = temperature is cool, yellow = it gets warm, red = it's hot. Maybe even flashing an item when it gets over a limit (e.g. voltage or temperature), or under a limit (e.g. a fan RPM or voltage). And of course, placing of one or more custom BMP images anywhere on the panel, so users can put their video card logo, CPU logo, or any other elements onto the panel. The custom skins and other visual tricks may come only as a second step, we prefer not to "bite" too much at first I'll of course let you know here as soon as we have something to try out

Thank you for the bug report. We've got the same feedback from 2 other users, but they also added that the error message only comes up at the very first start of AIDA64. Any further starts go fine, so we suspect it could be related to the engine behind the self-installing EXE package (InnoSetup). We'll investigate it, and hopefully can fix the error soon. Thanks, Fiery

Thank you

Wishbringer: I of course understand what you mean, but what we provide is a chance to switch from EVEREST to a more advanced product named AIDA64. True, the free AIDA64 license is not for 2 or 3 years, but only for 1 year. We do believe as a free gesture, it's not that bad We are not Lavalys, but we are a different company named FinalWire. In the case you are worried about the support period you purchased from Lavalys, you have to contact Lavalys' Sales Department for clarification on ongoing software updates and technical support. What seems to be obvious is that there has been no EVEREST software update for 4 weeks already, and that the very popular Lavalys Discussion Forum, where most of the EVEREST technical support was done has been disappeared. We are FinalWire, and we provide support for our own product AIDA64. EVEREST is a product distributed, sold and supported by Lavalys Consulting Group, Inc.