In Windows 7, or Windows 10? In Windows 7 & 8.1, if you go to Device Manager, then go down the list to 'Universal Serial Bus Devices' it will be listed there. Note that it will NOT be listed until: MotoTRBO is running, the radio is turned ON, and the radio is connected to the computer. Sep 18, 2015 Windows 10 vs Remote NDIS - Ethernet USB/Gadget not recognized Hi, I used to connect my ODROID U3 with Ubuntu via USB to Windows 7 and Windows 8 via remote ndis, which shows up in the device manager as 'Linux USB Ethernet/RNDIS Gadget' and results in a new LAN connection. Nov 19, 2015 In Windows, start the Device. But you do get the USB Device Add or Device Fail sound, you may need to reinstall the MOTOTRBO Driver. To do this have a look at these two posts. Driver USB Windows. Related Posts. Leave a Comment. MOTOTRBO Driver; MOTOTRBO Capacity Max; Two new pages October (4) September (2). There's a MOTOTRBO solution that's perfect for you. Give productivity a boost. Distribute service orders to team members outside of your area. Connect to remote machines and operate them right from your radio. And get fast access to the functions you use most by customizing your device to fit your job. See how A safer place. If “MOTOTRBO Radio X” is not listed under Network Adapters (see 4) but you do get the USB Device Add or Device Fail sound, you may need to reinstall the MOTOTRBO Driver. To do this have a look at these two posts.
Scan performed on 4/25/2017, Computer: NEC PC-GV296VZGL - Windows 7 64 bit
Outdated or Corrupted drivers:8/20
Device/Driver | Status | Status Description | Updated By Scanner |
Motherboards | |||
Intel(R) Xeon(R) E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers - 0E71 | Corrupted By Mototrbo Radio | ||
Mice And Touchpads | |||
WheelMouse HID-compliant mouse | Corrupted By Mototrbo Radio | ||
Usb Devices | |||
Option nv Standard OpenHCD USB Host-controller | Outdated | ||
Texas Instruments Texas Instruments USB 3.0 eXtensible Host Controller - 0096 (Microsoft) | Up To Date and Functioning | ||
Sound Cards And Media Devices | |||
AVerMedia AVerMedia A373 MiniCard Dual DVB-T | Up To Date and Functioning | ||
IC Plus Unimodem Half-Duplex Audio Device | Up To Date and Functioning | ||
C-Media Standardgameport | Corrupted By Mototrbo Radio | ||
Network Cards | |||
Qualcomm Atheros Atheros AR8152/8158 PCI-E Fast Ethernet Controller (NDIS 6.20) | Up To Date and Functioning | ||
Keyboards | |||
Microsoft HID Keyboard | Corrupted By Mototrbo Radio | ||
Hard Disk Controller | |||
Intel(R) ICH9R/DO/DH 6 Port SATA AHCI Controller - 2922 | Outdated | ||
Others | |||
Texas Instruments Dispositivo compatible con HID | Corrupted By Mototrbo Radio | ||
Western Digital WD SES Device USB Device | Up To Date and Functioning | ||
ENE ENE CB-1410/851 Cardbus Controller | Corrupted By Mototrbo Radio | ||
Unibrain OHCI Compliant IEEE 1394 Host Controller | Up To Date and Functioning | ||
Cameras, Webcams And Scanners | |||
Canon Canon MP600R | Up To Date and Functioning | ||
Video Cards | |||
ATI RADEON X300 Series | Up To Date and Functioning | ||
Input Devices | |||
Microsoft HID-compliant system control device | Up To Date and Functioning | ||
Port Devices | |||
Mobile Connector Device Application Interface (COM12) | Up To Date and Functioning | ||
Monitors | |||
Sony Digital Flat Panel (1024x768) | Up To Date and Functioning | ||
Mobile Phones And Portable Devices | |||
Acer NOKIA | Up To Date and Functioning |
UPDATE:
I've done some more poking around and have found a few possible 'better' solutions.
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.
![Mototrbo Mototrbo](https://www.sjmradio.com/include/shared-images/motorola/mototrbo/apps/rbx-2.jpg)
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.
Mototrbo Driver Windows 10 Update
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. 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.
![Download Download](https://4.bp.blogspot.com/-QL2L_RPWl-A/Wp7M0j-wABI/AAAAAAAAC_E/Hz0V5x5liLwYYTQi0hS3uFY_cLquzf7ggCLcBGAs/s1600/4.jpg)
ORIGINAL MESSAGE:
Motorola Mototrbo Usb Driver
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.
Mototrbo Driver Windows 10 64 Bit
It would be really nice if Microsoft could make it so that rndiscmp.inf shows up as compatible with USBVID_0525&PID_a4a2.