Hi all,

I am using WINCE 5.0 i am working on wireless Prism2 WLAN driver. Normally
when i downloaded image(nk.abf) on board and after that when i inserted
Wireless Compact Flash Card it ask for "Enter Driver name" when i given
"ISLP2NDS.DLL" name Then on Hyper Terminal it shows some msgs are comming and
after some time it will stop in taht msg the driver islp2nds.dll is LOADED
and after some seconds it is UNLOADED.

I don't know due to why it is unloaded driver. I read some posts in that
they written

Adding WZC support is done by adding the Wireless LAN (802.11)... item from
the catalog. All that will do, of course, is add support for it. The
second piece is a wireless LAN adapter that supports WZC. CE 5 includes
support for several: Cisco 350-series (PC Card), Intersil Prism2 (chipset,
usually PC Card), RNDIS (USB).

Is any body know how to add WZC in our BSP or in pbxml? and How it will work??

Thanks in advance

Swapnil

Re: How to add WZC? by Michel

Michel
Wed May 07 04:55:47 PDT 2008

For wireless configuration to work you need to add "Wireless LAN
(802.11) STA - Automatic Configuration and 802.1x" (SYSGEN_ETH_80211) to
your platform and do a "sysgen".

What you are seeing is just the behavior of an unsupported card. The
driver "ISLP2NDS.DLL" doesn't know how to handle your card that's why it
is unloading. When you insert your card the PCMCIA driver investigates
the card and gets some ID's from it that identify the type of card. The
PCMCIA bus driver then searches the registry to see if a driver is
registered that can handle that type of card. In your system it isn't,
that's why it is showing you the box to "enter a driver". You then enter
a driver name, but that driver apparently doesn't know how to handle the
card. You need the correct driver for that card. Try asking the
manufacturer of the card for a Windows CE driver.


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Swapnil Manglekar wrote:
> Hi all,
>
> I am using WINCE 5.0 i am working on wireless Prism2 WLAN driver. Normally
> when i downloaded image(nk.abf) on board and after that when i inserted
> Wireless Compact Flash Card it ask for "Enter Driver name" when i given
> "ISLP2NDS.DLL" name Then on Hyper Terminal it shows some msgs are comming and
> after some time it will stop in taht msg the driver islp2nds.dll is LOADED
> and after some seconds it is UNLOADED.
>
> I don't know due to why it is unloaded driver. I read some posts in that
> they written
>
> Adding WZC support is done by adding the Wireless LAN (802.11)... item from
> the catalog. All that will do, of course, is add support for it. The
> second piece is a wireless LAN adapter that supports WZC. CE 5 includes
> support for several: Cisco 350-series (PC Card), Intersil Prism2 (chipset,
> usually PC Card), RNDIS (USB).
>
> Is any body know how to add WZC in our BSP or in pbxml? and How it will work??
>
> Thanks in advance
>
> Swapnil

Re: How to add WZC? by SwapnilManglekar

SwapnilManglekar
Wed May 07 06:22:01 PDT 2008

Thank you for reply Michel,

already I have added "Wireless LAN (802.11) STA - Automatic Configuration
and 802.1x" in my platform. And i also get the

GetCardCRC: CRC = 7ea7
CreateDeviceID _-IEEE_802.11_Wireless_LAN/PC_Card-7EA7 done
Manufacturer = _
Product Name = IEEE_802.11_Wireless_LAN/PC_Card

and after some time

ActivateDeviceEx('Drivers\PCMCIA\_-IEEE_802.11_Wireless_LAN/PC_Card-7EA7')
failed 110
>>> Loading module islp2nds.dll at address 0x036D0000-0x037F7000 (RW data
at 0x01F0F000-0x01F97C4E)

******Loaded symbols for ISLP2NDS.DLL *********

