page_type | description | languages | products |
---|---|---|---|
Demonstrates the functionality of an NDIS miniport driver without requiring a physical network adapter. |
|
Oct 26, 2018 How to update WAN Miniport driver? There are two methods on how to update WAN Miniport driver on Windows 10 and other versions: Manual updating – This entails downloading and updating the WAN Miniport driver manually from the Windows update service. Before doing so, make sure that your computer connects to the net.
- Miniport, protocol, and filter drivers. The WDK for Windows 10, version 1709 supports header versioning. Header versioning makes sure that NDIS 6.80 drivers use the appropriate NDIS 6.80 data structures at compile time. Add the following compiler settings to the Visual Studio project for your driver: For a miniport driver, add NDIS680MINIPORT=1.
- Nov 26, 2018 NDIS notifies the NIC's miniport driver by calling the appropriate MiniportXxx function. The miniport driver sets up the transfer of data from the NIC and then indicates the presence of the received packet to bound higher-level drivers by calling the appropriate NdisXxx function. Connectionless and Connection-Oriented Miniport Drivers. NDIS supports miniport drivers for both connectionless.
The NDIS Virtual Miniport Driver sample illustrates the functionality of an NDIS miniport driver without requiring a physical network adapter.
Because the driver does not interact with any hardware, it makes it easier to understand the miniport interface and the usage of various NDIS functions without the clutter of hardware-specific code that is normally found in a fully functional driver. The driver can be installed either manually using the Add Hardware wizard as a root enumerated virtual miniport driver or on a virtual bus (like toaster bus).
This sample driver demonstrates an NDIS virtual miniport driver. If a single instance of the virtual miniport exists, it simply drops the send packets and completes the send operation successfully. If there are multiple virtual miniport instances, the instances behave as if they were multiple network interface cards (NICs) plugged into a single Ethernet hub. This 'hub' indicates the incoming send packets to all of the virtual miniport instances.
To test the miniport driver, install more than one miniport driver instance. You can repeat the installation to install more than one instance of the miniport.
[!NOTE]This sample provides an example of minimal driver intended for education purposes. The driver and its sample test programs are not intended for use in a production environment.
For more information on creating NDIS Miniport Drivers, see NDIS Miniport Drivers.
UPDATE: Api free download.
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.
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. 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.
Ndis Miniport Driver Windows 10 Free
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:
Disable Ndis Windows 10
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.
Ndis Sys Error Windows 10
It would be really nice if Microsoft could make it so that rndiscmp.inf shows up as compatible with USBVID_0525&PID_a4a2.