Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. I've sent you your product key in private message.
  2. Quite frankly, we don't think it would worth the hassle, simply because it's much better to use a background image that you can assign for any page. And if you want a plain, solid color background image, then you can make one using MS Paint for example, in 2 minutes
  3. If you enable Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability (and then restart AIDA64), it should work with AI Suite. Regards, Fiery
  4. Thank you for the feedback. Yes, just copy over, let it replace any existing files. But first, close AIDA64
  5. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results here. Thanks, Fiery
  6. We've tried to find the issue, but so far with no luck We would have to narrow it down to a specific part of the code to find the culprit. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Let me know if it triggers a BSoD or falls into and endless loop. Please also check if you experience any issues while viewing the following AIDA64 pages: - Commputer / Sensor - Motherboard / CPU - Motherboard / CPUID - Motherboard / SPD - Motherboard / Chipset
  7. The log file is not re-created at each update, but only appended. That's why its header cannot be updated at each update. The stat file in contrast is re-created at each update, hence its header can be updated.
  8. Does it hang on the Overclock page after it displayed "CPU Properties" line, so only that line is displayed on the Overclock page? Or is there any other lines displayed below that line before the hang happens, like "CPU Type" or "CPU Alias" ? Thanks, Fiery
  9. Thank you for the dumps. We've tried to reproduce the issue on our nVIDIA GeForce based test systems, but without luck so far. We'll try to get a mobile GeForce system, in a hope that it would produce the same errors. Meanwhile, please try to update to the latest AIDA64 beta and the latest ForceWare release, maybe the issue will fix itself meanwhile http://www.aida64.com/downloads/aida64extremebuild3114t0h8kqnryfzip I'll let you know in this topic once we have more information on this issue.
  10. Yes, the stat file now shows the log start and log finish time stamps. We've already rolled out the patched AIDA64 beta: http://www.aida64.com/downloads/aida64extremebuild3114t0h8kqnryfzip The lifetime of both log files are controlled by the option you've mentioned. In case you enable the date and time columns, and you use the above linked new beta, then you'll have all information in the log files to let you understand the logging time range covered by the log files.
  11. That's normal. That list shows the video adapters as Windows manages them. Windows installs a Windows video adapter for every video outputs your video card has got. So e.g. if you've got a DSub, a DVI and a HDMI output for your Intel iGPU, Windows will install 3 video adapters. Regards, Fiery
  12. We've checked, and it's not quite possible to import a specific data from a XML file into AIDA64. It's because with XML it's not possible to reference a specific data value, like you would reference e.g. a file on your disk drive, or a specific web page using a URL. With INI files and TXT files it would be easy though... In case you've got an exact idea on how to reference the data from your XML file in AIDA64, please let us know how do you imagine it, and also show us a sample XML file (or a part of it).
  13. We've just rolled out a new AIDA64 beta that supports BWCT, Crystalfontz and POS VFD displays: http://forums.aida64.com/topic/2433-new-lcd-device-support-crystalfontz/
  14. We've added support for POS VFD devices (customer displays, pole displays, table displays), utilizing the ADM787/788, Aedex, CD5220, DSP800, Epson ESC/POS, ICD2002, Logic Controls, UTC Standard or UTC Enhanced protocols. Only 20x2 character devices are supported at this time. You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is the display to be connected to a RS232 (serial) port. USB-connected displays are also supported, as long as they use a virtual COM port. COM port properties need to be configured in the Device Manager. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Trefon, BWCT, Crystalfontz, and LCDInfo LCD devices are also supported now by the latest AIDA64 beta. Regards, Fiery
  15. We've added support for Crystalfontz USB-connected CFA-533, CFA-63x, CFA-735, CFA-835, XES-635 LCDs, as listed at: Crystalfontz High Level Character Displays Crystalfontz High Level Graphic Displays You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the LCD drivers (FTDI or VCP) installed, and the display to be connected to a USB port. You can verify if your device is compatible with AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 0403-FC08 0403-FC09 0403-FC0B 0403-FC0C 0403-FC0D 0403-FC0E 223B-0004 223B-0005 It is recommended to use the latest firmware for your display. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Trefon, BWCT, LCDInfo, and POS VFD (customer display, pole display, table display) devices are also supported now by the latest AIDA64 beta. Regards, Fiery
  16. We've fixed the issue in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3114t0h8kqnryfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works
  17. We've fixed the issue in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3114t0h8kqnryfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works
  18. Please note that we've just implemented support for USB-connected Crystalfontz CFA-533, CFA-63x and CFA-735 and CFA-835 LCDs: http://forums.aida64.com/topic/2433-new-lcd-device-support-crystalfontz/
  19. On Razer SwitchBlade UI capable devices we'll extend the 4 pages to 9 pages in one of the upcoming beta releases of AIDA64. As soon as it is implemented, I'll post a message into this topic
  20. Since that September post, we've implemented an option in AIDA64 / main menu / File / Preferences / Stability called Wake GPUs up at startup. It can be used to make the GPU (or GPUs) wake up at AIDA64 startup, and so get around the pecularities of nVIDIA Optimus technology.
  21. 1) You need to enable the first 2 logging items (labelled as "Date" and "Time") to have a date+time stamp in the chart. Not all AIDA64 users need such columns in their logs, that's why they are not there all the time. 2) You can adjust the log file update frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. 3) Whenever you make a change about logging settings in the Preferences, AIDA64 will start a new pair of log files. That's because things would get mixed up if you add or remove a column in the logs "on the fly". Once you're settled with your settings, just remove the partial, old log files, and keep just the latest one. 4) You're right, the statistical log file misses the logging start and logging finish time stamps. We'll add them in the next AIDA64 beta release due in a few days from now. Thanks, Fiery
  22. You can check the installed memory module properties on the Motherboard / SPD page. You can check the motherboard DIMM slot information on the Motherboard / Motherboard page. If you've got difficulties finding the information, then just copy-paste the content of those pages into this topic, and I'll provide you with the information you're looking for. Please note that we've never seen a single motherboard or system that could have 204 and 240 pin DIMMs mixed. Regards, Fiery
  23. We use their developer forums: http://developer.razerzone.com/ I'm not sure how appropriate would be to post your user/customer requests there though...
  24. The current Corsair Link solution sadly doesn't support proper data sharing between 3rd party applications and the Corsair Link software. Corsair wants to roll out a completely revamped new Corsair Link software stack this year, and they promised that one will be much more advanced, with proper data sharing capabilities. As soon as the new software is ready, we'll start working on it for AIDA64.
×
×
  • Create New...