Windows Embedded CE 6.0 == Windows CE 6.0 == WinCE 6 == CE6 == Yamazaki

The new name for Windows CE is Windows Embedded CE 6.0.  Some of the marketing guys are unhappy when I call it only “Windows CE”, never mind WinCE or just CE.  Though I really really doubt any of you would be confused or care, I’ll call out officially that all these are the same thing. …

1

DCOM Demystified (kindof) on CE 6

As I hinted at here, in CE 6.0 we have removed DCOM remoting due to security concerns.  This is only the remoting portion.  There has been some confusion on this so I want to make it clear what this means.  You can still do interprocess communication on the same device if you include SYSGEN_DCOM in…

7

Services.exe Migration for Applications in CE 6.0

Thanks to Seattle getting snowed in and MS borderline shutting down and me not having an emulator image built yet, this will be my first ever two blog in one day. OK, enough soon to be dated blog chattiness.  Down to business. Suppose you’re writing an application that calls into a service in servicesd.exe.  (Servicesd.exe…

1

Writing services for the WinCE 6.0 Kernel

When rewriting services.exe for the CE 6.0 kernel, we tried to make it so that as few changes as possible were required for service writers. Unlike application BC (which is critical), there were some places in services.exe where your service may need to be reworked for the new kernel.  Some of these were unavoidable (like…

3

Corrections to CE RTC 1.5 documentation on MSDN

There has been several documentation errors related to RTC 1.5 on MSDN. Here are a few of them:   Issue 1: http://msdn2.microsoft.com/en-us/library/aa924993.aspx   The following page mentions that RTC 1.5 supports multi party audio/video and application sessions. This is incorrect. RTC 1.5 does not support multi-party audio/video and application sessions. It supports only single party…

1

Configuring TAPI line devices in Windows CE

In Windows CE, TAPI listens for device plug and play notifications. When it gets notified of a new device, it looks in the device driver’s key and subkeys for a REG_SZ value named Tsp. If it is found, it specifies the dll name of a TSP (TAPI Service Provider, for instance, unimodem.dll) to be associated…

0

Quality of Service in RTC 1.5

RTC 1.5 supports quality of service for SIP & audio packets using DSCP and 802.1Q tagging. Windows CE has the following pre-defined DSCP traffic types: typedef enum _DSCP_TRAFFIC_TYPE {    DSCPTypeNotSet        = 0,    DSCPBestEffort        = 1,    DSCPBackground        = 2,    DSCPExcellentEffort   = 3,    DSCPVideo             = 4,    DSCPAudio             = 5,    DSCPControl           = 6,    NumDSCPTrafficTypes   = 6} DSCP_TRAFFIC_TYPE Check…

1

Introducing the Location Framework for Windows CE

We’re very committed on CE to creating a great development platform for location aware applications.  The first piece of this was GPSID, introduced in WM5 and now in general embedded for CE 6.0. In CE 6.0, I’m pleased to announce we’ve added another, more generic abstraction layer for retrieving location — the Location Framework.  I…

3

GPSID in Windows CE 6.0

In Windows Mobile 5, we first introduced the GPS Intermediate Driver.  I describe why it went into a WM release rather than general embedded here.  In CE 6.0, I’m happy to announce that GPSID did make it into the product for real, as promised (or as close to promising in public as the lawyers/marketing/pr/all my…

3

Completing RTC’s NAT story

In my first post, I touched on all the new features of RTC 1.5. Prathap also posted a blog on RTC 1.5 port manager, which shows how RTC’s port manager APIs can be used by user app to communicate outside NAT. Here I will try to complete the NAT picture of RTC 1.5  As mentioned…

2