Find Usb Serial Number Registry
2021年5月27日Download here: http://gg.gg/uqrs7
-->
Software to allow USB Devices based on serial number - so need to add serial number of over 120 devices so that only those devices can be used on work computers. The serial number it works on is the one showing in device manager, which is why I need to find a way of retrieving that number. Export HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersion registry key to text file on USB thumbdrive. Boot into Windows, open registry key dump in Notepad, copy DigitalProductId value into the clipboard. Paste clipboard into Javascript. Here’s a PowerShell solution that will give you the serial number of all ’USB Mass Storage Devices’ mounted on the system which you run it. It uses Get-CIMInstance to query the Win32PnPSignedDriver class to get the property values with filtering, looping, setting a couple variables, using a method, etc. Some programs don’t offer the option to view a serial number in the registry. If you’re having a hard time finding a serial number, there are a number of serial programs (called key finders) available free on the internet to help you find the correct code. The volumes that have been mounted and the assigned drive letters are stored in the following registry entry: System MountedDevices Locating the USB drive’s manufacturer name and serial number in this registry key may provide examiners with the drive letter of the volume. Figure 4: Locating USB drive in /System/MountedDevices.
Summary
*Registry keys that must be set by OEMs to define USB descriptors.
Applies to:
*Windows 10
Last updated:
*November 2015
OEMs must set several registry values to make sure that their device enumerates with the correct metadata when connected to a computer. These values specify device and configuration descriptors for the USB device-side drivers in Windows. OEMs that create and include their own interfaces must set additional registry values in order for their interfaces to be loaded and used.
Registry keys related to the device-side USB drivers are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This topic describes settings for the preceding key and subkeys that define the device, configuration, and interface descriptors for the device.USBFN registry key
Configuration information for the USB device are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This table describes its subkeys. Some of them can be modified by OEMs. More information about the supported values for each subkey is provided in sections below.SubkeyDescriptionAlternatesThis subkey contains additional subkeys that describe an interface that has one or more alternate settings.AssociationsThis subkey defines Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. Each subkey represents a different IAD and OEMs can modify the values for those subkeys.DefaultThis subkey contains default values that are used to describe device-specific settings such as the VID and PID. This is a Microsoft-owned subkey whose values are overridden by those in the parent key.ConfigurationsThis subkey contains additional subkeys that contain configuration descriptor values that are used during USB enumeration. For example, the standard test configuration might exist under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurationsTestConfig.ConfigurationsDefaultThis is a Microsoft-owned subkey. It contains values for the default configuration. The interfaces in the default configuration are added before the current configuration present when the IncludeDefaultCfg value is set to 1 under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key.InterfacesThis subkey contains additional subkeys that describe specific interface descriptors. For example, the IP over USB interface may reside under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfacesIpOverUsb. The name of the interface subkey is also used as the hardware ID of the USBFN child device for loading the USBFn class driver. In the IP over USB example, the hardware ID of the USBFN child device will be USBFNIpOverUsb.
This table describes the values that OEMs can define in the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key. Values that are not defined in this key assume the default values defined by Microsoft under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNDefault.
All OEMs must set the idVendor, idProduct, ManufacturerString, and ProductString values. OEMs that create and add their own interfaces must also set CurrentConfiguration to the name of the subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that includes their interfaces in the InterfaceList.ValueTypeOwnerDescriptionIncludeDefaultCfgREG_DWORDOEMSet to 1 when OEMs want to include the interfaces of the Default configuration such as IpOverUsb or MTP.idVendorREG_DWORDOEMThe vendor identifier for the device descriptor that is sent to the host during enumeration.idProductREG_DWORDOEMThe product identifier for the device descriptor that is sent to the host during enumeration.ManufacturerStringREG_SZOEMThe manufacturer string that is sent to the host to identify the manufacturer of the device.ProductStringREG_SZOEMA string that describes the device as a product. The default value is Windows 10 Mobile Device. This value is used as the display name of the device in the connected computer’s user interface. OEMs should make sure that this value matches the value of the PhoneModelName value under the DeviceTargetingInfo subkey.iSerialNumberREG_DWORDOEMIf this value is set to 0, then the device does not have a serial number. If this value is non-zero or does not exist, then the serial number is generated uniquely per device.CurrentConfigurationREG_SZOEMThis string must correspond to the name of a configuration subkey. This string determines which configuration to use to build a configuration descriptor for USB device enumeration.USBFNConfigurations registry key
This table describes the values that OEMs can define for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations. Each subkey represents a different USB configuration. If the OEM wants to create their own interface, the OEM must define a new configuration which contains the interfaces to be used. To do this, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that uses the name of the configuration and populate the subkey with the values in this table. Additionally, for the USB driver to use the new configuration, the CurrentConfiguration value (described in the preceding table) must be set to the name of the configuration subkey.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or Microsoft
Contains a list of interface names that correspond to interface subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces, the IAD associations defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations, and the alternate interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates. Those keys determine the interfaces that are used to describe the composite configuration descriptor.
If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, this list is appended to the Microsoft-owned default interface list to create the complete interface list that the device will use to enumerate.MSOSCompatIdDescriptorREG_BINARYOEM or Microsoft
Optional. Defines an Extended Compat ID OS Feature Descriptor for the configuration. If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, the functions in this descriptor are appended to the functions and interfaces in the default configuration.USBFNInterfaces registry key
This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces.
Garmin Support Center is where you will find answers to frequently asked questions and resources to help with all of your Garmin products. Skip navigation links. All Wearables & Smartwatches Fashion Smartwatches MARQ Luxury Watch Collection Running Multisport Adventure Swimming Diving Golf Fitness Tracking Kids Wearables. This setup will install / pre-load all Garmin USB Drivers on your system and upgrade older versions if found. These drivers are designed for use with those GPS units that support USB transfer of data to/from the PC - not to include the iQue. This setup also includes the drivers for the USB Data Card Programmer. Garmin usb ant stick driver for mac.
Each subkey represents a different USB interface. To define an interface, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces using the name of the interface, and populate it with the values in the table below. Additionally, an interface will only be included if the interface is part of the InterfaceList of the CurrentConfiguration.ValueTypeOwnerDescriptionInterfaceDescriptorREG_BINARYOEM or MicrosoftA binary representation of an interface descriptor to send to the host during USB enumeration. The bInterfaceNumber and iInterface values are automatically populated by the USB function stack after compiling a full configuration descriptor to avoid conflicts with other interface descriptors.InterfaceGUIDREG_SZOEM or MicrosoftA GUID that uniquely identifies an interface on the bus.InterfaceNumberREG_DWORDOEM or MicrosoftOptional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.USBFNAlternates registry key
The alternates subkey is used to define a single interface that has one or more alternate interfaces. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates.
Each subkey represents a different interface. To define an interface with alternate settings, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates by using the name of the interface, and populate it with the values in the table below.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or MicrosoftA list of two of more interface names that correspond to interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces. That key collectively defines an interface with alternate settings. The first interface corresponds to alternate setting 0, the second interface corresponds to alternate setting 1, and so on.InterfaceNumberREG_DWORDOEM or MicrosoftOptional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.USBFNAssociations registry key
OEMs can specify associations by defining Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations.
Each subkey represents a different IAD. To define an association, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations by using the name of the IAD, and populate it with the values in the table below.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or MicrosoftA list of interfaces or alternate interfaces that are associated with a USB function. If the size of the list is less than 2, then the function driver stack fails to load. Other functions or interfaces continue to load.bFunctionClassREG_DWORDOEM or MicrosoftThe class code of the function, set to 02.bFunctionSubClassREG_DWORDOEM or MicrosoftThe subclass code of the function, set to 0d.bFunctionProtocolREG_DWORDThe protocol code of the function, set to 01.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.
Use case: Enabling MirrorLink
MirrorLink is an interoperability standard that allows integration between mobile devices and car infotainment systems. The device must expose a USB CDC NCM interface to the MirrorLink client. As a Communications Device Class (CDC) device, it is required to describe the data interfaces by using either an Interface Association Descriptor (IAD) and/or a CDC Function Union Descriptor.
To enable MirrorLink connectivity on Windows 10 Mobile Device, OEM must make these changes to expose an IAD.
*
Create an association for the communication and data interfaces by using an Interface Association Descriptor (IAD) by setting registry values shown in the preceding table.
*
In addition to the registry settings, set this registry value to a non-zero value.ValueTypeOwnerDescriptionMirrorLinkREG_DWORDOEM or MicrosoftA non-zero value indicates the interface supports MirrorLink. The USB function stack does not stall the MirrorLink USB command.
*
Class-specific descriptors can be included in the interface descriptor set that is defined in the registry. The size field must be set in those descriptors so that USB function driver stack can parse them accurately.
Alternatively, a CDC Function Union Descriptor can also be defined as a Class-Specific Interface Descriptor; however, the interface numbers specified by the Union descriptor are static and are not be assigned by the USB function driver stack, and the presence of a Union descriptor does not cause the interfaces described by it to be associated with a single child PDO. An IAD is required for that association.Usb Drive Serial NumberRelated topicsUsb Serial Controller Driver
USB device-side drivers in Windows
Developing Windows drivers for USB function controllers
Download here: http://gg.gg/uqrs7
https://diarynote-jp.indered.space
-->
Software to allow USB Devices based on serial number - so need to add serial number of over 120 devices so that only those devices can be used on work computers. The serial number it works on is the one showing in device manager, which is why I need to find a way of retrieving that number. Export HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersion registry key to text file on USB thumbdrive. Boot into Windows, open registry key dump in Notepad, copy DigitalProductId value into the clipboard. Paste clipboard into Javascript. Here’s a PowerShell solution that will give you the serial number of all ’USB Mass Storage Devices’ mounted on the system which you run it. It uses Get-CIMInstance to query the Win32PnPSignedDriver class to get the property values with filtering, looping, setting a couple variables, using a method, etc. Some programs don’t offer the option to view a serial number in the registry. If you’re having a hard time finding a serial number, there are a number of serial programs (called key finders) available free on the internet to help you find the correct code. The volumes that have been mounted and the assigned drive letters are stored in the following registry entry: System MountedDevices Locating the USB drive’s manufacturer name and serial number in this registry key may provide examiners with the drive letter of the volume. Figure 4: Locating USB drive in /System/MountedDevices.
Summary
*Registry keys that must be set by OEMs to define USB descriptors.
Applies to:
*Windows 10
Last updated:
*November 2015
OEMs must set several registry values to make sure that their device enumerates with the correct metadata when connected to a computer. These values specify device and configuration descriptors for the USB device-side drivers in Windows. OEMs that create and include their own interfaces must set additional registry values in order for their interfaces to be loaded and used.
Registry keys related to the device-side USB drivers are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This topic describes settings for the preceding key and subkeys that define the device, configuration, and interface descriptors for the device.USBFN registry key
Configuration information for the USB device are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This table describes its subkeys. Some of them can be modified by OEMs. More information about the supported values for each subkey is provided in sections below.SubkeyDescriptionAlternatesThis subkey contains additional subkeys that describe an interface that has one or more alternate settings.AssociationsThis subkey defines Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. Each subkey represents a different IAD and OEMs can modify the values for those subkeys.DefaultThis subkey contains default values that are used to describe device-specific settings such as the VID and PID. This is a Microsoft-owned subkey whose values are overridden by those in the parent key.ConfigurationsThis subkey contains additional subkeys that contain configuration descriptor values that are used during USB enumeration. For example, the standard test configuration might exist under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurationsTestConfig.ConfigurationsDefaultThis is a Microsoft-owned subkey. It contains values for the default configuration. The interfaces in the default configuration are added before the current configuration present when the IncludeDefaultCfg value is set to 1 under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key.InterfacesThis subkey contains additional subkeys that describe specific interface descriptors. For example, the IP over USB interface may reside under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfacesIpOverUsb. The name of the interface subkey is also used as the hardware ID of the USBFN child device for loading the USBFn class driver. In the IP over USB example, the hardware ID of the USBFN child device will be USBFNIpOverUsb.
This table describes the values that OEMs can define in the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key. Values that are not defined in this key assume the default values defined by Microsoft under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNDefault.
All OEMs must set the idVendor, idProduct, ManufacturerString, and ProductString values. OEMs that create and add their own interfaces must also set CurrentConfiguration to the name of the subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that includes their interfaces in the InterfaceList.ValueTypeOwnerDescriptionIncludeDefaultCfgREG_DWORDOEMSet to 1 when OEMs want to include the interfaces of the Default configuration such as IpOverUsb or MTP.idVendorREG_DWORDOEMThe vendor identifier for the device descriptor that is sent to the host during enumeration.idProductREG_DWORDOEMThe product identifier for the device descriptor that is sent to the host during enumeration.ManufacturerStringREG_SZOEMThe manufacturer string that is sent to the host to identify the manufacturer of the device.ProductStringREG_SZOEMA string that describes the device as a product. The default value is Windows 10 Mobile Device. This value is used as the display name of the device in the connected computer’s user interface. OEMs should make sure that this value matches the value of the PhoneModelName value under the DeviceTargetingInfo subkey.iSerialNumberREG_DWORDOEMIf this value is set to 0, then the device does not have a serial number. If this value is non-zero or does not exist, then the serial number is generated uniquely per device.CurrentConfigurationREG_SZOEMThis string must correspond to the name of a configuration subkey. This string determines which configuration to use to build a configuration descriptor for USB device enumeration.USBFNConfigurations registry key
This table describes the values that OEMs can define for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations. Each subkey represents a different USB configuration. If the OEM wants to create their own interface, the OEM must define a new configuration which contains the interfaces to be used. To do this, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that uses the name of the configuration and populate the subkey with the values in this table. Additionally, for the USB driver to use the new configuration, the CurrentConfiguration value (described in the preceding table) must be set to the name of the configuration subkey.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or Microsoft
Contains a list of interface names that correspond to interface subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces, the IAD associations defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations, and the alternate interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates. Those keys determine the interfaces that are used to describe the composite configuration descriptor.
If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, this list is appended to the Microsoft-owned default interface list to create the complete interface list that the device will use to enumerate.MSOSCompatIdDescriptorREG_BINARYOEM or Microsoft
Optional. Defines an Extended Compat ID OS Feature Descriptor for the configuration. If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, the functions in this descriptor are appended to the functions and interfaces in the default configuration.USBFNInterfaces registry key
This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces.
Garmin Support Center is where you will find answers to frequently asked questions and resources to help with all of your Garmin products. Skip navigation links. All Wearables & Smartwatches Fashion Smartwatches MARQ Luxury Watch Collection Running Multisport Adventure Swimming Diving Golf Fitness Tracking Kids Wearables. This setup will install / pre-load all Garmin USB Drivers on your system and upgrade older versions if found. These drivers are designed for use with those GPS units that support USB transfer of data to/from the PC - not to include the iQue. This setup also includes the drivers for the USB Data Card Programmer. Garmin usb ant stick driver for mac.
Each subkey represents a different USB interface. To define an interface, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces using the name of the interface, and populate it with the values in the table below. Additionally, an interface will only be included if the interface is part of the InterfaceList of the CurrentConfiguration.ValueTypeOwnerDescriptionInterfaceDescriptorREG_BINARYOEM or MicrosoftA binary representation of an interface descriptor to send to the host during USB enumeration. The bInterfaceNumber and iInterface values are automatically populated by the USB function stack after compiling a full configuration descriptor to avoid conflicts with other interface descriptors.InterfaceGUIDREG_SZOEM or MicrosoftA GUID that uniquely identifies an interface on the bus.InterfaceNumberREG_DWORDOEM or MicrosoftOptional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.USBFNAlternates registry key
The alternates subkey is used to define a single interface that has one or more alternate interfaces. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates.
Each subkey represents a different interface. To define an interface with alternate settings, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates by using the name of the interface, and populate it with the values in the table below.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or MicrosoftA list of two of more interface names that correspond to interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces. That key collectively defines an interface with alternate settings. The first interface corresponds to alternate setting 0, the second interface corresponds to alternate setting 1, and so on.InterfaceNumberREG_DWORDOEM or MicrosoftOptional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.USBFNAssociations registry key
OEMs can specify associations by defining Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations.
Each subkey represents a different IAD. To define an association, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations by using the name of the IAD, and populate it with the values in the table below.ValueTypeOwnerDescriptionInterfaceListREG_MULTI_SZOEM or MicrosoftA list of interfaces or alternate interfaces that are associated with a USB function. If the size of the list is less than 2, then the function driver stack fails to load. Other functions or interfaces continue to load.bFunctionClassREG_DWORDOEM or MicrosoftThe class code of the function, set to 02.bFunctionSubClassREG_DWORDOEM or MicrosoftThe subclass code of the function, set to 0d.bFunctionProtocolREG_DWORDThe protocol code of the function, set to 01.MSOSExtendedPropertyDescriptorREG_BINARYOEM or MicrosoftOptional. Defines an Extended Property OS Feature Descriptor for the interface.
Use case: Enabling MirrorLink
MirrorLink is an interoperability standard that allows integration between mobile devices and car infotainment systems. The device must expose a USB CDC NCM interface to the MirrorLink client. As a Communications Device Class (CDC) device, it is required to describe the data interfaces by using either an Interface Association Descriptor (IAD) and/or a CDC Function Union Descriptor.
To enable MirrorLink connectivity on Windows 10 Mobile Device, OEM must make these changes to expose an IAD.
*
Create an association for the communication and data interfaces by using an Interface Association Descriptor (IAD) by setting registry values shown in the preceding table.
*
In addition to the registry settings, set this registry value to a non-zero value.ValueTypeOwnerDescriptionMirrorLinkREG_DWORDOEM or MicrosoftA non-zero value indicates the interface supports MirrorLink. The USB function stack does not stall the MirrorLink USB command.
*
Class-specific descriptors can be included in the interface descriptor set that is defined in the registry. The size field must be set in those descriptors so that USB function driver stack can parse them accurately.
Alternatively, a CDC Function Union Descriptor can also be defined as a Class-Specific Interface Descriptor; however, the interface numbers specified by the Union descriptor are static and are not be assigned by the USB function driver stack, and the presence of a Union descriptor does not cause the interfaces described by it to be associated with a single child PDO. An IAD is required for that association.Usb Drive Serial NumberRelated topicsUsb Serial Controller Driver
USB device-side drivers in Windows
Developing Windows drivers for USB function controllers
Download here: http://gg.gg/uqrs7
https://diarynote-jp.indered.space
コメント