GetDhcpLease(DM90002): failed badly!
==>NdisInitializeWrapper
<==NdisInitializeWrapper
==>NdisMRegisterMiniport: NdisWrapperHandle 00053DF0
==>ndisRegisterMiniportDriver: NdisWrapperHandle 00053DF0
<==ndisRegisterMiniportDriver: MiniBlock 00053E60
NdisMRegisterMiniport: MiniBlock 00053E60
>>> Loading module oneex.dll at address 0x038A0000-0x038EA000 (RW data at
0x01F9C000-0x01F9F9DC)

*****Loaded symbols for ONEEX.DLL ********

>>> Loading module wzcsapi.dll at address 0x03990000-0x03997000 (RW data at
0x01FAB000-0x01FAB494)

******Loaded symbols for WZCSAPI.DLL **********

>>> Loading module wlsvc.dll at address 0x038F0000-0x0392F000 (RW data at
0x01FA1000-0x01FA179C)

*******Loaded symbols for WLSVC.DLL ************

<==NdisMRegisterMiniport: MiniBlock 00053E60, Status 0

ndisMInitializeAdapter: Miniport 00054DB0,
==>ndisQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60
<==ndisQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60, rc 1
==>NdisMSetAttributesEx: Miniport 00054DB0
(+) STATUS PDCardGetWindow()
In CPcmciaCardSocket* GetSocket()
GetDhcpLease(DM90002): failed badly!
(+)CPcmciaCardSocket* ObjectBySocket
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F7E0>
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F834>
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F8F0>
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F8A4>
(-)CPcmciaCardSocket* ObjectBySocket
if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
(+) STATUS PDCardGetWindow()
In CPcmciaCardSocket* GetSocket()
(+)CPcmciaCardSocket* ObjectBySocket
(-)CPcmciaCardSocket* ObjectBySocket
if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
CPcmciaWindows::CardMapWindowPhysical:RsourceRequest(abcd0001,300,40 )fail!!!
NDIS: ERROR-INdisGetPcmciaWindow failed 0xc000009a
>>> Loading module rsaenh.dll at address 0x01E70000-0x01E99000

*****************Loaded RSAENH.DLL**************, no matching symbolic
information found.

(+) STATUS PDCardGetWindow()
In CPcmciaCardSocket* GetSocket()
(+)CPcmciaCardSocket* ObjectBySocket
(-)CPcmciaCardSocket* ObjectBySocket
if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
==>NdisMDeregisterAdapterShutdownHandler: Miniport 00054DB0
<==NdisMDeregisterAdapterShutdownHandler: Miniport 00054DB0
***NDIS*** (b, 2078)
INIT FAILURE: Dequeueing the miniport from the driver block.
==>ndisDeQueueMiniportOnDriver, Miniport 00054DB0, MiniBlock 00053E60
<==ndisDeQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60
***NDIS*** (b, 2105)
<<< Unloading module rsaenh.dll at address 0x01E70000-0x01E99000

****************Unloaded symbols RSAENH.DLL ****************

ONEEX:: OneExReadGlobalRegistryParams: Error in RegQueryValueEx for
cwszSupplicantMode, 2, InfoSize=4
ONEEX:: OneExReadGlobalRegistryParams: Error in RegQueryValueEx for
cwszAuthMode, 2, InfoSize=4
ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3089]: **
Trying to lock 01F9F7A0:01F9F7E0 **
ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3089:] ++
Locked 01F9F7A0:01F9F7E0
INIT FAILURE: Dereferencing the miniport block.
ndisDereferenceMiniport:Miniport 00054DB0, Ref = 0
==>ndisMUnload: DriverObject 0004F120
ndisMUnload: MiniBlock 00053E60
<==ndisMUnload: DriverObject 0004F120, MiniBlock 00053E60
ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3094]: --
Unlocking 01F9F7A0:01F9F7E0
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F750>
ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F974>
<<< Unloading module islp2nds.dll at address 0x036D0000-0x037F7000 (RW data
at 0x01F0F000-0x01F97C4E)

*******Unloaded symbols ISLP2NDS.DLL********

I have also used WZC tool i have added into my project an run from command
line in WINCE i got

