Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

bohemian's Achievements


Newbie (1/14)



  1. Oaky the link provided took my VC++ x64 runtime from the newer version 10.0.40219 to an older version 10.0.30319. Uninstalled FLIRC, resinstalled and got some behaviour and same event viewer error as before.
  2. The OS is Windows 7 Ultimate 64-bit SP1 fully updated via Windows Update. The Event Log shows some form of VC++ runtime issue: Faulting application name: Flirc.exe, version:, time stamp: 0x54f4fb86 Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722 Exception code: 0xc0000005 Fault offset: 0x0000980a Faulting process id: 0x2618 Faulting application start time: 0x01d0bb880fa241d2 Faulting application path: C:\Program Files (x86)\Flirc\Flirc.exe Faulting module path: C:\Windows\syswow64\msvcrt.dll Report Id: 4d9b9deb-277b-11e5-98f3-005056c00008
  3. Okay this is fun. Or maybe not, Got the GUI to actually work (0.96 anyway) by building an XP VM and then running the installer there. Lo and behold, it actually finds the device despite there being a hypervisor between the app and the device. I guess as long as never want to upgarde the firmware I'm fine, since this version of the GUI wants a firmware file to updgrade, which doesn't exist any more. Still a crappy expereince when the GUI doesn't work on Win7 for unknown reasons. I'll resist the urge to rate this product on AMZN for now.
  4. So much for that idea. The GUI starts, but says the device is disconnected. Despite the OS saying that it is. Sigh. This isn't easy.
  5. Okay, just installed the 0.96 'XP only' version and now it works. Confusing and a bad user experience to say the least, but whatever. Now to see if this thing works on my Amazon Fire.
  6. Just installed FLIRC Windows GUI Version 1.3.6. After restart, FLIRC drivers are okay and I can see my FLIRC in the device manager (Windows 7 x64). But the FLIRC GUI will not fire up. It seems to try to start but never does. No error messges, nothing. Tried running as Admin, same result. So, is there asecret to getting the GUI working or do I just have an attractive dongle that I can't program? Troubleshooting tips welcome.
  • Create New...