Wince6.0 installation sequence

From http://www.cnblogs.com/walzer/archive/2007/05/13/744729.html

1. Install Visual Studio 2005 first. I got Professional Edition. It is best not to use default to install the component custom. Otherwise, it will waste a lot of disk space. Wince600's platform builder is not as independent as wince500, but as a vs2005 plug-in. Later, the establishment and customization of OS and compilation and debugging will all be completed in vs2005.

2. Install Visual Studio 2005 Service Pack 1, publish the address http://msdn2.microsoft.com/zh-cn/vstudio/bb265237.aspx
This is required. In release note, SP1 provides Windows Embedded 6.0 platform and tools support.
Different vs2005 versions (Standard/professional/TEM edition) correspond to different downloads, but simply use this download http://www.microsoft.com/downloads/details.aspx? Familyid = BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC & displaylang = EN 430 + MB, all versions available.

3. Optional. Install Visual Studio 2005 Service Pack 1 Update for Windows Vista.
Publish and download URLs
Http://www.microsoft.com/downloads/details.aspx? Familyid = 90e2942d-3ad1-4403-a2ee-4acc0aace5b6 & displaylang = en
Added support for Vista Based on SP1. Note that you must first install SP1 and then install this. In system requirements, we emphasize required software: licensed copy of A Visual Studio 2005 and Visual Studio 2005 Service Pack 1. I thought it included the above SP1 and it took a lot of time.

4. Install msdn. select from the installation page of vs2005. The msdn interface function of the new version looks cool, but the product documentation of ce6 is very sloppy, and many details seem to have not been clearly written. Therefore, we recommend that you choose the product documentation of ce5 for future reference.

5. Install Windows Embedded ce 6.0. Application developers can skip this step. Later, we will mention that the SDK generated by ce6 can be used for work. However, if you do not install the SDK, you may not be able to obtain the ce6 product documentation on the local msdn, in addition, there are a variety of application sample codes in the public directory.
Notes:
(1) You can change the path in this step. Click components and then click browse below. This is not a special step to change the path when installing wince500. I am so mad at next/back for a few laps.

(2) ce6 does not have a dedicated emualtor (x86) option. I thought it was included in x86, and later I found that I installed the x86 part in white. The Simulators of wince600 and vs2005 can directly run arm commands. They call this armulator. (It seems that this is the first thing on Linux, Which is copied by Ms? ). This led to the failure of ce5 x86 emulator to run on vs2005. I had to use a detour and not very easy-to-use method. I will write an article later.

(2) Pay attention to the disk space. I chose armv4i and x86 to use 6.5 GB, which is larger than wince500.

6. Install Windows Embedded ce 6.0 platform builder Service Pack 1. Similarly, application developers may not install it.
Publish page http://www.microsoft.com/downloads/details.aspx? Familyid = BF0DC0E3-8575-4860-A8E3-290ADF242678 & displaylang = en
This copy only upgrades platform builder and does not modify the code in the wince600 directory.

--------------------------------
If BSP developers do not intend to use the simulator, install it in this step. Continue with the application.

7. Install the Microsoft device emulator 2.0. Release page
Http://www.microsoft.com/downloads/details.aspx? Familyid = dd567053-f231-4a64-a648-fea5e7061303 & displaylang = en
Note that there are 32-bit and 64-bit versions available for download. After the installation, the emulator program is still under C:/program files/Microsoft device emulator/1.0, and does not generate a directory named 2.0. I always feel fooled by Microsoft.

8. Install Virtual Machine Network Driver for Microsoft device emulator. Release page
Http://www.microsoft.com/downloads/details.aspx? Familyid = dc8332d6-565f-4a57-be8c-1d4718d3af65 & displaylang = EN // This release page is out of date and cannot be found. I uploaded this file myself, please download it from the address below
Http://files.cnblogs.com/walzer/Virtual%20Machine%20Network%20Driver%20for%20Microsoft%20Device%20Emulator.rar
If this is not installed, the simulator cannot be started, black screen. If the command line is used to load and compile deviceemulaotr.exe, you can see that the Serial Output Window is stuck in the initialization DMA transmission step. I got stuck on this issue for nearly all night. I just got lucky when I slept on this release page and finally got it. The download and transport modes of the ce6 simulator are called "device emulator (DMA)". I initially understood it as direct memory access, thinking that Microsoft is trying to solve the problem of slow single-step debugging on the simulator, what data does the memory and simulator process transmit in DMA mode? similar to the dual-port RAM mode, the data is directly transferred in the memory, which is irrelevant to ActiveSync and TCP/IP connections. Later I found out that the DMA is estimated to be the device emulator adaptor. It will automatically find out the available Connection Methods on the simulator, or several old methods such as TCPIP, ActiveSync, kitl, and manual. There is no ActiveSync on Vista, so you have to use TCP/IP to connect. If you don't install this virtual switch, you won't be able to connect.

9. It is best for Vista users to install Windows Mobile Device Center 6. As a substitute for ActiveSync, I expect most of them will be used for later debugging.
32-bit edition: http://www.microsoft.com/downloads/details.aspx? Familyid = 83d513ea-9df9-4920-af33-3a0e2e4e7beb & displaylang = en
64-bit edition: http://www.microsoft.com/downloads/details.aspx? Familyid = 6eb8d0aa-bc6b-4864-8ffe-dc26e1d9f843 & displaylang = en

I have successfully installed ce6 on both XP SP2 and Vista Business and created a new deviceemulator Project (not pbworkspace now, osdesigns). After compilation, I started it with ce6 attach device; then compile and generate the SDK, install it on XP SP2 or Vista, and then create a VC project from emulator SDK in vs2005, compile and debug it in a single step on emulator, now, emulator is not connected from the attach device, but started from the device emulator manager. That is to say, application developers do not need to install ce6 at all, as long as vs2005 is installed.

Send two customs clearance charts, device emulator manager, and a customized ce6 Chinese Simulator