Connecting new devices stops device from working

[Furyspark]

As brilliant as this software is, it is giving me issues when connecting new devices.

Every time (after a reboot) I connect a keyboard OR mouse for the 4th time(possibly related to the amount of (virtual) keyboards/mice I have connected), that device doesn't transmit anything to Windows anymore. But it does still light up, and the other devices that were already connected still work fine. After that, any device I connect has the same issues. Until a reboot of Windows, which (usually) fixes things. Until I (re)connect devices again in the same way.

Now mind, this is BEFORE I ran any programs to create a context at all. And after I uninstall Interception and reboot my pc, and try connecting devices in the same way, everything works like expected again.

Also note, it doesn't matter if it's the same device or different devices I (re)connect. 4th time is the charm (in my case). Also not sure if related to Windows 10 or if this would be the case for all Windows systems, as I don't have a W8/W7 device to test it on. Though my notebook is giving the same issues (also W10).

[oblitum]

Thanks for reporting this... I suspect I realize what's happening here but I'm unable publish a fix because it means resigning the drivers, which I'm not able to do at the moment.

What I think is happening is that your reattaching process is increasing the suffix Windows use to name its device objects (device objects can be browsed with OSR DeviceTree for example). It's like something KbdClass0, KbdClass1, and so on. I've implemented Interception to filter devices up to the 9 suffix since previously I didn't know how the suffixes would go beyond that, increase to 10 or to the ASCII char coming after the character for 9, and indeed, it counts using just one char through the ASCII table. I've implemented Interception to just ignore and don't filter devices not ending with a 0-9 suffix, there may be a problem here. Your reattaching, I guess, instead of assigning the same name with same suffix for the same device on every attachment should be giving instead a newly suffixed device name.

[Furyspark]

Ah, that would explain it. Would you perhaps know of a way to reset the count and/or rename the device objects? That would be a temporary fix, at least.

I don't believe I can remove all the excess devices to start at 2/3, unfortunately. Razer and Logitech install a (virtual) keyboard AND mouse driver for every device I connect, and I don't know of a way (at the moment) to do something against that.

[oblitum]

Sorry, I dunno. This naming scheme is really internal behaviour of Windows drivers.

[oblitum]

Closing for now since solution is known and can be solved increasing maximum number of devices with access to driver sources. That's, in case this is indeed the solution for this particular report.

[Furyspark]

That is no solution, however. It can happen without starting any Interception-dependent program, after just having installed the driver and just unplugging and replugging a device a couple of times.

We can compile all we want, but in the end, it is most likely something in the part of the source code we have no access to without a license.

And yes, just to be sure, I have tried this, and also compiled the accessible source code with max mice and max keyboards set to 500.

[oblitum]

Hi, this has never been a issue for me and I've previously licensed it with specific purpose of having an increase of the number of devices supported, so, people interested enough may indeed have access to this by licensing. Changing library headers is not advised since library and drivers must be in-sync regarding such configuration, changing header alone can only bring more problems.

[AlexMKX]

@oblitum it is fixed in licensed version?
If yes, how I can get it?

[TaranVH]

"Can be solved by increasing maximum number of devices with access to driver sources"... what does that mean? How do I do that?

[Furyspark]

I'm not 100% sure either, but it seems this issue has been fixed regardless in the currently latest release (v1.0.1)

[oblitum]

As can be read at https://github.com/oblitum/Interception#license. There's a license that gives access to all source code including drivers. With access to them, increasing the limit and doing a custom build is trivial. The only remaining issue is signing, which requires acquiring a certificate to run it on any machine, or using the updated drivers through a self-signed certificate in a machine that's started with TESTSIGNING on.

I currently assume it as solved because I've licensed the drivers to companies and helped them doing exactly that. They needed more devices, they licensed drivers sources, signed with their own certificate, and the limit was trivially increased.

[TaranVH]

Mikau, I did uninstall 1.0.0, and I installed 1.0.1, but I still have the same issue.

Forgive me for being daft, but I still don't get it. Much of this stuff is very new to me, and I'm simply using a tool called intercept.exe created by Kamaz.

Is the problem that Logitech and Corsair are not using the drivers that Oblitum has provided to them...?

Or am I supposed to install a "self-signed certificate" onto my own computer? (And how?)

Or... should I uninstall all these devices in my device manager, http://i.imgur.com/BmMw9GF.png then plug them in and hope that Windows finds and installs the newest drivers for all my USB devices?

Or... do I just need to "contact francisco@oblita.com for acquiring a commercial license?" How much does that cost?

Any help is greatly appreciated. I'm trying hard to learn this stuff, but I'm not a programmer, I'm just a video editor who wants to have more keyboards for macro keys.