Hi, all there
I dynamically load my NDIS protocol driver from app by CreateService.
But then it seems it doesn’t not bind onto Miniport driver. What I should
do to make them bound?
Best Regards
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
----- Original Message -----
From:
To: NT Developers Interest List
Sent: Tuesday, April 24, 2001 4:48 AM
Subject: [ntdev] dynamically binding miniport and protocol driver
> Hi, all there
> I dynamically load my NDIS protocol driver from app by CreateService.
> But then it seems it doesn’t not bind onto Miniport driver. What I should
> do to make them bound?
>
The NDIS binding engine does not know about the desired binding of
dynamically loaded NDIS protocols. How could it? You have bypassed it.
Consequently, NDIS will NOT call your BindAdapter handler. You must do
that yourself (actually, you must call NdisOpenAdapter yourself…).
To call NdisOpenAdapter yourself you must deternine the “Adapter Name” that
you must pass to NdisOpenAdapter. On Windows 2000 you can use the SNetCfg
API to find this.
Good luck,
Thomas F. Divine
PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - NDIS Intermediate - TDI Client
http: - http:
> Best Regards
>
> Kevin Liang
> Accton Technology Corporation
> Shanghai R&D Division
> =========================
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</http:></http:>