Jump to content

Fiery

Administrators
  • Posts

    11200
  • Joined

  • Last visited

  • Days Won

    475

Everything posted by Fiery

  1. Other tools include AIDA64, of course But that feature generally requires a platform that supports such readout, and AFAIK LGA1366 platforms do not support that due to lack of hardware implementation in ICH10 south bridge.
  2. Please try to enable the option "Use HKLM in Registry" in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar. Let me know if it helps. Thanks, Fiery
  3. Thank you for the clarification, now I understand the problem you're facing. We'll do some test runs to reproduce the issue, and I hope I'll be able to get back to you (in this topic) with a solution next week. Thanks, Fiery
  4. 1) AIDA64 has the gadget in its distribution package. It is the file named AIDA_VSB.VSB. As soon as you enable the Sidebar feature in AIDA64 (main menu / File / Preferences / Hardware Monitoring / Vista Sidebar), then the gadget files are copied to the relevant Sidebar folder on your computer. After that, all you have to do is manually add the gadget to your Sidebar or Desktop. 2.1) It is a limitation that no Windows software can get around. You simply need to have admin rights to communicate with sensor devices. 2.3) Have you tried to run AIDA64 by right-clicking on the AIDA64.EXE file (or the AIDA64 shortcut on your Desktop) --> Run as administrator? Regards, Fiery
  5. We're still changing icons, so Build 1123 was only a mid-term preview The motherboard icon is not an old one, and it's not related to the previous WinXP-style looks, so we kept it. We may change it soon though, to make sure that icon also features a "fresh" look.
  6. Please let us know more abuot your system: 1) Windows variant? 32-bit or 64-bit kernel? 2) Intel storage drivers version? 3) Disk drives configuration? Any RAID arrays defined? 4) AIDA64 version and build number? Thanks, Fiery
  7. We've managed to fix this issue. It will be included in the next stable release of AIDA64. Thanks, Fiery
  8. Can you please check if HWMonitor is also affected by this anomaly?
  9. Thank you for the suggestion. We'll consider this in the a future release of AIDA64.
  10. Unfortunately most controllers don't feature a working temperature sensor, so it's not just Crucial's controller
  11. It's a false alarm. We've already got feedbacks from a couple of users about the same issue, and they already reported the false alarm to Comodo. Let's hope Comodo will soon fix their software. Regards, Fiery
  12. The reference benchmark results listed on the benchmark pages are there for a reference. They are measured and collected by us (FinalWire), and they represent 100% reliable, valid, accurate results. We may come up with an online database with validator in the future, but our short-term plans focus on other improvements (automatic internet update, OpenCL-based GPGPU benchmarks + GPGPU stress test, etc). Thanks, Fiery
  13. Thank you Only 2 more days left of the $20 discount period
  14. Thank you all for the feedback, I'm glad you like it. It took us 4 days to implement the new icons set, but it indeed looks nice
  15. Quite frankly, we have very limited programming information on Marvell SSD controllers. But based on our test runs, Marvell controllers do not seem to support temperature sensing
  16. I hope you all like it If not, you can revert back to XP icons (AIDA64 / main menu / Preferences / General / Icons style). We'll soon revamp the tool bar icons as well.
  17. 1) No data is written during read tests. 2) The data written during write tests were garbage. We've changed that in the latest beta version of AIDA64 Extreme Edition (link below) so that from now on the written data will be absolutely random (non-compressable). We've also added a warning for the Buffered Write test about SSD drives. http://www.aida64.com/downloads/aida64extremebuild1123r4ivje6xphzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery
  18. We've implemented Windows 7 style icons. Please note that we're not finished with this, so this is just a sneak peek of how it will look like in the next stable release of AIDA64. We'll continue revamping the graphics elements of the user interface to make it look more consistent. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1123r4ivje6xphzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. You can switch between Windows 2000 looks, Windows XP looks and Windows 7 looks in AIDA64 / main menu / Preferences / General / Icons style. Thanks, Fiery
  19. Thank you for the tip. We've enhanced the RAID member enumeration and implemented SMART information readout for Intel ICH/PCH RAID controllers. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1123r4ivje6xphzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. --- Please note that Intel's Rapid RAID drivers feature a bug about the ATA passthrough interface. SMART thresholds readout returns the same data than SMART attribute values readout. Hence the thresholds column shown in Intel SSD ToolBox shows garbage (invalid) data. We've implemented a trick to detect that driver bug and ignore the thresholds data when it is invalid. We've notified Intel about this driver bug, and as soon as they fix it, AIDA64 will start showing valid thresholds data. Thanks, Fiery
  20. NoBS: Thank you! 3rik: The lack of further beta releases now is due to the fact that we're bringing major changes with the next beta We need some more time to further test the new features, but we're hoping to release the next beta in 2-3 days from now. Just a hint about the new features: http://forums.aida64.com/index.php?showtopic=31
  21. Thank you for performing that experiment. Quite frankly, I think it could be normal, and it may come from the fact that AIDA64 uses 2 different threads to measure sensor values (temperatures, voltages, fan speeds). One thread is used exclusively by the Sensor page, and the other one is shared by all the Hardware Monitoring features (Sensor Icons, OSD, Sidebar Gadget, Logitech LCD, External Applications, Logging, Alerting). The two threads usually measure the same when they're running side-by-side (e.g. when you have OSD and also Sensor page opened); however, the Intel DTS core diodes are very sensitive to CPU load, so some variance on the thread that is used by AIDA64 to measure sensor values can occur. When I write "side-by-side", of course I don't mean the 2 sensor threads would measure values at the same time. The two threads are executed one after each other, otherwise their low-level code would collide with each other. When e.g. the thread of the Sensor page is executed first, and it puts a load (utilization) on the CPU core it runs at, the second thread going after that (the Hardware Monitoring thread) may just start from a hotter state of the CPU core, and so it could measure a hotter CPU core temperature than expected. Then, until the next update the CPU core cools down a bit, hence the next thread (Sensor) starts from a cooler state again, hots the core up again, and the next thread (Hardware Monitoring) starts from a hotter state again, etc. etc. Such anomaly could be confusing, I admit, but I believe it's not a program bug, but more like an architectural short-coming of AIDA64 that we could only eliminate by joining the two separate sensor threads, to make sure once a value is measured, the same value is displayed everywhere in AIDA64. We'll work on it. Thanks, Fiery
  22. Thank you for your support We plan to release a new AIDA64 beta every week, so at least 52 beta releases per year. We also plan to publish at least 5 or 6 new stable updates per year.
  23. 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
  24. 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: http://www.aida64.com/news/finalwire-unveils-aida64 And also on the "what's new" page: http://www.aida64.com/whatsnew/aida64-here 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.
×
×
  • Create New...