Open Control Panel, choose Add Hardware, and then choose Next.
Choose Yes, I have already connected the hardware, and then choose Next.
From the Installed hardware list, select Add a new hardware device, and then choose Next.
Choose Install the hardware that I manually select from a list (Advanced), and then choose Next.
From the Common hardware types list, select Network adapters, and then choose Next.
From the Manufacturer list, select Microsoft.
From the Network Adapter list, select Microsoft Loopback Adapter, and then choose Next.
Choose Next, and then choose Finish.
To install the Microsoft Loopback Adapter in Microsoft Windows 2000
Open Control Panel, choose Add/Remove Hardware, and then choose Next.
Choose Add/Troubleshoot a device, and then choose Next.
From the Devices list, select Add a new device, and then choose Next.
Choose No, I want to select the hardware from a list, and then choose Next.
From the Hardware types list, select Network adapters, and then choose Next.
From the Manufacturers list, select Microsoft.
From the Network Adapter list, select Microsoft Loopback Adapter, and then choose Next.
Choose Next, and then choose Finish.
11.14. 为什么当模拟器使用了一个COM端口的时候不启动不了(黑屏)？
Symptom: When the Emulator image is starting up, it stays as a black screen forever. This happens when the Emulator is configured to use at least one COM port.
Cause: By default, the Emulator is not assigned a COM port but the user may change the configuration to assign a COM port to the Emulator. When a COM port assigned to the Emulator is used by ActiveSync or any other running application, the Emulator image loading will fail.
Workaround: Remove all of the COM ports assigned to the Emulator or change them to those not used by ActiveSync or any other running application. To remove or change the COM port configurations in Visual Studio .NET 2003, go to Tools/Options/Devices, choose an Emulator in the Devices window and click the Configure button.
11.15. 为什么Visual Studio .NET 2003的模拟器不能和eMbedded Visual Tools的模拟器同时使用？
Symptom: When the eMbedded Visual Tools (Platform Builder) Emulator is running, Visual Studio .NET 2003 Emulator deployment fails, and vice versa. Sometimes even after the Visual Studio .NET 2003 Emulator is closed, the eMbedded Visual Tools Emulator still does not work.
Cause: The Visual Studio .NET 2003 Emulator and the eMbedded Visual Tools Emulator internally use two different instances of Emulator.exe which are not compatible with each other. Because they share the same executable name and the exe is a single instance application, while Emulator.exe for eMbedded Visual Tools is running, the one for Visual Studio .NET 2003 cannot be started, and vice versa. Another issue is that when the Visual Studio .NET 2003 Emulator user interface is closed, emulator.exe does not close until the hosting Visual Studio IDE instance is closed. In that case, the eMbedded Visual Tools Emulator cannot be started even though there is no Emulator running visually.
Workaround: Do not use the two Emulators at the same time. If an Emulator cannot be started, check the Task Manager and close any running emulator.exe processes.
11.16. 为什么没有ActiveSync连接的时候不能通过TCP连接向设备发布程序？Symptom: When a device does not have an ActiveSync connection with the Visual Studio machine but has a valid TCP connection, deployment does not work.
Cause: ConMan relies on an ActiveSync connection to perform some initial settings between the Visual Studio machine and the device. If no ActiveSync connection is available, the setting will have to be performed manually.
Workaround: Use the separately provided Keyman tool to perform the initial device settings with the following steps:
Choose the correct flavor of Keyman.exe (e.g. ARMV4 or SH4, etc) and place it on the device. Launch Keyman and select "FILE->CONNECT". Keyman is now waiting for the VS machine to connect to it via TCP/IP. After the VS machine has connected, and then disconnected, Keyman on the device will automatically exit.
On the VS machine, copy CryptoAPIWrapper.dll from <VSROOT>\ CompactFrameworkSDK\ConnectionManager\bin to the directory of KeymanDesktop.exe. Launch KeymanDesktop.exe.
Click "Save" to save your settings in the current directory where KeymanDesktop.exe is running. The saved defaults will be loaded next time the exe is launched.
Enter the IP Address of the device
Use the recommended value for the Device Port.
Enter the path of the "Target" directory where the ConmanClient bits such as ConManClient.exe reside. The typical value is \ CompactFrameworkSDK\ConnectionManager\Target.
Use the Connect button to connect.
Click on "prep device" after you have connected. On success, you will see a dialog telling you everything went OK.
Use the Disconnect button to disconnect. When you disconnect, the device side bits will automatically exit.
Launch ConManClient.exe on the device. First you must select the flavor of the target device. Also, you must select the location of your "Target" directory in Visual Studio. 11.17. How can I allow Activesync to connect to an Emulator session from Visual Studio .NET 2003?
Download the Emulator ActiveSync Connection Tool from Windows Mobile Developer Power Toys:
11.18. How can I copy files to the device currently connected to desktop ActiveSync?
Download CECopy from Windows Mobile Developer Power Toys:
11.19. Why does the Visual Studio debugger fail to connect to an ARMV4I device?
Cause
Bug in the connection tool after selecting ARMV4I CPU type
Resolution
Configure tool for ARMV4T CPU type:
In Visual Studio, on the Tools menu, click "Select Windows CE Device CPU". Note: this menu item is installed by the Windows CE Utilities for Visual Studio .NET 2003 Add-on Pack
Change the device architecture to ARMV4T
Click Configure, then click Close. Restart Visual Studio if prompted
