Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

Unlike connecting physical devices, connecting emulated devices requires an extra step.

Note:
If you have Visual Studio 2005 and either the Windows Mobile 5.0 Pocket PC SDK or the Windows Mobile 5.0 Smartphone SDK installed on your workstation, then by default, Device Emulator Manager is installed at the following location: C:\Program Files\Microsoft Device Emulator\1.0\dvcemumanager.exe.

To connect an emulated device

  1. Start Device Emulator Manager.

    Device Emulator Manager presents you with a hierarchical list of available emulator images to choose from.

  2. Right-click the emulator image you want, and then click Connect.

    When Device Emulator Manager connects an emulated device, the emulator image for that device loads and runs, but the connection process does not automatically proceed to the next stage and make a logical connection with ActiveSync . For that, you need to perform the next step.

  3. In the list of emulator images, right-click the entry for the emulator image that you just "connected," and then click Cradle.

    ActiveSync detects the emulated device, and establishes its own kind of connection with it.

  4. When ActiveSync's Synchronization Setup Wizardappears, click Cancel.

    ActiveSync establishes the minimal "Guest" connection with the emulated device. Security Configuration Manager Powertoy for Windows Mobile then detects the connected device as "Microsoft DeviceEmulator," queries it for security configuration details, and then populates it's application window with them.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.