Windows Embedded Home
Windows Embedded 8 Family
Windows Embedded 7 Family
Other Windows Embedded Products
Posted By David CampbellProgram 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.
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
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:
Comments Product Updates
The July 2012 Optional Updates are now available ont he ECE site for Windows Embedded Standard 7.
The list below applies to Windows Embedded Standard 7 and Windows Embedded Standard 7 SP1.
Note: The July Optional Update for Windows Embedded Standard 7 is affected by the issue described in MIcrosoft Security Advisory 2749655, in which the digital signature on files produced and signed by Microsoft will expire prematurely. To resolve the issue for the July Optional Update for Windows Embedded Standard 7, install the September update.
Posted By Phillip CaveSoftware Development Engineer
Last time I presented the first part of this post. In this post I dive deeper into making work visible and discuss the pragmatic application of it.
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:
Now that we have our worked defined (infrastructure, discovery, implementation), our goal is to make it all visible.
There is an amazing psychology around visualizing and making our work tangible. I will go into small detail about how our senses (sight and touch) play a part in this. Suffice it to say when we make our work visible we tend to take on a different level of responsibility for it and our decision making is affected by it in a positive way.
Our world is composed of “bits”. The experience we deliver to customers is the culmination of the assembly of a lot of bits. Our customers do not care about the bits, they care about the experience. Our customers do not care about our roles of who works on those bits; they care about getting the experience in a timely fashion. Our business relies on us to complete our bits quickly in order to realize the cash flow and tangible value associated with those bits.
Comments Intelligent Systems
Posted By Chris ElliottSenior Marketing Communications Manager
This week, we’re bringing Ford SYNC, powered by Microsoft, to the Emerald City as part of gdgt Live! Seattle. And we want to share the fun with you while we’re at it.
On Thursday August 16, we’re going social for a fun contest. Whether you are able to attend gdgt Live! Seattle or not, it’s easy to participate. All you have to do is go follow @MSFTWEB and tweet your favorite Ford SYNC feature some time during the day using the #SYNCSEA hash tag.
Told you it was simple.
So, what’s in it for you? Well, for starters, our grand prize giveaway is an Xbox 360 with Kinect. Plus we’ll have some amazing Microsoft Hardware up for grabs too. We like to show off all the great things you can do with SYNC like telling the car where you want to go, listening to text messages or calling up your favorite song using your voice. Join us at gdgt Live! Seattle to see and hear for yourself.
And don’t worry if you can’t make it, the contest is open to all residents of the US.
See you in Seattle!
The Fine Print
Comments Windows Embedded Automotive