As with my replies on Sunday and yesterday, there are supported, documented ways to develop NDIS IM drivers. Is there a reason that you insist on using unsupported methods?
NDIS hooking drivers have been known to cause problems, mostly with interactions with other products and bugchecks. The author of such drivers is usually not aware of the difficulties that their non-standard driver has caused. Furthermore, it’s likely to have real problems in future stacks when inserted between an NDIS 6 miniport and a NDIS 6 transport.
Any development using the hooking scheme is likely to cause problems in the present and possibly cease to work in the future.
Bryan S. Burgin
xxxxx@microsoft.com
This posting is provided “AS IS” with no warranties, and confers no rights.
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Egemen Tas
Sent: Wednesday, December 01, 2004 4:19 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Prototype of ndisMSwapOpenHandlers and ndisMRestoreOpenHandlers functions
Hello?all,
?
While doing research on NDIS, I have seen two functions for which I have found no documentation.
?
Does anybody know the function prototypes of the following undocumented NDIS functions:
?
ndisMSwapOpenHandlers: Which swaps the Send handlers of a protocol with the bogus ones(which always return error) in case of Media disconnect and reset.
ndisMRestoreOpenHandlers:Which restores the handlers previously swapped by ndisMSwapOpenHandlers.
?
I have also found that? there is a protocol named HOOKPROC which is used to get a handle to current?protocol chain to dynamically hook NDIS?. Do you know which software may possibly initiate?this attempt?
?
Thanks in advance,
Egemen Tas
http://www.modemwall.com
?
?
?
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com