![install ppjoybus.sys install ppjoybus.sys](https://store.donanimhaber.com/53/03/eb/5303ebc4191694ccd12ef080dd52f305.jpg)
Showing a meaningful device description in Device Manager You have to use most device specific hardware-ID in your INF. If you do write your INF then there is no point in building the device to report compatible-ID because you cannot certify your INF with a compatible-ID match.
#Install ppjoybus.sys install#
If you have a custom driver for your device, you can use the “USBDevice” setup class in the INF.įor some reason, if you have to install the device under a custom class then you do need to write your own INF. Note that this class is not limited to WinUSB. On down-level OS versions, this class is defined by the new INF available through Windows Update. This class is system-defined on Windows 8.
![install ppjoybus.sys install ppjoybus.sys](https://a.fsdn.com/con/app/proj/vjoystick/screenshots/328729.jpg)
When a device is installed by using WinUSB.INF on Windows 8, it automatically installs the device under the “USBDevice” class. The compatible ID and USBDevice definitions are shown here:ĬlassGuid= It also includes a newly defined setup class called “USBDevice”. The INF includes an install section that references a compatible ID called USB\MS_COMP_WINUSB. In Windows 8, the in-box Winusb.inf file has been updated. Those sections are required for instantiating the service, copying inbox binaries, and registering DeviceInterfaceGUID that is required by applications to find the device and talk to it. The custom INF must specify your device specific hardware ID and also include sections from the inbox Winusb.inf. , and then install the driver on the target machine. Prior to Windows 8 if you choose Winusb.sys as the function driver for your device, you have to write a custom INF (see In this blog, we’ll explain how you can build your device so that the Winusb.sys gets installed automatically on Windows 8 and earlier versions of the operating system. If you are developing a USB device for which Windows doesn’t include an in-box class driver, you can use Winusb.sys as the device driver instead of writing your own driver. Is a Microsoft-provided kernel-mode client driver for USB devices.