\windows> wzctool
trying to read and configure wireless settings
security warning: storing encryption key in clear text is volunerable to
attack

but nothing any action on WLAN Card. It doesnot show any popup menu also.

It is problem of any registry entry or anything??

Best Regards

Swapnil

"Michel Verhagen (eMVP)" wrote:

> For wireless configuration to work you need to add "Wireless LAN
> (802.11) STA - Automatic Configuration and 802.1x" (SYSGEN_ETH_80211) to
> your platform and do a "sysgen".
>
> What you are seeing is just the behavior of an unsupported card. The
> driver "ISLP2NDS.DLL" doesn't know how to handle your card that's why it
> is unloading. When you insert your card the PCMCIA driver investigates
> the card and gets some ID's from it that identify the type of card. The
> PCMCIA bus driver then searches the registry to see if a driver is
> registered that can handle that type of card. In your system it isn't,
> that's why it is showing you the box to "enter a driver". You then enter
> a driver name, but that driver apparently doesn't know how to handle the
> card. You need the correct driver for that card. Try asking the
> manufacturer of the card for a Windows CE driver.
>
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog: http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.


Re: How to add WZC? by Paul

Paul
Wed May 07 08:41:30 PDT 2008

How confident are you that your PCMCIA driver is working? How confident are
you that you actually have a Prism2 card? What brand and model is it?

Paul T.

