Posted By David CampbellProgram Manager
He’s back! Doug Boling has once again supplied us with a great write-up for those who missed his July webcast. The topic will be a two-part post. In the first part, Doug details an overview of the three CEPC boot loaders as well as the boot sequence on a PC - which is key to understanding the Windows Embedded Compact process:
It may come as a surprise that the most popular hardware platform for Windows Embedded Compact 7 (WEC) is the standard PC chassis. This is also the hardware platform for Windows Embedded Standard (WES), but Compact 7 brings its own unique features. A properly tuned Compact system can boot faster than WES. Writing drivers is significantly simpler on WEC than on Standard. And of course, there is the dramatically lower licensing cost. This isn’t to say that Windows Embedded Standard isn’t a great operating system, it is. The point is that Compact has a different feature set than Standard and many embedded systems choose Compact over Standard on their embedded PCs.
Comments Windows Embedded Compact
The July 2012 Optional Updates are now available on the ECE site for Windows® XP Embedded SP3 and Windows® Embedded Standard 2009.
The list below applies to Windows Embedded XPe SP3 and Standard 2009:
If you have questions on accessing the ECE, please email MS Mobile & Embedded Communications Feedback & Support, ECE@microsoft.com.
Comments Product Updates
Posted By J.T. KimbellProgram Manager
A lot of our summer interns are wrapping up their experiences here at Microsoft, so you’ll be seeing several more of these posts in the next few weeks. In this post Arijit Choudhury, an SDE intern, tells you about his experience and work this summer.
Getting a chance to work as a Software Development Engineer (SDE) intern at Microsoft is my very own ‘What do you want to be when you grow up?’ story. I still remember using my first PC from the 90s (Windows 95 running on an Intel MMX processor) and how it introduced me to the Internet, PC games and computer science (CS). Today I am going to share my experiences about my Microsoft internship and in particular, my stint with the Windows Embedded Componentization team.
But first, whoami? I am Arijit Choudhury and I’m studying for my Master’s degree in Computer Science at the University of Florida in Gainesville. Before that, I finished my bachelors from the Dhirubhai Ambani Institute of Information and Communication Technology in Gandhinagar, India. Most of the time, you’ll find me programming (complete with noise cancellation headphones) or playing Soccer wearing an Arsenal jersey on the University field. Getting a chance to learn how to write good code for Microsoft and playing soccer along with other Microsofties in beautiful Seattle is my idea of a perfect summer.
Now that I’ve introduced myself, let us move straight to the three things that impacted me the most during my internship:
Comments Windows Embedded Standard
Posted By Robert PetersonSr. Product Manager
We have been talking about the cloud and ways embedded device OEMs can benefit – but let’s specifically look at why Windows Azure is a great fit. Only Microsoft can provide a familiar, complete solution to help your business from device to cloud. In fact, for devices powered by a Windows Embedded OS, using Windows Azure has some distinct advantages:
Comments Cloud Services & Management
Posted By Phillip CaveSoftware Development Engineer
Last month I provided an overview of Agile software development in Windows Embedded and set the table for some great follow-up posts. In this post I dive deeper into defining work and the value of making it visible.
The introduction to this series on “Embedded Agility” summarized the transition and ongoing transformation of Windows Embedded to a delivery model based in Lean thinking. That first post outlined 3 basic tenets:
Last time I wrote on defining small customer experiences. This post discusses what to do with all those experiences we define. This is our “work” to do. Our ability to deliver on that work is greatly enhanced when we understand and see it.
I am breaking this blog into two portions. I first need to describe the “work” we need to make visible. The second portion of this will discuss visibility and activities. Typically we only think of scenarios and user based stories. In software projects “work” may be defined within three areas:
Comments Intelligent Systems