Discussion:
error implementing Dot11ExtNicSpecificExtension() in IHV Extenstion DLL on Native Wifi Vista
(too old to reply)
Albert
2007-05-09 15:07:08 UTC
Permalink
Raw Message
Target Platform : Vista
Application: IHV Extenstion DLL based on Native Wifi Arrchitecture
WinDDK 600

Hi All,

We are developing IHV Extension dll for WLAN Adapter to implement
properiatary OIDs as per the Native Wi-Fi architecture.

I have started with the sample code that comes with WinDDK 6000. I am
able to load the IHV Extension DLL and IHV UI with our WLAN Adapter.

To send the properiatery OID request to the Driver I have written a
MyApp.exe written on top of WLAN ACM APIS which call the
WLANIhvControl() API which in turn calls the Dot11ExtIhvControl
implemented in MyIHVExtension.dll.

In Dot11ExtIhvControl of MyIHVExtension.dll calls the Extensability
funtion Dot11ExtNicSpecificExtension() API

Dot11ExtNicSpecificExtension() API returns error code 23 which is Data
Error (cyclic redundancy check). what are the reasons of getting this
error and what is the fix?

Also there is no call received in miniport driver so it seems MSM
performs some check on the input buffer and output buffer returns
error code 23. Is there any particular syntax/structure/padding for
passing the input and output buffer pointer?

Any help in this regard will be highly appreciated. Its really very
urgent.

Is this the correct approach? Is there any other way to implement
properietery OIDS?

Thanks & regards,
Albert
Bruno van Dooren
2007-05-10 06:31:22 UTC
Permalink
Raw Message
Post by Albert
We are developing IHV Extension dll for WLAN Adapter to implement
properiatary OIDs as per the Native Wi-Fi architecture.
...
Is this the correct approach? Is there any other way to implement
properietery OIDS?
I really have no idea, but you are asking in the wrong group.
This group deals with language issues or compiler / linker issues and stuff
like that.
Yours is a platform problem to which I don't know the answer.

Mosey over to one of the platformsdk groups, or perhaps the device driver
groups.
Those guys are much more likely to be able to help you.
--
Kind regards,
Bruno van Dooren MVP - VC++
http://msmvps.com/blogs/vanDooren
***@hotmail.com
Albert
2007-05-10 07:13:01 UTC
Permalink
Raw Message
On May 9, 11:31 pm, "Bruno van Dooren"
Post by Bruno van Dooren
Post by Albert
We are developing IHV Extension dll for WLAN Adapter to implement
properiatary OIDs as per the Native Wi-Fi architecture.
...
Is this the correct approach? Is there any other way to implement
properietery OIDS?
I really have no idea, but you are asking in the wrong group.
This group deals with language issues or compiler / linker issues and stuff
like that.
Yours is a platform problem to which I don't know the answer.
Mosey over to one of the platformsdk groups, or perhaps the device driver
groups.
Those guys are much more likely to be able to help you.
--
Kind regards,
Bruno van Dooren MVP - VC++
http://msmvps.com/blogs/vanDooren
Thanks bruno.. I will post it to relevant groups
dongjin suh
2011-07-21 02:20:41 UTC
Permalink
Raw Message
Hi,
I got the same problem that you had. I also got error code 23 in using WLanIhvControl()?
How did you solve this problem?
Any comment would help.
Thanks.

Dongjin
Post by Albert
Target Platform : Vista
Application: IHV Extenstion DLL based on Native Wifi Arrchitecture
WinDDK 600
Hi All,
We are developing IHV Extension dll for WLAN Adapter to implement
properiatary OIDs as per the Native Wi-Fi architecture.
I have started with the sample code that comes with WinDDK 6000. I am
able to load the IHV Extension DLL and IHV UI with our WLAN Adapter.
To send the properiatery OID request to the Driver I have written a
MyApp.exe written on top of WLAN ACM APIS which call the
WLANIhvControl() API which in turn calls the Dot11ExtIhvControl
implemented in MyIHVExtension.dll.
In Dot11ExtIhvControl of MyIHVExtension.dll calls the Extensability
funtion Dot11ExtNicSpecificExtension() API
Dot11ExtNicSpecificExtension() API returns error code 23 which is Data
Error (cyclic redundancy check). what are the reasons of getting this
error and what is the fix?
Also there is no call received in miniport driver so it seems MSM
performs some check on the input buffer and output buffer returns
error code 23. Is there any particular syntax/structure/padding for
passing the input and output buffer pointer?
Any help in this regard will be highly appreciated. Its really very
urgent.
Is this the correct approach? Is there any other way to implement
properietery OIDS?
Thanks & regards,
Albert
Post by Bruno van Dooren
I really have no idea, but you are asking in the wrong group.
This group deals with language issues or compiler / linker issues and stuff
like that.
Yours is a platform problem to which I don't know the answer.
Mosey over to one of the platformsdk groups, or perhaps the device driver
groups.
Those guys are much more likely to be able to help you.
--
Kind regards,
Bruno van Dooren MVP - VC++
http://msmvps.com/blogs/vanDooren
Post by Albert
Thanks bruno.. I will post it to relevant groups
Loading...