Jump to content
Flirc Forums

Search the Community

Showing results for tags 'windows 7'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Flirc forums
    • Skip
    • Raspberry Pi Cases
    • Flirc USB
    • Flirc USB Gen1
    • Jeff Probe

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests

Found 4 results

  1. Hi, I just received a new FLIRC (the new model). I'm running FW 4.05 and GUI 2.0.1 on a Asrock Z77 Pro4 (Windows 7) I'm having two problems: firstly, I can't get the FLIRC to wake the computer. I've tried enabling and disabling "Wake from USB mouse/kb" in the MB BIOS. I've also tried selecting (and deselecting) all of the "Allow device to wake from sleep" check boxes in device manager to no effect. What is weird is that my computer wakes up from sleep fine using a logitech diNovo edge bluetooth keyboard, but nothing happens through FLIRC. Additionally, and this is probably related, whenever I wake the computer from sleep using the keyboard, FLIRC is disconnected, and I need to remove it and plug it back in again. I've tried plugging it in multiple USB 2.0 and 3.0 slots, and they all produce the same error. Also, in the FAQ, I saw that sometimes power supplies can be an issue, but I've got a Seasonic PS, so I don't think that's the issue. I also made sure that "sleep detection" is checked Any ideas? I'd really like to be able to turn my computer on/off with my new harmony remote. Should I try installing 1.4.4? does that work with the newer FLIRC models? TY in advance!
  2. Hi, to resolve my problems with FLIRC and recording of my IR-codes from the Toshiba PC 'Qosmio' IR I tried every option from the 'Advanced' menu item but it keeps in "not working" state. E.g. the error message 'button already exists' occurs very often and even if not the recorded commands does not work at all or does not work as expected. Therefore I cannot use my Windows 7 media center HTPC together with FLIRC and my existing setup! I have read a lot of problem reports in this forum and my conclusion is: "Use any remote with your media center" is marketing bullshit. Sorry about my clear words but I'm very disappointed about this WRONG advertising. Why? Because also my IR keyboard "LiteOn SK-7100" shows the same negative result and for around 40 EUR (Amazon.de, approx. twice the price as in the US) FLIRC is a bad experience for me. One positive aspect I recognized: The "Flirc Kodi" device in the Logitech Harmony database works out of the box with my LINUX based Kodi HTPC. (This was only a cross-check if the FLIRC hardware is in general working.) For (e.g.) this use case you may get happy with FLIRC ... Michael P.S. I wrote this to inform other people which may have equal problems and not to get advices / help ...
  3. Hi, I have had a Flirc Gen.1 plastic model for a number of years in an older media PC. That unit had died and I have just setup a ZOTAC Windows 7 Pro PC. I also use a Harmony One remote and added a Flirc device in Kodi flavor. After downloading the current software from your site, I could program keys - but I cannot use the Harmony to operate Kodi (or even use the number-keys within a .txt file). The log reads: Error: unsupported device must have flirc gen 2 enabled device and fw >= 4.1.0 I did google this and ended up with messages based on the same symptoms but with no real solution. There is also mention of some "Zadic" software with no reference on how to use it or whether this did actually help anyone. Is this gen 1 dongle obsolete? Do I need different software, firmware, etc.? Thanx in advance for your help. Cheers, Volker
  4. I was happily using flirc on Windows 10 64 bit for several months. I installed GUI version 1.4.3 which indicated I should update firmware to 3.8. Now it shows disconnected in the GUI on 3 different machines. The interesting thing is that old remotes I programmed are still usable in Kodi and 3 different PC's (Win 7, Win 10, and Ubuntu 14.04) recognize the device, indicate that drivers are properly installed, and that it is functioning correctly. The problem is that I have purchased a new remote and would really like to be able to program it with the GUI. The main machine I want to use the device on is running Windows 10 so I'd prefer to focus on fixing the problem there. I would be happy to roll back to previous versions of GUI/Firmware or send logs (wherever they may be located) to support to find out why the GUI continues to show disconnected. I've tried manually installing drivers, Zadig, etc, although it isn't doing any good and as stated above, Windows 10 sees the device and indicates that it is working properly in device manager.
×
×
  • Create New...