![]() ![]() Reliable recovery mechanism (for example, no bricking of devices) Seamless firmware update with no user interaction The primary requirements from the USB device firmware update process are: ![]() This article outlines a recommended method to update USB device firmware without a co-installer. This poses a challenge to existing USB device firmware update process. However, co-installers aren't supported by the new "Universal INF" standard, which is a requirement on Windows 10. USB Device vendors use co-installers to update device firmware for devices that use inbox USB device drivers. To learn how to work around this change, see WDF redistributable co-installers don't work in the WDK known issues article. Still, as long as you don't change everything at once, you should be able to make sense of it much easier now, when all but one device have names (instead of having 8 devices called USB Audio Device).Starting with the WDK for Windows 11, version 22H2, WDF redistributable co-installers are no longer supported. Well first of all, although for me it's been running with not a hint of a problem for a couple of days now, and I really can't see how any problems should come from this (XP-Übernerds, feel free to comment): DO THIS AT YOUR OWN RISK!Īlso, this doesn't solve the problem that everything changes when you plug your device into another USB port – because Windows will repeat the automatic install for every single port, so you'll have to repeat the manual install steps from above as well. Enjoy clean and understandable entries in you device lists. Ignore the warning about the driver not being digitally signed (you should be used to that by now, anyway).ħ. The name of your edit should appear in the list.Ħ. specific location' > 'Don't search, I will choose. Right-click, choose 'Update driver', and click your way through the following dialogs: 'Can Windows connect. Then go to your Device Manager (Start > Settings > System > Hardware).Ĥ. If you haven't installed your device already, let Windows finish it's automatic install (it usually finds the generic drivers by itself when you first connect the device).Ģ. Then save the file – UNDER THE NEW NAME, into C:\WINDOWS\inf\ġ. Just edit the string in both lines to whatever you like (I'd be careful with non-ASCII characters like ü or é, though, stick to English, that should be safe)ħ. This one and line 1521 above (USB\CLASS_01.DeviceDes="USB Audio Device") are the key.Ħ. ![]() Search for this string: USBGenericDesc="USB Audio Device" (note: the quotes are part of the string), you should find it in line 1522. Obviously, DON'T OVERWRITE wdma_usb.inf AND/OR USE IT AS FILENAME FOR YOUR MODIFIED FILE, as then all your future installs will have the name you're just about to enter.ĥ. I call mine wdma_usb_devicename, so I know it's derived from wdma_usb and which device it's for.ģ. Duplicate it, leave it in the same directory and give it a name that makes sense. The INF file for the generic USB audio driver is located under C:\WINDOWS\INF\ and is called wdma_usb.infĢ. It took me about 5 minutes! So, even if XP is slowly approaching its final days, maybe someone else is finding this useful, hence I'm posting a quick how-to:ġ. Sounds familiar? Well, after adding the 7th of those devices and getting really annoyed of having to edit my MIDI OX routing once about every week, I googled a bit and found this invaluable piece of advice on the Max/MSP forums: Did you know you can just copy and hack the INF file and edit any name in there? What's worse, the numbers change when you change ports or sometimes even when you switch your devices on in the wrong order. When you have more than one controller using the generic Plug'n'Play drivers that come with Windows XP, it just gives them numbers and there's no way of knowing which is which. Here's a problem any XP-User with more than one controller knows, I reckon: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |