Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
The December 2012 Security Updates are now available on ECE for Microsoft® Windows® XP Embedded with Service Pack 3 and Windows® Embedded Standard 2009.
This list below applies to Standard 2009 only:
The list below applies to both XPE SP3 and Standard 2009:
Comments Product Updates
Posted By Valerie OlagueAmericas Business Group Lead
The Americas team congratulates four ecosystem partners who recently won Partner Excellence Awards: Bsquare, Adeneo Embedded, IntervalZero and ICOP Technology. The winners were announced at a virtual regional Gold and Silver partner event held on November 14, 2012.
The Windows Embedded Partner Excellence Awards recognize members of the Windows Embedded Partner Program that excel at driving the Windows Embedded business. Their contributions help bring solutions to market that support the development of intelligent systems worldwide.
Thanks to all the partners who submitted nominations. Below are descriptions of the contributions made by each winning partner:
Comments Windows Embedded Standard
Posted By David CampbellProgram Manager
In a previous post, I discussed the Windows Embedded Compact 2013 announcement and a number of great new features in the OS and tools. With those posts, I received a number of questions about the tools. As you all know, Windows Embedded Platform builder (PB) is a plug in to Visual Studio. For Windows Embedded Compact 7, our Platform Builder plug in and tools were hosted by Visual Studio 2008, while Platform Builder in Windows Embedded Compact 2013 will be hosted in Visual Studio 2012. A number of people asked whether PB from Windows Embedded Compact 7 could be hosted in Visual Studio 2012, or alternatively whether PB from Windows Embedded Compact 2013 can target Windows Embedded Compact 7. Unfortunately, the answer to that is no. There had to be significant changes to both Windows Embedded Compact 2013, including PB, as well as Visual Studio 2012 to support the latest versions of each. The hosting has changed, and more importantly, the compilers and ABI (Application Binary Interface) to the ARM chipset has changed and are incompatible with each other. Even though each version of Windows Embedded Compact 7 can target the same chipset in this case, the compilers from each cannot support the other. More information will be posted on this in a future article.
While the Windows Embedded Compact 2013 announcement is certainly exciting, we want to continue posting great information on Windows Embedded Compact 7 as well. To that end, we have another great in-depth article from Doug Boling to share.
Microsoft Platform Builder is a tool that anyone who ports Windows Embedded Compact will live in throughout the project. (PB is also used when creating new device images from scratch. This information certainly applies to that scenario as well.) Given the time spent in this tool, it’s critical that your development machine be properly configured to maximize the performance of the tool and by implication your performance.
Comments Windows Embedded Compact
Posted By Chris ElliottSenior Marketing Communications Manager
Christmas is fast approaching, and if you’re anything like me, you have some shopping to do.
Some of you may be considering buying a new mobile phone as a gift for yourself or someone on your list. There are so many cool new options out there to choose from (including some great Windows Phone 8 devices—hint, hint) but for those with a car that has an in-car connectivity system, like Ford SYNC, one important consideration will be whether the new device is compatible with your car.
Comments Windows Embedded Automotive
Posted By J.T. KimbellProgram Manager
A few years ago on our old blog, I posted to let everyone know about a PowerToy we released called CBS Package Inspector. With our new blog up and a new audience, I wanted to spend a bit of time highlighting that tool again.
CBS Package Inspector was created by Anup Vasudeva Rao, a software development engineer, and released shortly after the release of Windows Embedded Standard 7 with the purpose of allowing Windows Embedded developers to better understand the contents of the packages they are installing on the system. How does it do this? By providing the ability to crack open and peek inside .cab or .msu files, showing their contents.
“Great!” you may say, but what exactly does that mean? Good question, and luckily for you, I’m prepared to divulge some of those details.