![remote ndis driver windows 10 not working remote ndis driver windows 10 not working](http://www.sy.cz/res/archive/006/000681.jpg)
So I take this at face value and I can't rebut it. Hey - I've been lucky and just had to manage one INF file for 10 years,
Remote ndis driver windows 10 not working drivers#
Now, from the firmware engineer, he explained that the composite driver sits under the regular drivers, and the regular drivers have no idea that they are any different than usual. I assume it's because it's a composite device. Our older devices, but that no longer works for this device. It shows up as a COM port and a network interface by default, and we want the device to appear as a USB device and a network interface.
![remote ndis driver windows 10 not working remote ndis driver windows 10 not working](https://www.thewindowsclub.com/wp-content/uploads/2019/08/USB-tethering-Settings-on-Phone.png)
With this composite device, it is not longer enumerating on the USB bus. We also want to expose the network interface for the device so that they end user can also do some other 'stuff' that we want to allow them to do. Since this device is physically connected via USB, we want the user experience of USB
![remote ndis driver windows 10 not working remote ndis driver windows 10 not working](https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/94/2806.3.png)
We have an application that lists our devices that have enumerated on the USB bus so the end user can select which device to work with. What details do I need to provide to get to an answer on this? I work for the owner of the hardware, the software, and the firmware. In his mind it's a Windows driver installation deal, and I am inclined And since the firmware developer is a Linux guy (and virulently anti-Microsoft), he's proud to call hisĮfforts complete based upon a successful test on Linux and a demonstration of the COM port, USB port, and Network access on the Windows platform (via an installation/driver workaround). The device itself is exposed to the USB host through a standard composite device implementation that works perfectly fine when Linux is the host. The bigger issue is as a hardware manufacturer I don't want to be telling people to go grab some other company's driver to make our device work. On all platforms, etc., but that's all a moot point. Yes, this may not be something is recommended, works May be by accident, but hey, worse things have happened. Well, the selection of the modem driver as being a 'hack' was mainly my opinion, but Windows clearly supports it - because, you know, it works.