Jump to content


  • Posts

  • Joined

  • Last visited

Boldo's Achievements


Newbie (1/14)



  1. Did a full reinstall today... and guess what? no changes to the problem. Is there really no way we can get the updated v2 formfactor or anything to solve this? At the moment looking into the ancient winlirc solutions but I'm not sure what to buy and get that working. It's a real pain...
  2. Updated to 1803 final a bit ago and did some testing since till now. The problem persists, but a bit less often I feel like! Still a bag of hurt if you ask me. When it works there's still that stupid delay after a (re)boot of about 1-2 minutes. So yeah... it's still a waiting game I guess till this is solved. No difference between the blue and black PCB version, as far as I'm concerned they're 100% interchangeable with same behaviour. On a side note... really wished the new black pcb version had v2 capabilities, finally got hold of the remote I liked and it doesn't work on the v1 :'( . Just guessing it might work with the v2 as I'm not buying the v2 after having bought the black pcb version for nothing really. What do I need yet another Flirc for? On a side note 2.... that stupid bright blue led broke down, which I thought was useless in the first place anyways.
  3. 17133 became available to me today, the RTM version... and no luck again. On a more positive note, I finally found the remote I wanted for quite some time available now loose as a replacement. So ordered 2 of those from different suppliers to have at least something to do. This problem just persists and is really becoming an issue to me to the point I might replace the complete hardware if something I like comes along.
  4. Well I've installed the insiders build 17127 of RS4 now it's available and unfortunately the problem persists. Will try some things in the next days just as in the past but that never made any difference. So it looks like it won't be fixed by Microsoft anytime soon...
  5. Well Jason had a look and I missed his last msg in teamviewer. But for anyone researching this, it seems to be a common issue with USB hardware with the 1709 patch, much as I suspected. Unfortunatly not a lot can be done from Jasons end. Believe I just read in time he wanted to make a post about it in case anyone has the same issue.
  6. Sure I can, I have so before and it didn't make any difference. And yes it doesn't make any sense to me as well. What do you want me to test after I've unscrewed it?
  7. No, I'm not. Reminder, this is the htpc you surely remember now;
  8. No I don't, the htpc starts straight into kodi, and apart from the flirc gui, kodi and some other software titles the htpc is pretty bare. Even removed the tv card + software to a dedicated server to make sure that didn't interfere.
  9. You've seen it yourself over teamviewer, but I'll recap; Yes the gui still detects it, both the older and newer board as I bought a new one as I thought it was faulty. To make it work again I have to reconnect it about 20-30 times or remove it from the device manager and reinstall it etc etc. If I do a hot restart everything keeps working with no issues, but ofc you don't leave it on 24/7. From a cold boot you got this exact problem, ever since the windows 1709 update. The only thing I've tried since is renew the USB drivers with the latest inf pack from Intel to no avail.
  10. Indeed the streacom board. Maybe you like to have the specs of the current setup, it's somewhat older and that might have something to do with it; i3-3225 Intel DH77EB motherboard Planned to upgrade this pc to a more modern setup but still waiting for the new B/H boards by Intel. It's the only reason why I haven't done a total reinstall yet. Have ran a few linux live usb sticks and that confirms the problem lays with the os, maybe drivers, and not the actual hardware.
  11. Has a solution been found to this problem by now? It's getting really annoying to have to keep re-connecting the USB each day in order to get it working, not to mention having the case open on top of my a/v cabinet. So anyone any idea at all?
  12. Well a small update; I can reproduce what you did via teamviewer perfectly and when rebooting it works flawlessly. But on a cold boot (at least 1 min off) it refuses to work. I really have no clue what this is anymore and it's hard to test for you via teamviewer... Any ideas to where to look next?
  13. Well after it worked yesterday reboot after reboot, now after a cold boot this x-mass morning it's back to how it was before. Will look tomorrow, guess I'll use a keyboard again today...
  14. Sure, have installed it for you. I'm at a total loss. What I didn't mention yet is deleting all past drivers versions for Flirc that were present within windows and now it only has the ones supplied with 3.5.2. Will msg you the teamviewer credentials.
  15. A few developments but no solution yet: Followed this support article; https://support.flirc.tv/hc/en-us/articles/200712548-Using-the-ZADIG-Utility I can upgrade to libusbK with the latest version but no difference. Finally my replacement Flirc came in, a new revision with black PCB and overly unnecessary blue led on the back, and exactly the same behaviour! So we can eliminate it comes from the Flirc itself, it should be driver related. Also ever since connecting the new Flirc, I get this error in the Device log; "Error, unsupported device. Must have Flirc Gen2 enabled device and fw >= 4.1.0" Can't seem to get rid of this 'error' now. With the black one it's the same story; first time connecting it worked, next reboot it still worked, but after that it's unplugging and plugging back in till it works which can take up to 15 min to do. Thinking about the maintenance I did after which this happened; it was only using some compressed air to clean the htpc (which I do with all my pc's every year), upgrade to windows 10 version 1709 and since I got problems upgraded to the latest Flirc + FW. Beginning to suspect it's the windows update causing all of this as this setup had been working perfectly since november 2015.
  • Create New...