August, 2012

Creating cloud-connected
"intelligent" elevators
with Microsoft Azure services
Introducing Microsoft
Azure Intelligent
Systems Service
How big data
creates new
marketing options
for retailers
Enabling productivity
with the
Internet of Things



  • Windows Embedded Blog

    Agility, Team work and Pragmatism

    Posted By Phillip Cave
    Software Development Engineer

    successThis week the extended developer (SDE) leadership team in Windows Embedded had a lively discussion around “agile” and how to foster a collaborative team effort. I followed up with the extended leadership team to help them understand some of the nuances of the transformation we are making.

    The discussion was kicked off asking how we may focus working as a unit to ship product. A misunderstanding arose about specialist vs. generalist team members, how to review contribution, and an overall misconception about being flexible in an agile environment. What follows was my response to the team.

    Yes, foster domain/technology specialists. Of course we should foster expertise around key areas of our product so that we may create technical leadership. Think of the system while doing so. Ensure we have redundant knowledge so that we do not constrain ourselves when delivering product.

    Yes we have an HR review model to evaluate team members. However, an HR review system or rather our interpretation of an HR review system should not dictate how we deliver product.

    Based on our discussion what I heard was that we are going to be evaluated based on the good things we deliver. This is as it should be. Our contribution to delivering product and the leadership on delivering product is all that matters.


    Comments Windows Embedded Standard

  • Windows Embedded Blog

    The Intern Perspective: Colleen Forbes

    Posted By J.T. Kimbell
    Program Manager

    Earlier this week you had the chance to meet Meg. Now you get to meet the 2nd of 3 Explorer interns I coached as a PM this summer: Colleen Forbes.

    Who am I?

    Microsoft is a big company. It is so big it can’t fit in one country alone and employs over 90,000 people. Out of the 90,000 plus people, I am just one of the three Explorer interns at Windows Embedded. Also known as Colleen Forbes, future junior at Whitworth University, in Spokane, Wash.

    Over the summer most people ask me one of three questions (or if they are lucky all three):

    1. What is Windows Embedded?
    2. What is an Explorer Intern?
    3. What did you do work on this summer?

    Number one is always a good starting point, so let’s start with “What is Windows Embedded?”


    Comments Windows Embedded Standard

  • Windows Embedded Blog

    The Intern Perspective: Meg Quintero

    Posted By J.T. Kimbell
    Program Manager

    We continue our series of posts from Windows Embedded interns with the first of our 3 Explorer Interns that I had the privilege of coaching this summer. What’s an Explorer Intern? These interns don’t spend their whole summer in one of the three Software Development positions, but rather rotate between all of them, getting a taste for each. They’ll get the chance to come back next summer as a regular intern in the role of their choice. Below, Meg Quintero will tell you about her summer here in Seattle. To learn more about her project, check back next week for a post authored by all three Explorers.


    Intern Signature Event at Gas Works Park

    Oh hai! My name is Meg, and I am one of the three Explorer interns on the Windows Embedded team. I am a rising junior at Harvard College concentrating in Computer Science and am contemplating a minor in Anthropology to further explore human interaction with technology. I am most recently from Havre, Montana, however, Cambridge has become more of my home. Back at Harvard, I am a soprano in the Harvard LowKeys, a contemporary co-ed a capella group, and have been singing for as long as I can remember. I enjoy biking, rollerblading, running, and pretty much anything that allows me to be outside. I am a big fan of the Red Sox and was able to attend a Red Sox vs. Mariners game and rep my team. I have been enjoying all that the Puget Sound area has to offer including incredible theater (“Rent”, “Les Miserables”, and “Turandot” were phenomenal), great shopping (Pike Place FTW), and waterfront a plenty. I also felt as if I died and went to heaven when I was handed a Samsung 9 Series Ultrabook at the Microsoft Intern Signature Event after hearing one of my favorite bands (Young The Giant) live at Gas Works Park.


    Comments Windows Embedded Standard

  • Windows Embedded Blog

    Understanding CEPC Boot Sequence in Windows Embedded Compact 7 – part 2

    Posted By David Campbell
    Program Manager

    Welcome back! This is part 2 of Doug Boling’s great write-up on Understanding CEPC Boot Sequence in Windows Embedded Compact 7. Last time we covered the PC boot sequence in detail. That provides the background for the Windows Embedded Compact specifics. Let’s jump right in...

    In Part 1, I started this discussion with an overview of two of the three different CEPC boot loaders provided in the Windows Embedded Compact 7. I discussed the LoadCEPC bootloader as well as how to use the BIOSLoader. I also talked about how the FAT file system. An understanding of the layout of a FAT storage device is important when understanding how these bootloaders work. In this installment, I will cover how the BIOSLoader and the WCELDR work and how to modify the WCELDR to adapt it to your hardware.

    How BIOSLoader Works

    In Part 1, I discussed how the file system works, now let’s return back to the BIOSLoader to cover how it works. When the system starts, the BIOS will load the Master Boot Records (MBR) into RAM which will find and load the boot sector of the active partition. This boot sector will be one of the BIOSLoader boot sectors that will have to be installed on the disk. The source code for the BIOSLoader boot sectors is located in \WINCE700\platform\cepc\src\bootloader\biosloader\bootsector, There is a unique boot sector for each of the different File Allocation Table (FAT) formats including ExFAT.

    The boot sector code finds the root directory and looks for the name BLDR with no extension. It expects to find this name in one of the first 32 entries in the root since the boot sector only reads the first sector of the root directory into memory.

    When the BLDR entry is found, the boot loader finds the location of the file data by using the first cluster entries in the directory entry for the file. Instead of following the FAT chain to properly load the entire file, the boot sector assumes that the file will be stored in linear sectors on the disk and reads a fixed (68 sectors or 34816 bytes) into memory at address 0:1000. This hard coded size provides an absolute limit on the size of the BLDR code.

    The boot sector then jumps to the first byte of the BLDR file. The BLDR then switches to protected mode and executes the remaining tasks from there. Those tasks include reading and parsing the BOOT.INI file and downloading or reading from the disk the NK.BIN file.


    Comments Windows Embedded Compact

  • Windows Embedded Blog

    July 2012 Optional Updates are on ECE for POSReady7

    The July 2012 Optional Updates are now available on the ECE site for Windows Embedded POSReady7.

    The list below applies to Windows Embedded POSReady 7:

      • KB2654644 - This is a USB driver update roll-up which includes the latest Embedded USB boot drivers.  Note that KB2533552 is a pre-requisite for this KB.  Volume Licensed customers can download this KB from the Download Center.
      • KB2721923 - This update fixes an issue with the Registry Filter, where the registry filter does not take the customer registry setting correctly.  Volume Licensed customers can download this KB from the Download Center.


    Comments Product Updates

Page 2 of 4 (18 items) 1234