Talk:Windows XP Embedded

Some non-sensical / readily available information
This article seemed rather shorter than last time I saw it, so I checked the history and found another editor had deleted more than half the text, with the following rationalle: Removed non-sensical / readily available information duplicated from existing sources

I know this stuff is not exactly gold, and I'm not bold enough to reinsert it into the article, but I thought I would repost it here, since I feel it does contain worthwhile info which could be worked back in. I've not posted the Embedded Enabling Feature Descriptions section since this may have been an MSDN copyvio. Linton 02:48, 1 February 2006 (UTC)

The XPe Developers kit (also called Windows Embedded Studio) consists of:


 * Embedded Development tools (Target Designer, Component Designer, etc.)
 * A SQL database of all the component/binary/registry dependency information for XP Pro
 * A repository of all the binaries that comprise the entire XP Pro OS
 * Embedded Enabling Technologies (apps and drivers that allow Windows to run in embedded environments, these are a "Value Add" when compared to XP Pro)

The kit will allow the developer to customize the Windows OS by picking and choosing which of 1,000 Windows features and 9,000+ Windows drivers to include. The smallest bootable runtime you can create with most Win32 API support is about 4MB. Although this would not have a networking stack or video, it could perhaps be useful for a serial control device. As you add more windows features to the runtime, the number of dependencies increases which results in a larger "footprint". As an example, if you don't want Internet Explorer in the runtime, simply don't add the IE component to the configuration you build with the XPe development tools. If you do add IE to the configuration then all of its dependencies also come in to the configuration automatically which increases the ultimate size of the footprint.

The Primary development tools the developer uses the most are Target Designer and Component Designer. Target Designer (TD) is for adding, removing and tweaking various components in a configuration. With it one can display all the resources that are "owned" by the components in ones configuration, add Windows components (or custom hardware drivers or third party applications) and build a configuration which results in a bootable mini version of XP.

Component Designer is used to build or view custom components for third party apps or drivers, for converting INF based drivers to a format that can be imported into the SQL database along side all the Windows components.

XPe doesn't use Windows Setup. It uses a feature called First Boot Agent (FBA). Since most of the setup is done offline in Target Designer by prepopulating items such as registry keys, hardware information for PnP or custom shell settings and bin placing all files in advance, there is no need to go through the Windows XP Setup, so FBA is used to process the few items 'online' that couldn't be done 'offline' by Target Designer. After FBA is complete, the embedded device is ready for use or cloning or further customization.

Removed example about McDonald's UK not using b/c of instability

 * Recently McDonald's UK has started trialing till systems using XPe for full-adoption in the coming years, however they have proven unstable in busy drive-through restaurants.

Please provide a source for this. Removed from article for the time being. -- 82.255.73.218 14:14, 31 August 2007 (UTC)

Fair use rationale for Image:Windows XP Embedded Logo.jpg
Image:Windows XP Embedded Logo.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot 23:18, 13 September 2007 (UTC)