Saturday, April 05, 2008

 

Functionality Removed from Windows Embedded CE 6.0

Topics Description
COM and DCOM
Distributed COM (DCOM), sometimes also referred to as COM Remoting, is not included in CE 6.0. For more information, see this Microsoft Web site, or contact Microsoft support or an authorized distributor to inquire about possible alternatives.

Export Wizard
The Export Wizard has been removed from CE 6.0. For information about a workaround, see Exporting a Catalog Item from the Catalog.

File Viewers
The Microsoft Excel, Microsoft PDF, Microsoft PowerPoint, and Microsoft Word viewers are no longer available from the catalog in CE 6.0.

IEEE 1394
CE 6.0 no longer provides device drivers for IEEE 1394 devices. IEEE 1394 device drivers may still be available for Windows Embedded CE through third-party vendors.

Inbox
The Inbox, also known as the Messaging Application (PMail), has been removed from Windows Embedded CE.

Native Wi-Fi
CE 6.0 does not support native Wi-Fi.

Peer-to-Peer Networking
Peer-to-Peer Networking (P2P) has been removed from Windows Embedded CE.

Pocket Internet Explorer
CE 6.0 no longer includes the Pocket Internet Explorer browser.

The catalog items corresponding to the SYSGEN_PIE and SYSGEN_WEBVIEW variables have been removed.

If you set the SYSGEN_HELP variable, you must now set the SYSGEN_IE or the SYSGEN_IESAMPLE variable to achieve an effect.

SDK Wizard
The SDK Wizard has been removed from CE 6.0. The SDK Wizard has been replaced by the SDK development tool accessed through Visual Studio. For more information, see SDK Development.

x86 Emulator
The x86 emulator has been removed from CE 6.0. Instead, Windows Embedded CE includes a new Device Emulator that emulates the operational behavior of a target device based on an ARM microprocessor. For more information, see Device Emulator.

Thursday, April 03, 2008

 

Connecting the CE 5.0 emulator to VS2005

Title: Connecting the CE 5.0 emulator to VS2005

From: Lewis Williams

Email (Optional): lewisw#tesco.net

Added: 3/10/2007 5:32:12 AM

Message: Connecting the CE 5.0 Emulator to VS2005

1. This uses the network method and saves the emulator state. It does not use activesync, communications ports or a null modem cable.

Start the emulator using a shortcut command that is something like this:

"C:\Program Files\Windows CE 5.0 Emulator\Emulator_500.exe" nk.cem
/video 640x480x16
/Ethernet virtualswitch
/sharedfolder "C:\CE5SharedFolder"

The shared folder appears on the emulator as \My Device\Storage Card. Using the shared folder, copy the following files to the \My Device\Windows\ folder on the emulator. These files are located on the host at \Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\x86, or similar

Clientshutdown.exe
ConmanClient2.exe
CMaccept.exe
eDbgTL.dll
TcpConnectionA.dll

2. Select Emulator -> Start Menu -> run -> \Windows\conmanclient2.exe.

3. Get the IP address of the emulator by double-clicking on the T networking symbol bottom left. If it has no ip address try installing Microsoft Loopback Adapter on the host, check for Virtual Machine Network Services, or other host networking hacks. (This is the difficult bit).

4. To check that the emulator is responding, on the host type Ping at a DOS prompt.

5. To get "Save State" working on the emulator, shut down the emulator using the "Save State" option. Then navigate to Host -> My Documents -> My Virtual Machines

6. The saved state is in the folder that is named with a curly brackets string similar to {06A8A448-EB8B-4E0B-8A88-451412A10C66} say, and known as a GUID. Attempt to rename this folder so that you can highlight and copy the GUID string itself (not the folder).

7. Then add an option, which is similar to /vmid {06A8A448-EB8B-4E0B-8A88-451412A10C66}, to the emulator shortcut command above.

8. The shortcut should now start the emulator from its saved state. It is a good idea to back up the saved state folder.

9. On the host select Visual Studio 2005 -> Tools -> Options -> Device Tools -> Devices

10. Then select Windows CE 5.0 Device -> Properties -> Configure

11. In the "Configure TCP/IP Transport" dialog box, select "Use specific IP address", and then type the emulator IP address you found above.

12. Close the dialog boxes.

13. Select Emulator -> Start -> run -> \Windows\cMaccept.exe and connect to the emulator from VS2005 within three minutes.

14. Run your application from Start Debugging in VS2005 and VS2005 should deploy the two cab files nectcfv2.wce5.x86.cab and system_SR_enu.cab first (this may take some time), and then your application.

15. Close your application in the emulator (I've had trouble using the Stop button on the host).

16. Shut down the emulator using the "Save State" option.

17. You may need to re-run cMaccept each time you restart the emulator or VS2005, but the cab files should not need to deploy again, and the emulator ip address should remain the same.

18. To avoid cMaccept navigate host -> programs -> Microsoft Visual Studio 2005 -> Visual Studio Remote Tools -> Remote Registry Editor

19. In the "Select a Windows Device" dialog box that appears highlight the "Windows CE 5.0 Device" option

20. In the emulator run cMaccept and then immediately click OK in the Remote Registry Editor

21. Highlight Windows CE 5.0 -> HKLM -> System

22. Right click in the right hand pane and select New DWORD value.

23. In the name field type (exactly and without the quotes) "CoreConOverrideSecurity" and set its value to 1

24. Close the editor. Shut down the emulator with Save State.

Lewis Williams

This page is powered by Blogger. Isn't yours?