Looks like this trial version of Windows Embedded supports only x86 based target devices. Now that we have all these ready, lets create a real project. How the heck am I going to deploy this? They just say copy the files on to your target device and boot up – it’s not that simple! Build Target Image – this will compile and generate all the necessary binaries and other files for your embedded OS, together with the necessary directory structure. Check Dependencies – this will tell you what are the missing dependent components in your configurationsģ. Add necessary components to your configurationĢ. To begin, you start a new project (it is called configuration):ġ. It also lists all the components that you got with Windows Embedded Standard 2009 Kit, approximately 10,000 components. This has access to your component database. This is where you develop your Embedded project. I’ll discuss the use of this later as we go along. This is a utility for you to allocate (or de-allocate) some space in your hard drive and use it as a virtual disk drive.
After designing, you can add these components to above database for later use.
This lets you design new components out of your software applications, third party device drivers (Windows XP), etc. You may have your components also added to the same database for future projects. Operating System components, such as NT loader, Session Manager, etc.Ĭomponent Database Manager uses SQL Server for managing these components. Hardware/Software drivers needed to have in the final image of Embedded OS.Ģ. I learnt almost everything by searching the WEB, Microsoft also had good tutorials, only for the earlier versions (Windows XP Embedded), but they help.ġ. All the files are in C:\Program Files\Windows Embedded directory. Windows Embedded Development Tool Kit is installed as “Microsoft Windows Embedded Studio” in your Windows Programs menu.
First download all the software components, and install them in the above order. Imagine if you didn’t have high speed Internet? You don’t need to spend so much time since I have already done all the hard work. Two complete days are gone – just to install the software on your development machine. Completed SQL Server installation after installing PowerShell 1.0 SQL Server 2008 Express – this is another pain in the b…, I needed one more piece of software to complete this, and it was Windows PowerShell 1.0, can be downloaded from Microsoft.Ĥ. NET Framework SP1 (these are cumulative upgrades of. This SQL also needs the latest Microsoft installer 4.5.įinally, I installed all the software in this order:ġ.NET Framework 3.5 and then. So I downloaded that and now I am ready to go (so you think). I downloaded the latest – 2008 Express, which needs.
I didn’t have this, but you can download it for free (all the Express editions are free). Now you need Microsoft SQL Server 2005 SP 1 Express at a minimum.
Next step when you try to install this, there are PREREQUISITES! Your development machine (PC) should have Windows XP Service Pack 2 (or if you have SP 3, even better). So, you need another software to burn the ISO image to a DVD - another software to download (I used ISO Magic – the trial version). Save them in your hard drive and run the first part (exe) to extract and make a 4.5GB ISO image that you can burn into a DVD. It comes in 7 pieces, each approximately 700MB in size. Some of the things I discuss here are workable in Windows XP Embedded too, but you may need SP2/SP3 with 2007 feature pack.įirst of all you need to download this ginormous Windows Embedded Standard 2009 installation files. This is the Microsoft’s new genration of Windows XP Embedded OS, with 10-year life cycle guarantee.