Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Fiery

  1. We have (long-term) plans about a native 64-bit application, but it wouldn't be an AIDA64 update, but more like a brand new, separate software product.

    As for the installation question: it wouldn't offer any advantage to install AIDA64 individually under each operating system, unless you consider the individual configuration an advantage. Since if you run it from a central location, you cannot configure it differently for e.g. XP SP3 than for Win7. If you install one AIDA64 copy for each OS, you can have different settings configured in AIDA64 Preferences for all OS.

    BTW, in our test labs we don't install AIDA64 on each test system, but we run it straight from the network, from a central shader folder (using UNC path). AIDA64 is the most flexible and most portable diagnostic software in its class :huh:

  2. Since this is a brand new product, we don't publish all small details we introduced in AIDA64. The major improvements are well documented in our press release:


    And also on the "what's new" page:


    Besides them, we've spent endless hours optimizing the sensor code, e.g. making AMD Radeon HD 5xxx support a lot faster. We've also made the PCI scanning module faster, to make the application start-up considerably quicker than before, especially on Core i3/i5/i7 systems. The Preferences changed a bit too, but the small touches here and there mostly serve optimization purposes, and involve no major functionality changes.

  3. Thanks. Maybe a long shot, but can you please try the following:

    1) Disable Turbo Boost (you can do it in AIDA64 / CPU Tweakings, I'm sure you know where to find that :huh: ), and check if it makes any difference.

    2) If #1 doesn't make a difference, then please try to run AIDA64, and manually adjust the CPU affinity (using Task Manager), and so lock AIDA64 to the 2nd logical processor, then the 3rd logical processor. Please let us know if it makes any difference.



  4. I fully expect to purchase the new version license when it is available but I'm curious about something.

    This free license expires after one year which I assume means it will either stop working or have nag screens like a trial version.

    It will stop working one year after the free license was created.

    But once we upgrade to the new version with a normal license then the license agreement as posted on the license page takes over. It is useable forever but service and support only lasts for one year.

    Do I have that right?

    Yes, you do. A full purchased license of AIDA64 can be used perpetually. It will not expire at all. The only thing that will expire is the support & updates (maintenance) period, but you will only notice that if you try to upgrade to a new AIDA64 version that your license doesn't permit. If you don't upgrade to a newer version after the maintenance period is expired, AIDA64 will keep working with its full functionality.

  5. Generally speaking, write benchmark tests shall not be used on SSD drives, unless the measurements are done for specific purposes like it is for a hardware review article, or there's a suspicion about hardware malfunctioning.

    Linear Write fills the whole disk space once, so unless it is performed in loop mode, it's nothing critical for a SSD, since it only writes every flash memory block just once. The Buffered Write test however constantly writes the beginning first few sectors of the SSD "surface", so it shall not be used on flash memory based devices at all, unless it's absolutely necessary.

    Random Write and Average Write Access tests write random sectors on the SSD "surface", so they are not much harmful, unless of course you use them a lot, or if you use loop mode and let it go "all night long" :huh:

    We'll add a special warning for the Buffered Write test, specifically about SSD drives, so it would strongly advise against using that particular test on SSD drives.



  6. Yes, our beta releases are just as stable and high quality as our stable releases. Of course, from time to time slight issues may slip in a beta, but they usually only affect a single piece of hardware or a very small group of users.



  7. Sorry I meant is it a correct reading or just a bogus value?

    The only way to verify if it is a correct value is by checking it a couple of times a day. If it always shows the same degrees Celsius value, then it is stuck and so it doesn't report a valid value. At least 1-2 Celsius variation should be shown.

  8. Thank you for the dump. I'm sorry, but I cannot see any DIMM TS (Thermal Sensor) capable memory modules in your system. Are you sure your memory modules implement a thermal sensor chip? If yes, then do you have any software that is capable of measuring temperatures of your memory modules?



  9. We cannot publish all information in details at this early stage. Currently, our release schedule puts AIDA64 v2.00 later this year, probably in early December, with a brand new hardware monitoring visual panel implemented, sort of an "OSD on steroids". AIDA64 v3.00 will only come in 2011, probably in Q2 (April or May). We plan to implement e.g. OpenCL benchmarks and OpenCL System Stability Test in 2011, most likely by v3.00 release.

    Between those cornerstone releases, we will release at least 2 or 3 stable updates, where we implement support for the latest hardware components (video cards, motherboards, processors, SSD drives, etc) released between the major updates.

    We are also in the process of implementing Intel AVX support in our memory and FPU benchmarks, to optimize them for the upcoming Intel "Sandy Bridge" processor. However, the unveiling of the AVX-optimized benchmarks depends on Intel's release schedule of their new processors based on the "Sandy Bridge" core.

  10. Obtaining the 32x32 icons is not a problem, but as you can see, AIDA64 uses 16x16 icons e.g. in the page menu on the left of its user interface, and also in MHTML reports and on most information pages as well. But since we'll implement Win7 icons as an option, if someone doesn't like how they look, he can revert back to WinXP-style icons.

  11. Currently AIDA64 supports the following DIMM TS manufacturer IDs:







    In case you have a memory module that is not supported yet, then please start AIDA64, right-click on the bottom status bar of its main window --> Sensor Debug --> SMBus Dump (Full). And copy-paste the full results into this topic.

    Based on that output we can add new DIMM TS manufacturers to AIDA64.



  12. As our Terms and conditions state at ...


    ... we provide an AIDA64 license free of charge with a 12 months expiry. So the AIDA64 license you got today can be used until October 10, 2011. However, the license can be used only for AIDA64 v1.00. If in the future you find e.g. AIDA64 v2.00 or AIDA64 v3.00 appealing, and you will wish to upgrade to it, then you will need to buy a full new AIDA64 license to upgrade from AIDA64 v1.00 to a new version of it.

    We don't clone the EVEREST license, and we don't provide an AIDA64 license with the same limitations. We only provide a chance now to switch to AIDA64 free of charge, because AIDA64 is the future, and we want to give EVEREST customers a chance to benefit from the new features of AIDA64. This is not a "one-way street", you can switch back to EVEREST if you want, since your purchased EVEREST license is retained even after acquiring a free AIDA64 license.

    I hope this clarifies it :(



  13. 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.



  14. Thank you for you comments :D 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.



  15. 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.



  16. 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 :(



  • Create New...