I reported the post and requested it was moved to off-topic that should of been end-of-story. I'm no lover of the Redmond operating system either, but I don't think that justifies the 'B*gger off, we don't want your kind here' stance you appear to be advocating. I use exactly this trick in my job (self employed computer repair) and you can happily use a Pi for it. The OP has a reasonable number of posts, on this forum, so he's not someone who has blundered on here willy nilly, so its only civilised to give him an answer. Yes, he's asking for a windows driver, but I'm suggesting a method of achieving that using a Pi (or any linux computer) that might achieve what he wants. That is the biggest load of tosh for justifying a totally non Raspberry Pi thread, he is asking for a Windows Driver not a Linux Driver It doesn't always work but it often does. Very often the manufacturer of a chipset for devices will have a no frills generic windows driver on their website. You may use the built-in Device Manager to update the generic Bluetooth radio driver. Pluggy wrote:I often use a linux PC (like a Pi) to establish the exact chipset of a device (often Windows comes up with something unhelpful like 'Unknown Device' in Device Manager) and then look for a generic driver for that chipset for it to work in Windows. I bought a new Bluetooth USB dongle on Amazon and tried to get it working on my Arch Linux and yes, it didnt work, then I looked into these outputs: lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 28de:1142 Valve Software Wireless Steam Controller Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |