Windows CE 6.0 > Release, highlights and changes

WinCE 6.0 has now been released by Microsoft being the embedded operating system to succeed WinCE 5.0. The WinCE 6.0 Kernel offers a considerably larger expanded address space and more processes than that of WinCE 5.0.

New support features and changes:
- The number of supported processes has been increased from 32 to 32K!
- Both User mode and Kernel mode drivers are now supported
(User mode drivers interface with the kernel through a dedicated API rather than direct)
(Kernel mode drivers interface directly with the kernel)
- 32 MB address space for processes has now been increased to 1GB!
- CE 5.0 drivers can be ported over CE 6.0 in most cases
- No longer offer document viewers in CE 6.0.
(Document viewers were outsourced for CE 5.0.)


Unsupported Kernel APIs:

API Porting information
CeZeroPointer
This is no longer supported.
GetCurrentPermissions
Completely impossible, remove it. Likely this call wraps code that accesses another process’ virtual memory space; verify that the addresses you’re using are now getting duplicated / aliased for you, or else you will need to do so yourself.
MapPtrToProcess
This is no longer supported. If this is being used to access an API argument, you can remove the mapping call. If this is being used to access a pointer that is passed inside a structure or through some other means, you would need to explicitly switch to calling buffer marshalling and unmarshalling APIs.
MapCallerPtr
This is no longer supported. If this is being used to access an API argument, you can remove the mapping call. If this is being used to access a pointer that is passed inside a structure or through some other means, you would need to explicitly switch to calling buffer marshalling and unmarshalling APIs.
SetKMode
Completely impossible, remove it. Likely this call wraps code that accesses another process’ virtual memory space; verify that the addresses you’re using are now getting duplicated / aliased for you, or else you will need to do so yourself.
SetProcPermissions
Completely impossible, remove it. Likely this call wraps code that accesses another process’ virtual memory space; verify that the addresses you’re using are now getting duplicated / aliased for you, or else you will need to do so yourself.

* For more details click on: http://msdn2.microsoft.com/en-us/library/aa910715.aspx