How to Implement a Wireless Configuration UI for a Thin Client
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
In Windows Embedded CE 6.0, the wireless configuration user interface (UI) is a dialog box that can be accessed from the network connection status UI, also known as Ethman. Ethman is a sample application that can be accessed from an icon in the notification area and indicates network information, such as IP address and wireless network availability.
The notification area contains icons that users can quickly reference for information and is located on the taskbar of the thin client shell.
You can implement a custom wireless configuration UI that you can access within Ethman.
Hardware and Software Assumptions
- The target device supports wireless network connections.
- You have a wireless network card that is compatible with the LAN driver that is included in the operating system (OS) design.
- You have an 802.1X wireless network to which the target device can connect.
Steps
| Step | Topic |
|---|---|
1. To learn about the functionality involved in implementing a wireless configuration UI, review information about wireless networking and automatic configuration. |
|
2. Use the Windows Embedded CE OS Design Wizard to create an OS design that includes the Windows Embedded CE Standard Shell. |
Creating an OS Design with the Windows Embedded CE OS Design Wizard |
3. Customize the OS design by including Catalog items that support wireless networks and networking UI. |
Adding Wireless Capability to a Thin Client |
4. Customize the wireless configuration UI. |
|
5. If you have created a new wireless configuration UI module, add the newly created module to the OS design. |
|
6. Choose a Debug or Release configuration to target when Platform Builder builds the OS design into a run-time image. To use the kernel debugger, make sure that support for the kernel debugger is enabled. |
|
7. If you expect the size of either the debug or the release run-time image to exceed 32 MB, enable support for a large run-time image in the settings for the OS design. .gif "Bb905614.note(en-US,WinEmbedded.60).gif") Note:
Debug run-time images are typically larger than release run-time images. If you choose a debug configuration and the OS design contains many features, it is likely that the size of the run-time image will exceed 32 MB.
|
|
8. Build the OS design into a run-time image. To rebuild the code that you customized in step 4, on the build menu, choose Advanced Build Commands, and then choose Build and Sysgen. |
|
9. In the Output window, on the Output tab, verify that the build contains no errors. |
|
10. Choose a download service appropriate for the connection hardware. The download service will download a run-time image to the target device. |
|
11. Set up and configure the connection hardware required for the download service. That hardware connects the target device to the development workstation, on which Platform Builder is installed. Examples of connection hardware include cables, a hub, or Ethernet network adapters. |
|
12. If you selected Serial Download Service in step 5, configure the HyperTerminal terminal emulation application to display the serial debug output from the serial port on the target device. This configuration requires a null-modem cable connected to a serial port, such as COM1. |
|
13. Turn on the target device so that it becomes active on the Ethernet network or over the serial connection, and Platform Builder can discover it. |
Not applicable |
14. Configure the connection to the target device. Choose the appropriate topic based on whether the development workstation and the target device are connected by an Ethernet network or a serial port connection. |
|
15. Download the run-time image to the target device through the configured connection. |
|
16. Attach the appropriate wireless network adapter to the standard development board. |
Not applicable |
17. Turn on the target device and test the wireless configuration UI. |
Diagnosing Connectivity Problems using the Network Connection Status UI |
See Also
Concepts
Other Resources
Automatic Configuration Subsystem
Automatic Configuration Samples