Comments on: Preparing and Installing Windows XP Embedded Images – Part II: Building Images

By: MELVIN

MELVIN — Tue, 27 Jul 2010 17:31:09 +0000

my email is melvinng05@hotmail.com, thanks!

By: MELVIN

MELVIN — Tue, 27 Jul 2010 17:29:32 +0000

Anyone can tell me the product key of Windows Embedded Standard 2009? Thank Q so much for the helping :)

By: Augusto Alvarez

Augusto Alvarez — Fri, 19 Mar 2010 21:21:39 +0000

Hello Lisa,
The Windows Embedded Standard posts are made using virtual machines and I didn’t require to use any driver regarding the integration components in Hyper-V.
To add a driver into Windows XP Embedded or Windows Embedded Standard, you need to use “Component Designer”, “Import” and the save the new component. After that, import that file using “Target Designer”, it should now be available in “Hardware” > “Devices”.
Cheers!
Augusto

By: lisa toohey

lisa toohey — Fri, 19 Mar 2010 20:57:50 +0000

why is it you don’t add instructions for including drivers? In your windows standard instructions you just ignore the warnings and then never provide a solution.

By: Augusto Alvarez

Augusto Alvarez — Thu, 18 Mar 2010 16:17:00 +0000

Hello PB,
Which design templates did you use? You can check the components included on each by selecting “help”. You’ll see which one fits more into your needs.
Hope it helps,
Augusto

By: Pb

Pb — Thu, 18 Mar 2010 03:11:09 +0000

Hello Augusto,

I followed your instructions and able to run Windows XP Embedded.
However, it started up and showed me cmd.exe. I didn’t see user interface. I also set User interface core but I didn’t see GUI in Windows XP Embedded at all.
What did I miss?
Thank you,
Pb

By: AJ

AJ — Tue, 24 Nov 2009 23:14:18 +0000

Hi Augusto,

Thanks for your reply. So do you think individually adding each hardware component including chipset/audio/video/Lan drivers then using a template to add the OS files would work? So running tap.exe on my Windows desktop and importing that file will obviously not work. I’m confused! I have never created an image using these tools and I don’t have a system running with this SBC to be able to create an image. What do you suggest I should do?

Thanks,
AJ

By: Augusto Alvarez

Augusto Alvarez — Tue, 24 Nov 2009 22:09:45 +0000

Hello AJ,
I’m afraid that you won’t be able to actually manage to boot an image prepared in a completely different hardware; remember that Windows XP is a HAL dependant OS.
Still, the drivers can be imported using Component Designer, File > Import and select the INF files.
Hope it helps!
Cheers,
Augusto

By: AJ

AJ — Tue, 24 Nov 2009 22:03:04 +0000

Hi Aziz,

I have an atom based processor single board computer:http://www.portwell.com/pdf/embedded/NANO-8045.pdf

I have the WIN XP embedded and have installed the necessary components to create an image. But I am not sure how to go ahead and create the image considering the chipset is completely different to what I have on my PC on which I have installed the tools. So will running tap.exe actually work in my case? Also how do I add the drivers for the new chipset into the image? It has different Chipset, Audio, Lan and Video drivers.
Your help would be much appreciated. Also I have a SATA hard drive which I need to run the OS from.

Cheers!
Aj

By: Augusto Alvarez

Augusto Alvarez — Tue, 20 Oct 2009 13:01:59 +0000

Hello Aziz,
Have you check this PDF? http://www.sjjmicro.com/Docs/Articles_XPE/USB%202%20Flash%20Boot.pdf
Cheers!
Augusto

By: Aziz

Aziz — Tue, 20 Oct 2009 06:17:26 +0000

Hi Sir,

I want to build an XPe image for a ibase ATOM based motherboard (IB888). I have setup the development enviroment on my Laptop having Vista as OS, will this make any difference compared to setting up the development eviroment on a machine having XP pro?
I have followed the procedure mentioned in Part 1 and 2. I have added USB boot 2.0 as I want to install the operating system on a USB. I have checked the dependency and created the image. Also I have selected EWF NTLDR as I am going to burn the image on a CD. Rest I have followed as mentioned in your blog. Do I need to do anything extra other than this to make the system work?

Awaiting reply.

Thanks in advance.
Aziz

By: Arwin Tugade

Arwin Tugade — Wed, 12 Aug 2009 20:33:39 +0000

Mohammad,

You’re going to have to download the driver for that particular nic from intel. Basically it’s going to be the same thing that I had to do to get the SATA chipset to be recognized because I kept getting the 0×07 bluescreen error on image boot. You have to add the driver through the component designer via importing the inf file from the driver that you downloaded. After you do that, there should be a device that shows up in the target designer that you can add to you image and you can bake it in. I need to find my specific docs on doing so but it wasn’t that hard.

Arwin

By: Mohammad

Mohammad — Thu, 09 Jul 2009 19:10:41 +0000

I have a Intel Pro 100 VE network connection. I am trying to build a case supporting network connection. One I import pmq file it does not detect my network adapter. So I added manually. However, when I copy the img file on the development computer. Win xp embedded works but it does not recognize any network adapter. I would be very thankful if you help me to fix the problem?

By: Windows Embedded Standard 2009 Step-by-Step Deployment – Part II « Augusto Alvarez

Tue, 21 Apr 2009 03:40:04 +0000

[...] process it’s practically the same that we executed on XP Embedded (Post I, Post II and Post III). And again, as I mentioned before, this deployment is oriented to Embedded images [...]

By: Windows Embedded Standard 2009 Step-by-Step Deployment – Part I « Augusto Alvarez

Mon, 30 Mar 2009 00:31:12 +0000

[...] Preparing and Installing Windows XP Embedded Images – Part II: Building Images [...]

By: Augusto Alvarez

Augusto Alvarez — Thu, 26 Mar 2009 13:23:37 +0000

Hello RR,
I’m preparing the steps necessary for deploying Windows Embedded, that are practically the same that you con find here.
You’ll need to add the SATA drivers within the process of building the image, using Target Designer. Try downloading them from the HD manufacturer.
Cheers
Augusto

By: RR

RR — Thu, 26 Mar 2009 06:49:38 +0000

Hi,
Please let me know how to deploy a windows embedded standard image on SATA disk. What are steps to do that and which all components needs to be added.

By: Arwin Tugade

Arwin Tugade — Sat, 24 Jan 2009 04:51:33 +0000

A nice addition to this document would be how to add a third party driver with the component designer tool, by simply importing in the inf for the driver and doing the release etc. I had to do this for a device of mine because it had a SATA harddrive on it.

By: Augusto Alvarez

Augusto Alvarez — Mon, 12 Jan 2009 21:33:18 +0000

About the firewall, I didnt’t make much tests on that, but I was quite sure that the FW component was needed… maybe on the tests that I made, I had some other dependency that was corrupting my connectivity.

Thanks for all the comments, again.

Cheers!

Augusto

By: Roger Levy

Roger Levy — Mon, 12 Jan 2009 17:30:32 +0000

The guideline that twice as much target RAM is needed as the image size is frequently repeated but it is a misleading simplification. The guideline is based on the fact that a ramdisk is created in RAM that is as large as the image size so if RAM is twice the image size then there should be “enough” RAM left over. This idea really makes no sense. You need enough RAM so that the needed kernel elements, system DLLs, user code, etc. can fit entirely in the remaining RAM with no paging. Depending on the application this amount can be smaller or much greater than twice the image size. For example if your application creates huge arrays or allocates a large amount of memory dynamically, the guideline is inadequate. On the other hand, if you have a very simple app that uses little memory for data, the guideline is more than adequate.