Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Wireless pop-up window hangs in win ce 6.0
2 views
Skip to first unread message
sunsaro
Nov 19, 2009, 4:43:50 AM11/19/09
to
Hi All,
I newbie to WinCE. I'm working in WINDOWS CE 6.0. We are developing Our own
SDIO Stack and WLAN drivers.
My SDIO Stack is working fine and its able to initialize any wireless LAN
card or SD/MMC Memory card. When i connect my WLAN card,After initialization,
its starting dowloading the WLAN firmware to the card and After download to
the card, its able to detect the AP's in and around the circle and Displays
in the PoP-Up window properly. But the problem is, once the PoP-Up window
comes, I can able to access the PoP -Up window for 2 to 3 seconds only. After
that the PoP-Up window Hangs. But at the same time I can able to access the
other icons in the panel like Mydevice or Wordpad or any Game etc..
Please suggest me to come out of this problem.
Thanks in Advance.
Regards,
Saravana
I newbie to WinCE. I'm working in WINDOWS CE 6.0. We are developing Our own
SDIO Stack and WLAN drivers.
My SDIO Stack is working fine and its able to initialize any wireless LAN
card or SD/MMC Memory card. When i connect my WLAN card,After initialization,
its starting dowloading the WLAN firmware to the card and After download to
the card, its able to detect the AP's in and around the circle and Displays
in the PoP-Up window properly. But the problem is, once the PoP-Up window
comes, I can able to access the PoP -Up window for 2 to 3 seconds only. After
that the PoP-Up window Hangs. But at the same time I can able to access the
other icons in the panel like Mydevice or Wordpad or any Game etc..
Please suggest me to come out of this problem.
Thanks in Advance.
Regards,
Saravana
Luca Calligaris [eMVP]
Nov 20, 2009, 4:45:45 AM11/20/09
to
The wireless dialog uses heavilly the Wirleless Zero Configuration service
API (WZCQueryInterface, etc): the documentation about this functions is
someway scarce but there's a command line sample tool which you can
examinate to have some
hints about them (expecially the use of some structures) in
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\NETSAMP\WZCTOOL.
Those WZC* functions end up calling your driver to query/set various OID's.
The Wireless dialog code is implemented in
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\NETUI so you need to debug it to find
where it hangs and figure out what in your driver may be wrong. Obviously
you have to take in account even the fact that you're using a custom SDIO
stack also so some problems can -theoretically- come from it.
API (WZCQueryInterface, etc): the documentation about this functions is
someway scarce but there's a command line sample tool which you can
examinate to have some
hints about them (expecially the use of some structures) in
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\NETSAMP\WZCTOOL.
Those WZC* functions end up calling your driver to query/set various OID's.
The Wireless dialog code is implemented in
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\NETUI so you need to debug it to find
where it hangs and figure out what in your driver may be wrong. Obviously
you have to take in account even the fact that you're using a custom SDIO
stack also so some problems can -theoretically- come from it.
--
Luca Calligaris (MVP-Windows Embedded)
l.calliga...@eurotech.it.nospam
www.eurotech.it
"sunsaro" <u56304@uwe> ha scritto nel messaggio news:9f57701972616@uwe...
0 new messages