Is it possible to call NdisOpenAdapter after create a driver object in Ndis Protocol Driver DriverEntry?
If not Why?
craiglei
The short answer is in the WIndows XP DDK documentation for NdisOpenAdapter:
“NDIS no longer supports calling NdisOpenAdapter from the DriverEntry function, which was an option available to legacy (V3.0) protocols. NDIS no longer supports V3.0 protocols. NDIS fails any attempt to call NdisOpenAdapter outside the context of ProtocolBindAdapter.”
The long answer is that at least through Windows XP NDIS does not enforce this restriction. However, we have been warned. 
Regards,
Thomas F. Divine
PCAUSA - Tools & Resources For Network Software Developers
NDIS Protocol/Intermediate/Hooking - TDI Client/Filter
http: - http:
“craiglei” wrote in message news:xxxxx@ntdev…
Is it possible to call NdisOpenAdapter after create a driver object in Ndis Protocol Driver DriverEntry?
If not Why?
craiglei</http:></http:>
Yes, but this will result in NDIS3 obsolete protocol which is not unloadable and does not allow the NIC drivers to be unloaded.
NDIS4 and later protocols call NdisOpenAdapter from BindAdapter callback only.
Max
----- Original Message -----
From: craiglei
To: NT Developers Interest List
Sent: Monday, June 03, 2002 12:35 PM
Subject: [ntdev] Is it possible to call NdisOpenAdapter in Ndis Protocol Driver DriverEntry?
Is it possible to call NdisOpenAdapter after create a driver object in Ndis Protocol Driver DriverEntry?
If not Why?
craiglei
b??.??????+i???{.n???wZnV???h??{]z??b?(?(