It can be done by using the WinCE WLAN APIs and scan for access points if known access points are found, connect to it using credentials that are stored on the device. It’s your most predictable option with the least risk. We recommend a workaround for you to implement your simple connection manager in your WEC application. The bug is when 2 preferred Wi-Fi profiles were created that will trigger a dead loop to connect those two profiles and that will leads to memory depleting then the device will be unusable after some time. If you are using the default connection manager on the device then you will notice this bug.You can use application debugging over Ethernet as an alternative. Removing Connection manager from the OS design will also remove ActiveSync and FileSync because of their dependency on Connection Manager.Import it using Regedit tool and save registry and then reboot. The connection manager can be disabled temporarily by using this registry. So, for this demo Connection Manager should not be included in the WinCE 7 image.
Some Native Wi-Fi APIs return "ERROR_ACCESS_DENIED" if the Connection Manager is included in the OS design.You can refer Native Wi-Fi APIs from here. This demo uses Native Wi-Fi APIs to configure the wireless network. Windows CE 7 provides Wi-Fi configuration support via Native Wi-Fi automatic configuration component and replaces the previous Windows Zero Configuration (WZC) Wi-Fi stack in Windows Embedded CE 6.0 R3. If this is not the information you are looking for, please, refer to the Wi-Fi Connectivity with Toradex’s Computer on Module (CoM) article for more Wi-Fi related information. This article shows how to connect to a Wi-Fi network from the user application using Windows CE.
0 kommentar(er)
