Disconnect the device from the system and reconnect it to the same physical port. Note If you change the physical port then you must repeat steps 1 through 4. As part of the driver package, you provide an. The following example.
You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufacture's name, the name of your signed catalog file, the correct device class, and the vendor identifier VID and product identifier PID for the device. Also notice that the setup class is set to "USBDevice". You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. We recommened that you provide a universal INF.
Only include a ClassInstall32 section in a device INF file to install a new custom device setup class. INF files for devices in an installed class, whether a system-supplied device setup class or a custom class, must not include a ClassInstall32 section. Except for device-specific values and several issues that are noted in the following list, you can use these sections and directives to install WinUSB for any USB device.
These list items describe the Includes and Directives in the preceding. You should not modify these directives. Services section includes the system-supplied. HW : This section is the key in the. It specifies the device interface globally unique identifier GUID for your device.
When Winusb. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID.
Most USB devices can use these sections and directives without modification. Note Each co-installer has free and checked versions. Each time Winusb. To use WinUSB as the device's function driver, you create a driver package. The driver package must contain these files:. Create a driver package folder on the machine that the USB device is connected to. But in this case I have no any files to sign nor. If you only care about supporting Windows 8.
Another option would be to use Zadig or the related library libwdi to install the driver for your device. I would only recommend this for small, temporary, or organization-internal installations since it is kind of a hack it installs its own certificate into your Trusted Root Certification Authorities list.
You could also look into disabling driver signature enforcement on your computer if you want to use the unsigned INF file.
If none of those options are going to work for you, then you need to look into buying a code-signing certificate from a certificate authority and signing your driver. Code signing for Windows is an ever-evolving field but my article Practical Windows Code and Driver Signing attempts to document what you need to know. Active 2 years, 6 months ago.
Hacker Software Download.
0コメント