"Swapnil Manglekar" <SwapnilManglekar@discussions.microsoft.com> wrote in
message news:9ADFDC48-7B88-4B65-AF69-A552F4BF5379@microsoft.com...
> Thank you for reply Michel,
>
> already I have added "Wireless LAN (802.11) STA - Automatic Configuration
> and 802.1x" in my platform. And i also get the
>
> GetCardCRC: CRC = 7ea7
> CreateDeviceID _-IEEE_802.11_Wireless_LAN/PC_Card-7EA7 done
> Manufacturer = _
> Product Name = IEEE_802.11_Wireless_LAN/PC_Card
>
> and after some time
>
> ActivateDeviceEx('Drivers\PCMCIA\_-IEEE_802.11_Wireless_LAN/PC_Card-7EA7')
> failed 110
> >>> Loading module islp2nds.dll at address 0x036D0000-0x037F7000 (RW data
> at 0x01F0F000-0x01F97C4E)
>
> ******Loaded symbols for ISLP2NDS.DLL *********
>
> GetDhcpLease(DM90002): failed badly!
> ==>NdisInitializeWrapper
> <==NdisInitializeWrapper
> ==>NdisMRegisterMiniport: NdisWrapperHandle 00053DF0
> ==>ndisRegisterMiniportDriver: NdisWrapperHandle 00053DF0
> <==ndisRegisterMiniportDriver: MiniBlock 00053E60
> NdisMRegisterMiniport: MiniBlock 00053E60
> >>> Loading module oneex.dll at address 0x038A0000-0x038EA000 (RW data at
> 0x01F9C000-0x01F9F9DC)
>
> *****Loaded symbols for ONEEX.DLL ********
>
> >>> Loading module wzcsapi.dll at address 0x03990000-0x03997000 (RW data
> >>> at
> 0x01FAB000-0x01FAB494)
>
> ******Loaded symbols for WZCSAPI.DLL **********
>
> >>> Loading module wlsvc.dll at address 0x038F0000-0x0392F000 (RW data at
> 0x01FA1000-0x01FA179C)
>
> *******Loaded symbols for WLSVC.DLL ************
>
> <==NdisMRegisterMiniport: MiniBlock 00053E60, Status 0
>
> ndisMInitializeAdapter: Miniport 00054DB0,
> ==>ndisQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60
> <==ndisQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60, rc 1
> ==>NdisMSetAttributesEx: Miniport 00054DB0
> (+) STATUS PDCardGetWindow()
> In CPcmciaCardSocket* GetSocket()
> GetDhcpLease(DM90002): failed badly!
> (+)CPcmciaCardSocket* ObjectBySocket
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F7E0>
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F834>
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F8F0>
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F8A4>
> (-)CPcmciaCardSocket* ObjectBySocket
> if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
> (+) STATUS PDCardGetWindow()
> In CPcmciaCardSocket* GetSocket()
> (+)CPcmciaCardSocket* ObjectBySocket
> (-)CPcmciaCardSocket* ObjectBySocket
> if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
> CPcmciaWindows::CardMapWindowPhysical:RsourceRequest(abcd0001,300,40 )fail!!!
> NDIS: ERROR-INdisGetPcmciaWindow failed 0xc000009a
> >>> Loading module rsaenh.dll at address 0x01E70000-0x01E99000
>
> *****************Loaded RSAENH.DLL**************, no matching symbolic
> information found.
>
> (+) STATUS PDCardGetWindow()
> In CPcmciaCardSocket* GetSocket()
> (+)CPcmciaCardSocket* ObjectBySocket
> (-)CPcmciaCardSocket* ObjectBySocket
> if( pSocket != NULL ) (-) STATUS PDCardGetWindow()
> ==>NdisMDeregisterAdapterShutdownHandler: Miniport 00054DB0
> <==NdisMDeregisterAdapterShutdownHandler: Miniport 00054DB0
> ***NDIS*** (b, 2078)
> INIT FAILURE: Dequeueing the miniport from the driver block.
> ==>ndisDeQueueMiniportOnDriver, Miniport 00054DB0, MiniBlock 00053E60
> <==ndisDeQueueMiniportOnDriver: Miniport 00054DB0, MiniBlock 00053E60
> ***NDIS*** (b, 2105)
> <<< Unloading module rsaenh.dll at address 0x01E70000-0x01E99000
>
> ****************Unloaded symbols RSAENH.DLL ****************
>
> ONEEX:: OneExReadGlobalRegistryParams: Error in RegQueryValueEx for
> cwszSupplicantMode, 2, InfoSize=4
> ONEEX:: OneExReadGlobalRegistryParams: Error in RegQueryValueEx for
> cwszAuthMode, 2, InfoSize=4
> ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3089]: **
> Trying to lock 01F9F7A0:01F9F7E0 **
> ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3089:] ++
> Locked 01F9F7A0:01F9F7E0
> INIT FAILURE: Dereferencing the miniport block.
> ndisDereferenceMiniport:Miniport 00054DB0, Ref = 0
> ==>ndisMUnload: DriverObject 0004F120
> ndisMUnload: MiniBlock 00053E60
> <==ndisMUnload: DriverObject 0004F120, MiniBlock 00053E60
> ONEEX:: ThrdId[c7e9a192] Fn[OneExReadGlobalRegistryParams]:Ln[3094]: --
> Unlocking 01F9F7A0:01F9F7E0
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F750>
> ONEEX:: InitializeRWLock: SUCCESS -- created Lock <01F9F974>
> <<< Unloading module islp2nds.dll at address 0x036D0000-0x037F7000 (RW
> data
> at 0x01F0F000-0x01F97C4E)
>
> *******Unloaded symbols ISLP2NDS.DLL********
>
> I have also used WZC tool i have added into my project an run from command
> line in WINCE i got
>
> \windows> wzctool
> trying to read and configure wireless settings
> security warning: storing encryption key in clear text is volunerable to
> attack
>
> but nothing any action on WLAN Card. It doesnot show any popup menu also.
>
> It is problem of any registry entry or anything??
>
> Best Regards
>
> Swapnil
>
> "Michel Verhagen (eMVP)" wrote:
>
>> For wireless configuration to work you need to add "Wireless LAN
>> (802.11) STA - Automatic Configuration and 802.1x" (SYSGEN_ETH_80211) to
>> your platform and do a "sysgen".
>>
>> What you are seeing is just the behavior of an unsupported card. The
>> driver "ISLP2NDS.DLL" doesn't know how to handle your card that's why it
>> is unloading. When you insert your card the PCMCIA driver investi