Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

OSR Seminars


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 1  
09 Feb 18 13:10
Shashank Ram
xxxxxx@gmail.com
Join Date: 21 Sep 2016
Posts To This List: 47
ndis im driver and Windows 10

Hi, I have an NDIS 6.40 IM MUX driver that works perfectly on Win8.1 I am seeing a bunch of different issues while trying to get this work on Windows 10 (Server 2016) version 1607. I have tried the following: 1. With NDIS 6.50, the registry entries are not setup when my driver tries to read the bindings information, and hence the protocol bind function fails. As a result the miniport adapters are in disabled state. The problem goes away on a reboot but this breaks our installation workflow. 2. With NDIS 6.60, as soon as the MINIPORT_INITIALIZE function completes, the MINIPORT_HALT routine gets called by NDIS, causing the miniports to be destroyed. I am not sure what needs to be done to be able to create miniports succesfully on Server 2016 (Windows 10). Looks like there are some changes in the netcfg layer, causing NDIS IM driver installation to fail on Windows 10.
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 15:34.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license