[Q] Why new releases have no Setup Information file?

nefarius / ScpToolkit

Windows Driver and XInput Wrapper for Sony DualShock 3/4 Controllers

http://forums.pcsx2.net/Thread-ScpToolkit-XInput-Wrapper-aka-ScpServer-Reloaded

GNU General Public License v3.0

3.1k stars 539 forks source link

[Q] Why new releases have no Setup Information file? #116

Closed mirh closed 8 years ago

mirh commented 8 years ago

I mean, I always somewhat felt like the only way to make drivers stick was manually telling device manager "use this inf". Unfortunately the only one I can find in the new "ScpToolkit_Setup only" versions is ScpVBus one.

I see that with the installer forcing the driver for even the most noob that may have become completely not necessary. But is there any technical reason for their exclusion?

EDIT: or better, why these are created only when running the installer for the first time?

nefarius commented 8 years ago

The driver *.INF files for Bluetooth and controllers are always created on demand, that's why you won't find any shipped with the setup. The driver itself is embedded in libwdi.dll and gets customized for every system it's installed on. That's how libwdi is designed so I stick to that.

mirh commented 8 years ago

Oh, thank you. I missed a lot of this new "revamped architecture" though. And there's nothing in the Wiki. Is there anywhere I could read on the reasons of the switch to libusb?

nefarius commented 8 years ago

Not really, I know I'm far behind the documentation, I promise improvement ;)

The switch from WinUSB to libusbK was a bit of an accident I'm afraid when I was diagnosing problems with the DS4 and I didn't switch back because... reasons =P

mirh commented 8 years ago

Ehrm.. well, you are the boss. Thanks for your time!

nefarius commented 8 years ago

Every method has it's own pros and cons:

Using your standard signed INF/CAT/SYS configuration for shipping drivers is the easiest for the end-user since the installation can be handled by OS-included tools. Downside is that an additional Hardware ID which might be perfectly compatible breaks consistency of the INF with the signature and you (well, me) have to re-sign it.
Using additional tools like libwdi (the core that powers Zadig) overcomes the signature limitation by re-creating a self-signed INF for every device/installation. Downside of this is a breach of privacy since the end-users certificate store has to be modified and it also depends on libwdi to work on every target system.

So there is no clear winner. As a developer less code is better code so I'll stick with the first method.

mirh commented 8 years ago

Ehrm.. You already had answered to this question :p This, if any, replies to #380, for as much as it doesn't mention the mini-HID driver scenario.

nefarius commented 8 years ago

Just felt the urge to clarify. =P