-
Posts
12427 -
Joined
-
Last visited
-
Days Won
553
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
New LCD device support: Samsung SPF Digital Photo Frames
Fiery replied to Fiery's topic in Hardware monitoring
Don't worry, we'll sort it out Most likely the issue is caused by the collision between Samsung Frame Manager's main hardware polling process called sam_controller.exe and AIDA64. Please try the following: 1) Start Registry Editor (REGEDIT.EXE), and navigate to: HKEY_LOCAL_MACHINE\Software\Samsung\FrameManager 2) Check what value does the DeviceInfo field hold. If it's "00 00", then please switch the device to Mini Monitor Mode, and check it again. 3) Also check what USB device ID does your SPF-87H have assigned, on the Devices / USB Devices page. The device could be in either mode for that. I'm just wondering that because there are 3 different variants of SPF-87H out there, and it would be great to know which one have you got. 4) Try to kill the process called sam_controller.exe using Task Manager. That should take care of the collision between AIDA64 and Samsung Frame Manager, and let you use the DPF via AIDA64. If you don't want to use the Mini Monitor feature of your DPF for its intended purpose, then you may as well uninstall Samsung Frame Manager completely. It will leave the Mini Monitor USB device driver installed, so you will still be able to use AIDA64 with your DPF. 5) I'll send you something further in private message, but please only deal with that after the above 4 steps BTW, if nothing works out (which is unlikely), we already have a "Plan B" for Samsung SPF devices, so you will either way be able to use your SPF-87H with AIDA64. Thanks, Fiery -
What output is logging supposed to produce, and how often?
Fiery replied to DSperber's topic in General Discussion
It will be sorted out in the next AIDA64 beta release due in 1 or 2 days from now I'll post a download link here once the new beta is available. -
Thank you for the feedback, I'm glad you've managed to sort it out.
-
No, we're not planning to enable that. It would make configuration too complex and hard to follow for many.
-
T-Balancer bigNG supports 12 temperature inputs, and AIDA64 implements native support for it.
-
I've sent you your product key in private message.
-
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
-
Have the problems with Asus AI Suite been fixed?
Fiery replied to M.A.D.'s topic in Hardware monitoring
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 -
Access violations while monitoring with Logitech LCD
Fiery replied to DukeSan27's topic in Bug reports
Thank you for the feedback. Yes, just copy over, let it replace any existing files. But first, close AIDA64 -
2133MHz DDR3 showing as 1280MHz on o/c'd i7-4930K
Fiery replied to bwh's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results here. Thanks, Fiery -
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
-
What output is logging supposed to produce, and how often?
Fiery replied to DSperber's topic in General Discussion
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. -
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
-
Access violations while monitoring with Logitech LCD
Fiery replied to DukeSan27's topic in Bug reports
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. -
What output is logging supposed to produce, and how often?
Fiery replied to DSperber's topic in General Discussion
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. -
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
-
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).
-
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/
-
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
-
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
-
AIDA64 System Stability Test stops working after a few seconds
Fiery replied to eldrin's topic in Bug reports
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 -
AIDA64 System Stability Test stops working after a few seconds
Fiery replied to Tony Morton's topic in Bug reports
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 -
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/
-
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
-
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.
