UPDATE:
Microsoft Windows Mobile Device Center 6.1 Driver for Windows Vista (64-bit) This new version of the Windows Mobile Device Center contains key improvements and new features to support Windows Mobile 6 devices.
I've done some more poking around and have found a few possible 'better' solutions.
Garmin nuvi 200 manual pdf. View and Download Garmin NUVI R NVI 200 setup manual online. Graco GPS Receiver User Manual. NUVI R NVI 200 GPS pdf manual download. Also for: Nuvi 205, Nuvi 205t, Nuvi 255, Nuvi 260, Nuvi 250 - automotive gps receiver, Nuvi 270 - automotive gps receiver, Nuvi 200 series. View and Download Garmin Nuvi 200 setup manual online. Nuvi 200 Car Navigation system pdf manual download. Also for: Nuvi 250, Nuvi 270.
First, some more insight: The Linux rndis gadget function has USB class of 2 and subclass of 2, which matches 'USBClass_02&SubClass_02' in the usbser.inf file. This is why for some people, their device is initially detected as a COM port instead of RNDIS.
Solution 1: If you are one of the people that found this because your device is showing up as a COM port instead of RNDIS, you may be able to get away using the RNDIS 5.1 driver. Find your device under Ports (COM & LTP) in Device Manager. Right-click it and select Update Driver Software.., then Browse my computer for driver software and then Let me pick from a list of device drivers on my computer and finally choose Remote NDIS Compatible Device. This should install the Microsoft RNDIS 5.1 driver (shows 'Acer' as the manufacturer). If this works great. If it causes Network and Settings and other network related things to lock up, then you need the RNDIS 6.0 driver instead. Try one of the other solutions.
Solution 2: If you have control over the RNDIS device and it runs Linux (i.e. BeagleBone), you can tweak the driver to get along with Windows better. For example, if you have a 3.16 kernel or newer, you can setup your gadget using configfs and include os descriptors. Face recognition software for old photos. This is actually what I ended up doing for my case. You can find my fully documented script here. The key was specifying the compatible and subcompatible ids so that it matches 'USBMS_COMP_RNDIS&MS_SUBCOMP_5162001' in rndiscmp.inf. This causes the Microsoft RNDIS 6.0 driver to be installed for this device. With this driver, I have not seen the same lockup as I have with the 5.1 (Acer) driver. I also changed the vendor and product ids so that it wouldn't match the 'Acer' driver.
Solution 3: If the RNDIS 5.1 (Acer) driver is causing problems and you can't modify the remote device, then you can reboot into a mode that allows you to install unsigned drivers. The you can install this unsigned linux.inf file. However, if you reboot without enabling unsigned drivers again, Windows will not load the driver anymore. For a more permanent solution, you could self-sign that .inf file.
Solution 4: This one is for Microsoft (and better than the suggestion below).. Add 'USBClass_02&SubClass_02&Prot_FF' to rndiscmp.inf.
ORIGINAL MESSAGE:
Here is the workaround that I came up with for my particular case. Assuming your device has the same USB Vendor and Product ID's it should work for you. If not, you can modify the .inf file (see link) accordingly.
It would be really nice if Microsoft could make it so that rndiscmp.inf shows up as compatible with USBVID_0525&PID_a4a2.
Voiding how exactly?
It voids volume licensing and associated warranties -- mostly for corporate-owned Windows installations, though.
Loading drivers from external sources is a pretty common occurrence pretty much everywhere, isn't it?
I am not familiar with any normal cases where one installs a driver that didn't come from either Windows Update or a manufacturer's disk, and when it comes on a disk it's an installer and not the pure
.sys
and .inf
files.My worry is that there are a lot of cases where taking official Windows driver files from one PC and manually installing them on another can leave you in a bad state:
Download Win 10 64-bit
- If the version that you copy has had a Windows Update applied to it that the other files on the destination PC don't have
- If the normal driver installer does some extra config that you don't do yourself (e.g. add registry keys)
- If the source driver is from a different version of Windows
- If the source driver isn't signed with a certificate that the destination can verify (in that case you need to boot into safe mode with the driver verifier disabled).
Rndis Download Win 10 64 Bit
It doesn't necessarily have to be the official Microsoft one, just something compatible.
Windows 10 Rndis Not Working
That's a good point; If we could find a third-party driver that had a publically-available installer, that should be fine. But we'd need to make sure that it is from a trusted vendor and is actively maintained, to make sure that there aren't any incompatibilities. And generally, I'm not sure that I would be willing to install a driver that I got like this, so I think we'd still need a separate method for people that didn't trust our version.
Drivers for many devices with Qualcomm Atheros chipset, for example Allied Telesyn, Belkin, Cisco, D-Link, Gigabyte, HP, Linksys, Netgear, Proxim Orinoco, SMC, and more. Choose a driver version for AR5B125 and Windows 10 64bit. Atheros ar5b125 driver.