Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. We can only add that in case the BIOS Setup or Gigabyte's own software also shows the reading as PCH temperature. Otherwise it's just pure guessing
  2. It should be there But it's written there only when you close AIDA64 or it automatically opens a new log file.
  3. We've added support for all Trefon USB LCD and GLCD products, as listed at: Trefon USB-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 (libusb0) 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: FFF0-FFFD FFF0-FFFE It is recommended to use the latest firmware (Version 2.1) 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, Crystalfontz LCD, LCDInfo LCD and POS VFD (customer display, pole display, table display) devices are also supported now by the latest AIDA64 beta. Regards, Fiery
  4. We've just updated AIDA64 to include support for Samsung 800P, 800W, 1000P and 1000W DPF displays as well: http://www.aida64.com/downloads/latesta64xebeta This version also supports both Samsung's original SODI drivers and generic libusb0 drivers.
  5. We've implemented support for the new generation graphical Crystalfontz CFA-835 display in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta
  6. We've fixed the clipboard locale (character set) issues in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
  7. We've further tweaked the log files header/footer, as requested. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip Let me know how it works
  8. We've fixed the sensor readings in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip As for the PCH temperature, I'm not sure how HWiNFO64 reads it. Can you please post a screen shot that shows all HWiNFO64 readings and all AIDA64 readings side-by-side? As for the BIOS date, the emulated classic system BIOS apparently contains a wrong system BIOS date stamp. It's due to a BIOS bug, and not an AIDA64 issue.
  9. We've implemented the requested drag&drop LCD page reordering trick in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip Let me know how it works. Please note that at the time you perform the reordering, the page captions will be reordered as well, to indicate that you've performed a reordering. So e.g. after swapping Page 1 and Page 3, the page captions will look like: "Page 3 / Page 2 / Page 1 / Page 4". But, after you press the OK button and close the Preferences window, and reopen it again, the page captions will be restored to the default order of "Page 1 / Page 2 / Page 3 / Page 4". The pages content will however be kept as it should, so the content will be kept swapped.
  10. Sounds great, thank you for letting us know about the resolution.
  11. In our first test run under Win8.1 we've also attempted to install Frame Manager, but the installer failed. Frame Manager doesn't seem to be compatible with Win8.x at all, but the drivers work fine under Win8.x -- at least for us. We've installed the Mini Monitor device drivers using the drivers copied to \Program Files\Samsung\FrameManager by Samsung Frame Manager installer, and it worked just fine. In one of your previous posts you seemed to have indicated that it didn't work for you under both Win7 and Win8, but now you say it works fine under Win7? Just to make sure it's not a driver issue, please try to change the Mini Monitor drivers to the ones we're using. The driver version is the same with yours, but we've already got two different Samsung SPF driver sets, both with the same version, so you never know with Samsung I'll send you the download link to our drivers in private message. BTW, our "Plan B" for the Samsung issue is that we would implement an alternative driver path in our code, to let you use generic LibUSB drivers with Samsung DPFs. That may or may not help in your situation though, since -- if I properly understand what you wrote -- the device keeps disconnecting after 5 seconds even if you don't start AIDA64 at all. It could well be a driver issue that may be resolved with the LibUSB driver, but it is also possible that it's a hardware flaw that will not be resolved by a driver change. Anyway, if you have time and energy left to hassle with your SPF-87H, you can try our LibUSB solution soon. I'll send you a message once the LibUSB driver and the AIDA64 beta with LibUSB Samsung SPF support is ready to be test-driven.
  12. In case the Mini Monitor device disappears from the system after that 5 seconds elapsed, even if you don't start AIDA64 at all, then it seems to be an issue that is related to the Samsung driver or the device itself. Have you tried to connect the device to another computer? Have you tried to check the Windows Event Logs, to see whether there's any reference to why the device gets disconnected? I'm starting to feel like your particular SPF-87H device has some hardware flaws... Maybe try updating the firmware. I'll soon run out of ideas
  13. It's quite puzzling. Have you tried to connect the DPF to another USB controller? Have you tried to power the DPF off, power it on again, and switch the device to Mini Monitor Mode on the DPF, and see what happens when you start AIDA64?
  14. Can you check what happens if you let AIDA64 switch the device to Mini Monitor Mode, but then you quickly close AIDA64, before that 5 seconds elapses? Will the device stay in Mini Monitor Mode? Something must be causing the DPF to switch back to Mass Storage Mode again, but I have no idea what could it be, as long as Samsung's own application is completely removed from your system. We've now double-checked with the same drivers you're using, under Windows 8.1 64-bit, with both a SPF-75H and a 800P DPF, and found no such issues you're experiencing. It works absolutely smooth on our test system.
  15. Since you've got some kind of errors even with the AIDA64 kernel drivers disabled, and the error points to nVIDIA video drivers, I'd say your system is indeed not 100% stable. The BSoD's you get when running AIDA64 benchmarks may just be due to the system instability, and not due to a bug in AIDA64.
  16. The issues will be fixed in the next AIDA64 beta update due in a day or two from now. I'll post the download link here, as soon as the new AIDA64 beta is available
  17. Yes, that's the same driver we're using. Do you have any remaining Samsung devices in the Device Manager, under Display Adapters? If yes, then try to uninstall that, including removing its drivers.
  18. It sounds quite odd. After the uninstallation, were all Samsung Frame Manager related files removed? Can you please check if there's any of them left under \Program Files\Samsung ? What version of Frame Manager did you have installed? Can you maybe check the driver version and driver date for the Mini Monitor driver? There're quite a few versions out there, and maybe you're not using the driver we've used for our test runs.
  19. Thank you. Please let me know the exact configuration of your CPU and memory, like BCLK frequency, CPU core multiplier, and DRAM:BCLK ratio as configured in the BIOS Setup.
  20. You're right, AIDA64 does not yet cover those points. We'll have to work on enabling proper detection in such environment as well. As for logon count, I suppose it doesn't count Microsoft account logins, that's why it doesn't increase with furter logons. Regards, Fiery
  21. 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
  22. 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.
  23. Thank you for the feedback, I'm glad you've managed to sort it out.
  24. No, we're not planning to enable that. It would make configuration too complex and hard to follow for many.
  25. T-Balancer bigNG supports 12 temperature inputs, and AIDA64 implements native support for it.
×
×
  • Create New...