Anyone have any ideas on the 2 questions presented above?
↧
Re: MS-official "WinUSB class" driver for XP, Vista and 7 (salazar)
↧
Re: MS-official "WinUSB class" driver for XP, Vista and 7 (chinzei)
A) Name of WinUsb Device
The device "name" on the Device Manager depends on the OS version (**1).
a) Windows 8/8.1
The device name comes from the device - the iProduct string descriptor
b) Windows XP, Vista, 7
The name is always "WinUsb Device", which comes from winusb.inf
(**1) WinUSB Device - on MSDN site
http://msdn.microsoft.com...hh450799(v=vs.85).aspx
Described in "How to change the device description for a WinUSB device" section
These names are stored on this registry entry for each device
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_vvvv&PID_pppp\<serial-number>\DeviceDesc
At the first plug-in installation, this registry entry is made by the OS. As this registry entry is protected, we can’t change the value of this entry. That is, to change this entry from the default, a custom INF file is required, as described in above MSDN document.
But when "FriendlyName" entry is placed under the same key, Device Manager shows this "name" primarily instead of "DeviceDesc". FriendlyName entry is assigned manually, or by PC application (using SetupDiSetDeviceRegistryProperty(SPDRP_FRIENDLYNAME) under administrator privilege), as discussed on this topic.
http://www.microchip.com/forums/FindPost/477203
B) XP installation
If the target WinXP PC wouldn’t have been installed WinUSB before, "WinUSB Device" plug-in installation using winusbcompat.inf should fail. It’s because winusbcompat.inf refers to winusb.inf.
WinUSB is able to be pre-installed together with winusbcompat.inf. If you would like to customize the "name" of the device, however, ordinary INF-file installation of WinUSB is better.
Tsuneo
The device "name" on the Device Manager depends on the OS version (**1).
a) Windows 8/8.1
The device name comes from the device - the iProduct string descriptor
b) Windows XP, Vista, 7
The name is always "WinUsb Device", which comes from winusb.inf
(**1) WinUSB Device - on MSDN site
http://msdn.microsoft.com...hh450799(v=vs.85).aspx
Described in "How to change the device description for a WinUSB device" section
These names are stored on this registry entry for each device
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_vvvv&PID_pppp\<serial-number>\DeviceDesc
At the first plug-in installation, this registry entry is made by the OS. As this registry entry is protected, we can’t change the value of this entry. That is, to change this entry from the default, a custom INF file is required, as described in above MSDN document.
But when "FriendlyName" entry is placed under the same key, Device Manager shows this "name" primarily instead of "DeviceDesc". FriendlyName entry is assigned manually, or by PC application (using SetupDiSetDeviceRegistryProperty(SPDRP_FRIENDLYNAME) under administrator privilege), as discussed on this topic.
http://www.microchip.com/forums/FindPost/477203
B) XP installation
If the target WinXP PC wouldn’t have been installed WinUSB before, "WinUSB Device" plug-in installation using winusbcompat.inf should fail. It’s because winusbcompat.inf refers to winusb.inf.
WinUSB is able to be pre-installed together with winusbcompat.inf. If you would like to customize the "name" of the device, however, ordinary INF-file installation of WinUSB is better.
Tsuneo
↧
↧
Re: MS-official "WinUSB class" driver for XP, Vista and 7 (salazar)
There is one more issue that eludes me:
On my development computer (Windows 7 64-bit) I do not get a DeviceInterfaceGUID. I have tried numerous times uninstalling the device, deleting it from the registry, etc. Every time it reinstalls but does not give me a DeviceInterfaceGUID with which to open the device. I have not seen this problem on any other computer I have tested on. Is it possible that during development (adding the MS OS descriptors), that it corrupted something in the registry that I am not aware of, that is causing it not to list the DeviceInterfaceGUID?
This computer is running Windows 7 64-bit SP1 (Build 7601). I have tried changing the USB product id to something new, but that also does not seem to solve the problem for me. No matter what I do, the inbox WinUSB drivers plus this winusbcompat.inf file do not register the DeviceInterfaceGUID on this one specific computer. Are there any WinUSB registry settings I could check?
Any ideas what is happening here?
On my development computer (Windows 7 64-bit) I do not get a DeviceInterfaceGUID. I have tried numerous times uninstalling the device, deleting it from the registry, etc. Every time it reinstalls but does not give me a DeviceInterfaceGUID with which to open the device. I have not seen this problem on any other computer I have tested on. Is it possible that during development (adding the MS OS descriptors), that it corrupted something in the registry that I am not aware of, that is causing it not to list the DeviceInterfaceGUID?
This computer is running Windows 7 64-bit SP1 (Build 7601). I have tried changing the USB product id to something new, but that also does not seem to solve the problem for me. No matter what I do, the inbox WinUSB drivers plus this winusbcompat.inf file do not register the DeviceInterfaceGUID on this one specific computer. Are there any WinUSB registry settings I could check?
Any ideas what is happening here?
↧
Re: MS-official "WinUSB class" driver for XP, Vista and 7 (salazar)
Anyone know why the DeviceInterfaceGUID is not being installed on this specific computer?
↧
Re: MS-official "WinUSB class" driver for XP, Vista and 7 (salazar)
After many hours of debugging, I finally figured out that the DeviceInterfaceGUID for WinUSB devices was not being installed *only* when plugging the device into USB 3.0 ports on the Win7 machine. With that information, I finally found this thread:
http://www.microchip.com/forums/m802958.aspx
That thread solved my problem, and hopefully it will help others in this same situation.
http://www.microchip.com/forums/m802958.aspx
That thread solved my problem, and hopefully it will help others in this same situation.
↧
↧