M
Mark Tz
Guest
Hi
We make a device with embedded linux which presents itself via USB as a multifunction device (USB mass storage and network device).
It uses a standard linux driver which presents vendor ID 1d6b (linux foundation) and PID 0104 (multifunction composite gadget) when it is plugged in to a USB port.
We have not had to make a custom INF file for this device, because we have for many years been able to tell windows machines (windows 7 and 10) manually via the device manager to use the built in windows RNDIS driver. This is not entirely user friendly, but our setup is not for regular consumers, so this manual method is entirely good enough.
Since build 2004 of windows 10 this no longer works. Microsoft are looking into why, but can't promise to fix it. The advice I have been given is to make a custom INF file to tell windows to automatically choose the right driver for this device. Custom INF files can't be simply written in a text editor and tested these days- they need to be accompanied by digital signatures, which mean that we need a whole windows development environment and a certificate signing setup (we don't have this today).
My actual question- is there a simple way to test an unsigned inf file? I have tried the method of starting windows in some special mode which allows unsigned drivers to be installed (required lots of fiddling with BIOS and arcane sequences of choices from rarely-seen menus) but the machine still complained when I tried to manually choose my custom inf file from the device manager. Maybe I just did that wrong?
/Mark
Continue reading...
We make a device with embedded linux which presents itself via USB as a multifunction device (USB mass storage and network device).
It uses a standard linux driver which presents vendor ID 1d6b (linux foundation) and PID 0104 (multifunction composite gadget) when it is plugged in to a USB port.
We have not had to make a custom INF file for this device, because we have for many years been able to tell windows machines (windows 7 and 10) manually via the device manager to use the built in windows RNDIS driver. This is not entirely user friendly, but our setup is not for regular consumers, so this manual method is entirely good enough.
Since build 2004 of windows 10 this no longer works. Microsoft are looking into why, but can't promise to fix it. The advice I have been given is to make a custom INF file to tell windows to automatically choose the right driver for this device. Custom INF files can't be simply written in a text editor and tested these days- they need to be accompanied by digital signatures, which mean that we need a whole windows development environment and a certificate signing setup (we don't have this today).
My actual question- is there a simple way to test an unsigned inf file? I have tried the method of starting windows in some special mode which allows unsigned drivers to be installed (required lots of fiddling with BIOS and arcane sequences of choices from rarely-seen menus) but the machine still complained when I tried to manually choose my custom inf file from the device manager. Maybe I just did that wrong?
/Mark
Continue reading...