Preparing and Installing Windows XP Embedded Images – Part III: Using Remote Boot

After what we’ve seen on the previous posts: Setting up the environment (Part I) and building an Windows XP Embedded Image (Part II) we can complete the remote boot process with diskless devices with this last part.

There are special hardware requirements for this procedure and could get a little tricky. In the computer you are using to prepare the image (the server), you need an additional hard disk (or virtual disk) which you will use to boot the image from.

To prepare the image for remote booting:

1. Add a second drive to the machine that act as server. Format the volume and set it like an “Active” partition.

2. Copy all of the files that were created on the Windows Embedded Images subfolder you chose to a second disk (virtual disk if you are using virtual machines)

Note: Since this disk will be used to boot an operating system image, remember that the partition within must be Active. Otherwise the operating system will not boot.

3. After copying all of the files to the second hard disk, move it to a client machine and boot that client using the disk.

4. After the image boots, you’ll see that several components are configured in the image, by a process named First Boot Agent. This process takes a few minutes to complete.

If you are using the System Cloning Tool, then fbreseal is run in the first boot, as the last step of the First Boot Agent. As stated before, if the image is rebooted afterwards, the image gets a new name and SID, so the reseal process is lost. As you need to keep it for diskless computers, don’t reboot after you see the following message. Turn off the computer instead.

5. After shutting down the computer, remove the disk and place it as the secondary disk on the computer you use for creating the image. That is the image that will be uploaded to the remote boot server and downloaded by each diskless client.

Using SDI Loader and SDI script

Now that you have the operating system resealed in the secondary disk, it’s time to create the SDI image. You will create two SDI files, one for storing the image as it is copied from the physical (or virtual) disk, and a second one that will store the final image that the clients will use for remote booting.

1. Open SDI Loader from Start | All Programs | Microsoft Windows Embedded Studio

2. Click on Add Disk

3. As you are creating a new SDI, type the name of a new file (like xpe-partition.sdi) and select Add

4. Since the file is new, a dialog will ask if you’d like to create the file. Answer Yes

5. The next step is to set the image size. The image size must be:

a. At least the size that the files on the resealed disk + some space for temporary files

b. At most half of the total system RAM (ie, if the client has 512mb of RAM, the image limit is 256mb)

c. There is a practical image limit of 500mb. Beyond that, it is likely that the image won’t boot.

This SDI file represents the partition that hosts the operating system. Set the image size and click OK

6. After the SDI file is created, a new virtual disk will be automatically added to the server. The disk needs to be partitioned, formatted and mounted. From the Control Panel | Administrative Tools open Computer Management. Select the Disk Management item from the left pane

a. The following dialog will appear notifying of the new disk. Click on Next

b. Make sure the disk is selected and click on Next

c. Since you won’t use a dynamic disk, leave the disk unmarked in the following screen, and click on Next

d. Click on Finish to close the dialog

e. Right click on the newly created disk and choose New Partition

f. In the wizard that opens, click on Next

g. Choose Primary partition type and click on Next

h. Leave the maximum partition size and click on Next

i. Assign a letter to it (like F) and click on Next

j. Make sure that the selected File system is NTFS and click on Next

k. Click on Finish to format the disk.

7. With the partition created, move the files from the disk that was used for the first boot to the virtual partition

8. Optionally, if you need to add additional files to the disk, you can copy them in this step.

9. The next step is to create a remote bootable disk, based on the virtual disk you completed in the previous step. To do that, you will use the SDImgr.wsf script, located in the Windows Embeddedutilities folder.

Open a command prompt and type the following (each command in a line):

cd “c:Program FilesWindows Embeddedutilities”
cscript SDImgr.wsf /new c:ramdisk.sdi
cscript SDImgr.wsf c:ramdisk.sdi /readpart:F:

Replace F: by the unit letter in which you mounted the virtual partition.

Note: All the explorer windows must be closed, including the Disk Management snap-in. When this procedure is running, the script tries to lock (exclusively) the partition and if some program is using it, the procedure will fail.

10. After completing the process, you will have a working remotely-bootable disk, stored on C:ramdisk.sdi. To make it deployable by the Remote Boot Manager, copy the file to C:Program FilesWindows EmebeddedRemote Boot ManagerDownloads.

The Remote Boot Manager requires the images to be stored on that location.

Configuring Remote Boot Manager

The last task to make the image remotely deployable is to configure the Remote Boot Manager to send the image to the clients whenever they request.

1. Take note of the MAC Address (comprised of 12 hex digits) for the computers that will boot remotely. If you are using virtual machines you can easily find out the client NIC’s MAC address by taking a look to the Network Adapter options.

2. Open the Remote Boot Manager, from Start | All Programs | Microsoft Windows Embedded Studio

3. For each diskless computer that will boot remotely, add a new row to the grid, using the following values

a. Type down the MAC Address of the NIC you are configuring

b. Since the Boot Server is the local machine, leave the field at 0.0.0.0

c. As the Boot Program, select the startrom.n12 option. This boot program boots the client computer without asking for confirmation. Since the client computers may not have a keyboard or monitor attached, this is the preferred choice

d. As the Image File Name type the name of the second SDI file. In this case, type ramdisk.sdi

4. Click on Save

Booting client machines

Now that you have set up the DHCP server, created the image and set up the Remote Boot Server, it is time to boot the client machines.

When configuring each client machine, verify that each machine has PXE network booting enabled.

To verify that all of the previous steps were performed correctly, try booting a machine, verifying that it is booting from PXE. After it receives the IP from the DHCP will load the image and the configuration from the Remote Boot Server.

Client receiving image from the server

Client booting the image downloaded

Well that’s pretty much for now with Windows XP Embedded. I’ll be reviewing Windows Embedded Standard 2009 on next posts.

Hope you found it useful.

Cheers

Preparing and Installing Windows XP Embedded Images – Part I: Setting up the Environment

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

58 Comments »

  1. In the section “Using SDI Loader and SDI script” note the following. Steps 1-7 are optional since there is a shortcut method available. Once you have mounted the target disk drive on the development machine, the target disk drive will be given a drive letter when the development machine is booted. You can use that drive letter as the argument to the “readpart” option in step 9. If you use this method, the partition you create for the target disk drive should be the same size as you want your final SDI image file to be which is the same size you want your ramdisk on the deployed device to be.

  2. How would you further bake things into the image? For instance, citrix client or some other third party app? Do you do that through the component designer?

  3. Hey there Arwin,

    Citrix has special clients developed for XP Embedded, you should check on Citrix home page to download those components and install them on your Database.

    The other ways are creating the component using Component Designer; or you can even try to install that app using a script each time the machine boots (not recommended though)

    Cheers!

  4. Hello Grant,

    Regarding Windows XP Embedded and Microsoft Office: it’s not actually permitted by the license to install the Office suite on any XP Embedded installation.

    Check the “Windows XP Embedded Licensing Requirements and Guidelines” at http://msdn.microsoft.com/en-us/library/ms940172.aspx

    “Device Limitations/Limited Use of Product

    Licensee may not use or include Windows XP Embedded, the Windows XP Embedded run-time images, or any components thereof, in (i) the development of a general purpose computing device or (ii) any device or system in which a malfunction of the operating system would result in foreseeable risk of personal injury, death to the operator of the device or system, or to others, or severe physical or environmental damage.”

    “Definition of General Purpose Device

    A “general purpose device” is any computer device or system whose functionality allows unrestricted use of, or access to, “Office Automation and Personal Computing Functions.” Office Automation and Personal Computing Functions refer to consumer or business tasks or processes, including (but not limited to): e-mail, word processing, spreadsheets, database, network/Internet browsing, scheduling, and personal finance. Office Automation and Personal Computing Functions include features and functions derived from Windows XP Embedded, as well as features and functions derived from other software used on the device.”

    Cheers!

  5. Hi Augusto. Thanks for the response. I guess we’ll have to find a different diskless solution. The customer has 2 workstations in remote conference rooms that they want to be diskless and run the Office suite (ie. mainly Powerpoint.)

    Thanks. Grant.

  6. hai..i have problem.can u give me are process flow cart pxe boot..
    pxe boot hard disk server windows 2003..in windows 2003 i must create image windows xp.to do that i must configure windows deploying service.the problem is before i can use wds i must have window aik.aik more to vista.but my lecture want os xp.how i want to do.can u give me idea to settel this

  7. Hello Izzat88,
    If you are looking to deploy XP Pro images with WDS, there are several things to consider since XP does not use the image native format used in WDS. For example: Windows XP is a HAL dependant OS, meaning that if you create a reference XP image, the hardware of the client machines must be the same than the reference image.
    But, there are some workarounds for that, here’s a link that might help you:
    http://www.midteq.co.uk/index.php?option=com_content&task=blogcategory&id=36&Itemid=68
    Cheers!
    Augusto

  8. Izzat88,
    Windows AIK is not a requirement for deploying images, WAIK is a set of tools to complement WDS deployment process.
    Check also the WDS section on my blog to find out more.
    Hope it helps,
    Cheers
    Augusto

  9. i can’t not boot my XPE. i have added two hardisks and do all the step given in tutoril. my fba reboots again and again and in log file the invalid drive problem is written. help plz email me

  10. Hello Augusto,

    I followed the steps of deployment part 1 & 2. After building the image files, I copied the files to an harddisk and run the harddisk as a master disk in another computer. However, it can’t boot the XPe. The computer rebooted again and again without displaying any picture/screen.
    Please help me. Thanks

      • Yes..NTLDR file was included. In the harddisk, there are 4 files (boot.ini,NTDETECT.com, ntldr and WERUNTIME.ini) and 3 folders (Documents and Settings, Program Files and Windows).
        By the way, I did not set DHCP when setting the environment (deployment part 1) because I thought it was not necessary for my machine. My step is true or not?
        Thanks for the response.

  11. Hello Dama,
    The hardware where you captured the device drivers is the same one from which you are trying to deploy it?
    It could be related to a dependency not solved, check that also.
    Cheers!
    Augusto

    • Hello Augusto,

      Thanks for the response. The hardware I captured the device driver is same with the deployed computer. By the way, the computer has successfully booted from the harddisk after editing file boot.ini regarding the harddisk and XPe run well.
      However, I still have problem. Before capturing the device drivers, I installed a device (& the driver) connected to the computer by using USB interface. After deploying, there was no driver for the USB device. Although the computer could detect the device and install the driver, but the USB device could not be accessed (message: problem in INF file). Is there any mistake in installation and deploying I did before? Could you please tell me if there is possibility to install USB device after deploying XPe in the computer.
      Thank you very much.

  12. Can someone pointed to me where is the “Citrix client for XP embedded”? I need to inclued this component in my xpe image. thanks a lot.

  13. what shall i do to add the image created to my car pc
    as to be the default operating system??
    there are no connection between my pc & the carpc
    in the meaning i made all the steps but dont know how to make this embedded created image the operating system of my carpc
    n.b i got the carpc devices.pmq & included it in the image
    but how to replace it’s current operating system with this image???
    thanks in advance :)

  14. Salama,
    If you completed the steps as above, adding all the necessary boot components (except for the RAM disk), completing the first boot; you’ll have a full booteable image to use it on your carpc.
    Cheers,
    Augusto

  15. Hello Augusto,
    Like Dama I have the same repeated reboot issue when I tried to boot the XPE files from the hard drive on the target computer the first time. I have followed the instructons carefully. But unlike Dama I have looked at the Boot.ini file and I can’t see anything wrong with it. Help

  16. and here is log file
    ———————————-
    Saturday, December 04, 2010

    9:20:14 AM – [FBASetProgressText] Setting PNP Flag…
    9:20:14 AM – [FBAFixWindowsPathsInRegistry] Incorrect WinDir: [F:\WINDOWS] should be [G:\Windows]
    9:20:15 AM – [FBAProcessRegisterDLLs] 65536054 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 72089655 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 78643256 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 104857832 -> Invalid Path: [F:\WINDOWS\fba\fbasec.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 131072241 -> Invalid Path: [F:\WINDOWS\fba\fbareg.dll]
    9:20:15 AM – [FBASetProgressText] Installing Components…
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625610 -> Invalid Path: [F:\WINDOWS\system32\txflog.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625720 -> Invalid Path: [F:\WINDOWS\system32\netshell.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625739 -> Invalid Path: [F:\WINDOWS\system32\msctf.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625740 -> Invalid Path: [F:\WINDOWS\system32\netcfgx.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625741 -> Invalid Path: [F:\WINDOWS\system32\netman.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 137625829 -> Invalid Path: [F:\WINDOWS\system32\atl.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 144179224 -> Invalid Path: [F:\WINDOWS\system32\rsaenh.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 144179225 -> Invalid Path: [F:\WINDOWS\system32\dssenh.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 196608051 -> Invalid Path: [F:\WINDOWS\fba\fbapnp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 203161652 -> Invalid Path: [F:\WINDOWS\fba\fbapnp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 232652848 -> Invalid Path: [F:\WINDOWS\fba\fbanet.dll]
    9:20:15 AM – [FBASetProgressText] Installing Components…
    9:20:15 AM – [FBAProcessRegisterDLLs] 233308187 -> Invalid Path: [F:\WINDOWS\system32\sweninst.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 235929719 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 235929771 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 242483203 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 242483250 -> Invalid Path: [F:\WINDOWS\fba\fbanet.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 249037030 -> Invalid Path: [F:\WINDOWS\fba\fbasec.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 255590449 -> Invalid Path: [F:\WINDOWS\fba\fbanet.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 262144242 -> Invalid Path: [F:\WINDOWS\fba\fbareg.dll]
    9:20:15 AM – [FBASetProgressText] Installing Components…
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912001 -> Invalid Path: [F:\WINDOWS\system32\certcli.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912002 -> Invalid Path: [F:\WINDOWS\system32\initpki.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912004 -> Invalid Path: [F:\WINDOWS\system32\colbact.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912005 -> Invalid Path: [F:\WINDOWS\system32\comaddin.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912006 -> Invalid Path: [F:\WINDOWS\system32\catsrvps.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912007 -> Invalid Path: [F:\WINDOWS\system32\stclient.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912008 -> Invalid Path: [F:\WINDOWS\system32\comrepl.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912009 -> Invalid Path: [F:\WINDOWS\system32\catsrvut.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912011 -> Invalid Path: [F:\WINDOWS\system32\es.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912013 -> Invalid Path: [F:\WINDOWS\system32\com\comadmin.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912014 -> Invalid Path: [F:\WINDOWS\system32\clbcatex.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912015 -> Invalid Path: [F:\WINDOWS\system32\comsnap.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912016 -> Invalid Path: [F:\WINDOWS\system32\comuid.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912017 -> Invalid Path: [F:\WINDOWS\system32\catsrv.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912018 -> Invalid Path: [F:\WINDOWS\system32\clbcatq.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912019 -> Invalid Path: [F:\WINDOWS\system32\comsvcs.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912020 -> Invalid Path: [F:\WINDOWS\system32\comctl32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912021 -> Invalid Path: [F:\WINDOWS\system32\initpki.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912022 -> Invalid Path: [F:\WINDOWS\system32\credui.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912023 -> Invalid Path: [F:\WINDOWS\system32\initpki.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912028 -> Invalid Path: [F:\WINDOWS\system32\rastls.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912033 -> Invalid Path: [F:\WINDOWS\system32\ddrawex.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912034 -> Invalid Path: [F:\WINDOWS\system32\dsuiext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912035 -> Invalid Path: [F:\WINDOWS\system32\qasf.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912036 -> Invalid Path: [F:\WINDOWS\system32\qcap.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912037 -> Invalid Path: [F:\WINDOWS\system32\encapi.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912038 -> Invalid Path: [F:\WINDOWS\system32\devenum.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912039 -> Invalid Path: [F:\WINDOWS\system32\quartz.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912040 -> Invalid Path: [F:\WINDOWS\system32\dsdmo.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912041 -> Invalid Path: [F:\WINDOWS\system32\dsdmoprp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912042 -> Invalid Path: [F:\WINDOWS\system32\msdtctm.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912044 -> Invalid Path: [F:\WINDOWS\system32\msdtcuiu.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912045 -> Invalid Path: [F:\WINDOWS\system32\msdtcprx.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912046 -> Invalid Path: [F:\WINDOWS\system32\mtxoci.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912047 -> Invalid Path: [F:\WINDOWS\system32\mydocs.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912059 -> Invalid Path: [F:\WINDOWS\system32\shgina.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912061 -> Invalid Path: [F:\WINDOWS\system32\h323msp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912062 -> Invalid Path: [F:\WINDOWS\system32\itss.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912063 -> Invalid Path: [F:\WINDOWS\system32\hhctrl.ocx]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912064 -> Invalid Path: [F:\WINDOWS\system32\itircl.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912065 -> Invalid Path: [F:\WINDOWS\system32\MSHTML.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912066 -> Invalid Path: [F:\WINDOWS\system32\MSHTMLED.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912067 -> Invalid Path: [F:\WINDOWS\system32\dispex.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912068 -> Invalid Path: [F:\WINDOWS\system32\IESETUP.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912070 -> Invalid Path: [F:\WINDOWS\system32\hnetcfg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912071 -> Invalid Path: [F:\Program Files\Internet Explorer\Connection Wizard\trialoc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912072 -> Invalid Path: [F:\WINDOWS\system32\inetcfg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912073 -> Invalid Path: [F:\WINDOWS\system32\MLANG.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912074 -> Invalid Path: [F:\WINDOWS\system32\comcat.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912075 -> Invalid Path: [F:\WINDOWS\system32\urlmon.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912076 -> Invalid Path: [F:\WINDOWS\system32\MSHTML.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912077 -> Invalid Path: [F:\WINDOWS\system32\MSRATING.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912078 -> Invalid Path: [F:\WINDOWS\system32\HLINK.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912079 -> Invalid Path: [F:\WINDOWS\system32\PLUGIN.OCX]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912080 -> Invalid Path: [F:\WINDOWS\system32\ASCTRLS.OCX]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912081 -> Invalid Path: [F:\WINDOWS\system32\INETCPL.CPL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912082 -> Invalid Path: [F:\WINDOWS\system32\MSHTMLED.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912083 -> Invalid Path: [F:\WINDOWS\system32\corpol.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912084 -> Invalid Path: [F:\WINDOWS\system32\proctexe.ocx]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912085 -> Invalid Path: [F:\WINDOWS\system32\MSHTA.EXE]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912086 -> Invalid Path: [F:\WINDOWS\system32\MSTIME.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912087 -> Invalid Path: [F:\WINDOWS\system32\DXTRANS.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912088 -> Invalid Path: [F:\WINDOWS\system32\DXTMSFT.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912089 -> Invalid Path: [F:\WINDOWS\system32\IMGUTIL.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912090 -> Invalid Path: [F:\WINDOWS\system32\PNGFILT.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912091 -> Invalid Path: [F:\WINDOWS\system32\ACTXPRXY.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912092 -> Invalid Path: [F:\WINDOWS\system32\INSENG.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912093 -> Invalid Path: [F:\WINDOWS\system32\IESETUP.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912094 -> Invalid Path: [F:\WINDOWS\system32\WEBCHECK.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912095 -> Invalid Path: [F:\WINDOWS\system32\OCCACHE.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912096 -> Invalid Path: [F:\WINDOWS\system32\cryptdlg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912097 -> Invalid Path: [F:\WINDOWS\system32\IEPEERS.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912098 -> Invalid Path: [F:\Program Files\Internet Explorer\HMMAPI.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912099 -> Invalid Path: [F:\Program Files\Common Files\Microsoft Shared\Triedit\TRIEDIT.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912100 -> Invalid Path: [F:\Program Files\Common Files\Microsoft Shared\Triedit\DHTMLED.OCX]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912101 -> Invalid Path: [F:\Program Files\Common Files\Microsoft Shared\MSInfo\IEINFO5.OCX]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912102 -> Invalid Path: [F:\WINDOWS\system32\MSIDENT.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912103 -> Invalid Path: [F:\WINDOWS\system32\LICMGR10.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912104 -> Invalid Path: [F:\WINDOWS\system32\digest.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912105 -> Invalid Path: [F:\WINDOWS\system32\wininet.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912106 -> Invalid Path: [F:\WINDOWS\system32\iedkcs32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912107 -> Invalid Path: [F:\WINDOWS\system32\MSR2C.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912108 -> Invalid Path: [F:\WINDOWS\system32\tdc.ocx]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912110 -> Invalid Path: [F:\WINDOWS\system32\confmsp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912111 -> Invalid Path: [F:\WINDOWS\system32\polstore.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912112 -> Invalid Path: [F:\WINDOWS\system32\mfc42.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912113 -> Invalid Path: [F:\WINDOWS\system32\mfc42u.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912114 -> Invalid Path: [F:\WINDOWS\system32\mmcndmgr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912115 -> Invalid Path: [F:\WINDOWS\system32\mmcshext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912116 -> Invalid Path: [F:\WINDOWS\system32\cic.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912117 -> Invalid Path: [F:\WINDOWS\system32\msxml3.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912121 -> Invalid Path: [F:\WINDOWS\system32\oleaut32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912122 -> Invalid Path: [F:\Program Files\Outlook Express\msimn.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912123 -> Invalid Path: [F:\Program Files\Common Files\System\directdb.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912124 -> Invalid Path: [F:\WINDOWS\system32\inetcomm.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912125 -> Invalid Path: [F:\Program Files\Common Files\System\wab32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912126 -> Invalid Path: [F:\WINDOWS\system32\msoeacct.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912127 -> Invalid Path: [F:\Program Files\Outlook Express\msoe.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912128 -> Invalid Path: [F:\Program Files\Outlook Express\wabimp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912129 -> Invalid Path: [F:\Program Files\Outlook Express\oeimport.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912130 -> Invalid Path: [F:\Program Files\Outlook Express\oemiglib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912131 -> Invalid Path: [F:\Program Files\Outlook Express\wabfind.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912133 -> Invalid Path: [F:\WINDOWS\system32\lodctr.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912134 -> Invalid Path: [F:\WINDOWS\system32\browseui.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912135 -> Invalid Path: [F:\WINDOWS\system32\cdfview.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912136 -> Invalid Path: [F:\WINDOWS\system32\devmgr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912137 -> Invalid Path: [F:\WINDOWS\system32\els.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912138 -> Invalid Path: [F:\WINDOWS\system32\licdll.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912142 -> Invalid Path: [F:\WINDOWS\system32\ole32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912143 -> Invalid Path: [F:\WINDOWS\system32\osuninst.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912144 -> Invalid Path: [F:\WINDOWS\system32\sclgntfy.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912145 -> Invalid Path: [F:\WINDOWS\system32\sendmail.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912146 -> Invalid Path: [F:\WINDOWS\system32\shdocvw.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912148 -> Invalid Path: [F:\WINDOWS\system32\rsmui.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912149 -> Invalid Path: [F:\WINDOWS\system32\rsmsink.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912150 -> Invalid Path: [F:\WINDOWS\system32\ntmssvc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912151 -> Invalid Path: [F:\WINDOWS\system32\rsmps.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912152 -> Invalid Path: [F:\WINDOWS\system32\ntmsevt.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912153 -> Invalid Path: [F:\WINDOWS\system32\rpcrt4.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912154 -> Invalid Path: [F:\WINDOWS\system32\sdpblb.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912155 -> Invalid Path: [F:\WINDOWS\system32\zipfldr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912156 -> Invalid Path: [F:\WINDOWS\system32\cscui.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912157 -> Invalid Path: [F:\WINDOWS\system32\msieftp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912158 -> Invalid Path: [F:\WINDOWS\system32\cabview.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912159 -> Invalid Path: [F:\WINDOWS\system32\snmpsnap.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912160 -> Invalid Path: [F:\WINDOWS\system32\slbiop.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912161 -> Invalid Path: [F:\WINDOWS\system32\slbcsp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912162 -> Invalid Path: [F:\WINDOWS\system32\sccbase.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912163 -> Invalid Path: [F:\WINDOWS\system32\gpkcsp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912164 -> Invalid Path: [F:\WINDOWS\system32\scredir.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912165 -> Invalid Path: [F:\WINDOWS\system32\scardssp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912166 -> Invalid Path: [F:\WINDOWS\system32\dxmrtp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912167 -> Invalid Path: [F:\WINDOWS\system32\wavemsp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912168 -> Invalid Path: [F:\WINDOWS\system32\TAPI3.DLL]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912169 -> Invalid Path: [F:\WINDOWS\system32\g711codc.ax]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912170 -> Invalid Path: [F:\WINDOWS\system32\termmgr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912172 -> Invalid Path: [F:\WINDOWS\system32\remotepg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912173 -> Invalid Path: [F:\WINDOWS\system32\cfgbkend.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912174 -> Invalid Path: [F:\WINDOWS\system32\w32time.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912175 -> Invalid Path: [F:\WINDOWS\system32\upnp.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912176 -> Invalid Path: [F:\WINDOWS\system32\upnpui.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912178 -> Invalid Path: [F:\WINDOWS\system32\upnphost.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912179 -> Invalid Path: [F:\WINDOWS\system32\upnpcont.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912180 -> Invalid Path: [F:\WINDOWS\system32\urlmon.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912181 -> Invalid Path: [F:\WINDOWS\system32\shell32.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912182 -> Invalid Path: [F:\WINDOWS\system32\fontext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912183 -> Invalid Path: [F:\WINDOWS\system32\shsvcs.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912184 -> Invalid Path: [F:\WINDOWS\system32\docprop2.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912185 -> Invalid Path: [F:\WINDOWS\system32\wiaservc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912186 -> Invalid Path: [F:\WINDOWS\system32\sti.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912187 -> Invalid Path: [F:\WINDOWS\system32\wiascr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912188 -> Invalid Path: [F:\WINDOWS\system32\wiasf.ax]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912189 -> Invalid Path: [F:\WINDOWS\system32\wiavusd.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912190 -> Invalid Path: [F:\WINDOWS\system32\gptext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912191 -> Invalid Path: [F:\WINDOWS\system32\scrrun.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912192 -> Invalid Path: [F:\WINDOWS\system32\wshcon.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912193 -> Invalid Path: [F:\WINDOWS\system32\jscript.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912194 -> Invalid Path: [F:\WINDOWS\system32\vbscript.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912195 -> Invalid Path: [F:\WINDOWS\system32\scrobj.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912196 -> Invalid Path: [F:\WINDOWS\system32\wshext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912197 -> Invalid Path: [F:\WINDOWS\system32\wshom.ocx]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912198 -> Invalid Path: [F:\WINDOWS\system32\scecli.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912199 -> Invalid Path: [F:\WINDOWS\system32\wininet.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912201 -> Invalid Path: [F:\WINDOWS\system32\wbem\esscli.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912202 -> Invalid Path: [F:\WINDOWS\system32\wbem\fastprox.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912203 -> Invalid Path: [F:\WINDOWS\system32\wbem\mofd.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912204 -> Invalid Path: [F:\WINDOWS\system32\wbem\repdrvfs.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912205 -> Invalid Path: [F:\WINDOWS\system32\wbem\unsecapp.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912206 -> Invalid Path: [F:\WINDOWS\system32\wbem\wbemcore.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912207 -> Invalid Path: [F:\WINDOWS\system32\wbem\wbemess.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912208 -> Invalid Path: [F:\WINDOWS\system32\wbem\wbemsvc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912209 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmimsg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912210 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmiprvsd.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912211 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmiprvse.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912212 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmisvc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912213 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmiutils.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912214 -> Invalid Path: [F:\WINDOWS\system32\wbem\wbemprox.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912215 -> Invalid Path: [F:\WINDOWS\system32\wbem\ncprov.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912216 -> Invalid Path: [F:\WINDOWS\system32\wbem\xml\wmi2xml.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912217 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmiaprpl.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912218 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmiapsrv.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912219 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmicookr.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912220 -> Invalid Path: [F:\WINDOWS\system32\wbem\wmidcprv.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912221 -> Invalid Path: [F:\WINDOWS\system32\wbem\wbemupgd.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912222 -> Invalid Path: [F:\WINDOWS\system32\wbem\tmplprov.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912223 -> Invalid Path: [F:\WINDOWS\system32\wbem\fwdprov.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912224 -> Invalid Path: [F:\WINDOWS\system32\wbem\updprov.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912225 -> Invalid Path: [F:\WINDOWS\system32\wbem\trnsprov.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912226 -> Invalid Path: [F:\WINDOWS\system32\wbem\policman.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912227 -> Invalid Path: [F:\WINDOWS\system32\msaatext.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912228 -> Invalid Path: [F:\WINDOWS\system32\oleacc.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912231 -> Invalid Path: [F:\WINDOWS\system32\vbisurf.ax]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912239 -> Invalid Path: [F:\WINDOWS\system32\vss_ps.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 294912240 -> Invalid Path: [F:\WINDOWS\system32\vssvc.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 327680243 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 360448244 -> Invalid Path: [F:\WINDOWS\fba\fbareg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 363725046 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBASetProgressText] Installing Components…
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001626 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001629 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001630 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001631 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001632 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001653 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001660 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001709 -> Invalid Path: [F:\WINDOWS\system32\shmgrate.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001718 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001732 -> Invalid Path: [F:\WINDOWS\system32\shmgrate.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001747 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001800 -> Invalid Path: [F:\WINDOWS\system32\snetcfg.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001837 -> Invalid Path: [F:\WINDOWS\system32\regsvr32.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 367001838 -> Invalid Path: [F:\WINDOWS\system32\regsvr32.exe]
    9:20:15 AM – [FBAProcessRegisterDLLs] 393216245 -> Invalid Path: [F:\WINDOWS\fba\fbareg.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 524288057 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]
    9:20:15 AM – [FBAProcessRegisterDLLs] 557056058 -> Invalid Path: [F:\WINDOWS\fba\fbalib.dll]

  17. hello, I have a problem
    when I install database update in windows xp mbedded sp 2
    I have this message:
    ———————————————
    Windows XP Embedded Service Pack 2 Installer

    Copying ‘Windows XP Embedded Client (x86) Service Pack 2′ repository files to \\ComputerName\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}
    Error: Cannot delete repository files in the target folder. Make sure you have write access to the files.
    Error: Cannot delete repository files in the target folder. Make sure you have write access to the files.

    The following files have not been imported:
    d:\5d2e2e80376a0da7bc03cb5c4662\cooked\XPESP2.SLD

    File(s) processed: 1, File(s) imported successfully: 0

    No objects or files were imported to the database ComputerName.

    WEUpdate Exiting with return code: 9

    **** End Of Run ****
    ————————————————————-

    please help!………..

  18. Hello Augusto,
    I bought a new lap with window embedded pre-installed 2009. When the window show up, i could not open any content from usb or disk because it seems to be locked, right click also be locked. Then i tried to install win xp, but the boot system didnt work, i come to right place and clicked on boot menu, but it run to the main window. I have no idea how to remove or reinstall new window because couldnt open folders or “my computer”. Could you help me how to do?

    • Hello John,
      If the Windows XP CD is not booting from your machine, then there’s something wrong with the media. All of the Windows XP installation media can boot from any machine with a CD.
      Check the media and try to boot again the installation.
      Cheers,
      Augusto

  19. There is a MUCH easier way to deploy these images to a local disk instead of this whole round about non-sense. The following link

    http://msdn.microsoft.com/en-us/library/bb521481%28v=winembedded.5%29.aspx

    provides all the information you need. Basically, what you need to do is create an sdi image out of the window embedded images directory that contains the latest build. The instructions above show you how to do that, and it’s very easy. Then, you need to boot DOS 6.22 on the target machine. There is a DOS 6.22 img file that you need. This site has the .img file you need:

    http://www.allbootdisks.com/download/dos.html

    Use the HP USB boot utility to create a USB bootable key with that img file.

    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-UNITY-I23839

    The sdi2hd file requires DOS 6.22 to run. Hence, you need a DOS 6.22 environment booted to run the utility.

    The next trick involves copying the .sdi file you created above and the sdi2hd.exe file (just do a search for it on the development machine) to the target device. This is tricky and has many solutions. You can’t copy it to the USB bootable key since the HP boot utility creates a MBR of 1 meg. That is, the DOS 6.22 boot usb only has a few KB of free space left on it–regardless of how big your USB thumb drive is. Here are some solutions.

    You could try to load some device drivers into DOS 6.22 that will support external USB storage devices, e.g. another USB drive. This will allow you to copy the sdi file and sdi2hd to another USB drive and use it after DOS 6.22 boots. Or, if you have a built in CD ROM drive, you could load MSCDEX drivers on DOS 6.22. This will let you see the CD Drive when DOS 6.22 boots up. The benefit of this is you will be able to burn the sdi file and sdi2hd to a CD. I’m not sure if sdi2hd requires local temporary storage. If it does, this method will not work. The way I did it was a bit roundabout.

    First, I booted up the USB DOS 6.22 thumb drive. Then I ran FDISK. I deleted all partitions on the local drive of the target device. Then I created one primary partition and one extended partition. The extended partition is created to fit the sdi file and sdi2hd file. After creating both partitions and marking the extended partition as a logical drive, I marked the primary as the active partition. After this, the target device requires a reboot of DOS. On reboot, format both drives and label. Remove the USB drive and put it into the development machine.

    Use the HP USB boot utility and create a new configuration on that drive. Choose Hard Drive. Create New Filesystem. Click HP Firmware flash package. After this is all done, copy your sdi and sdi2hd file to the USB key. Boot this USB key on your target device. It will take awhile, and you will see warning signs saying not to REBOOT during the process. However, once you see the bash shell, you are now in Linux on the target device.

    First, you need to find the extended partition and mount it. Do the following:

    type fdisk -L

    Look for the secondary partition. It should be /dev/hdc5 (look for the smaller partition, and choose the device with a star). Mount this as follows:

    mkdir /mnt/hd
    mount /dev/hdc5 /mnt/hd

    Then, copy your files over. CD to /mnt/usb and ls for the files. If the files are there, copy them over to /mnt/hd. If not, look at the other /mnt directories. Once the files are copied, type exit and shutdown. Remove the USB key and put it back on the development machine.

    Recreate the DOS 6.22 boot USB. Then reboot the target device with it. Once booted, you will now be able to CD to the D: drive. You should be able to see the sdi files there. To proceed, type sdi2hd /X. This should give you the device identifier of all the drives. Find the C: partition. The device id should be 0. If not, note the device id. Then, type this command: sdi2hd sdifilename.sdi /D0 ; or whatever the device identifier number was, e.g. /D1 or /D2. This should do a sector for sector copy of the sdi file to the local C partition.

    It works fine for me.

  20. I’ve found some more refinements to the above. The best thing to use is Freedos instead of DOS 6.22. Freedos supports USB devices such as other USB flash drives, and large thumbdrive support (it creates two partitions, one for the dos boot partition, and another that contains the other files). So, instead of creating two partitions on the local HD, one to store the sdi file, all you need to do is create a freedos boot USB drive, copy the freedos FDISK and format utilities to it from the Freedos wiki, copy the sdi2hd.exe and sdi file to the same thumb drive, and boot the target device using the thumb drive. After boot, go to the C: partition and you should see all your files there.

    You can use Unetbootin to create your Freedos USB thumb drive. Download it, select Freedos as the distribution, select your drive, and create it. Easy peasy.

  21. “7. With the partition created, move the files from the disk that was used for the first boot to the virtual partition”

    I am lost at step#7. Could you please clarify – what files need to be copied to the virtual partition.

    Your help is appreciated.

    • Those files are the image we created earlier, that were also moved to a client machine where we executed our first boot. Once the first boot is completed in that client machine, copy those files.
      Hope it helps,
      Augusto

  22. Hi Augusto, thx for the article series, was the only place that I found a detailed explaned about it.
    But I’m having a problem in the step 4 of this page(3). The Window dont finish the process and reboot, and be in this infinite loop. What could be it?

  23. Hi.
    First of all thank you very much for your contribution, I’ve found it really helpful, but I have a problem.

    I’ve been able to do the first boot and install XPe in virtual PC one time, but when I try to recreate what I did, I’m not able to do the First Boot Agent, no matter how hard I try. The only thing I need to do is to do the first boot agent to continue, but Virtual PC’s screen goes to DHCP, like if there was only a blank disk, when I know I’ve copied everything to the virtual disk.

    Could you please guide me?

    • Hello Pablo,
      Prior the DHCP boot, are you receiving an error saying that is not able to boot from drive? Try removing the option to boot from network to make sure it tries to boot from disk. Have you reviewed that the partition is “Active” in the machine?
      If that fails also, there might be a file missing in the system drive.
      Hope it helps,
      Augusto

      • I found the problem. I was doing everything using XP XP3, so I had to use some virtual machines and there was a problem in the virtual machines that wasn’t activating my virtual discs correctly, it would work sometimes and others it just stopped.
        What I did: I reinstalled my virtual machine and everything qorked properly.

  24. Hello Augusto,

    I would like to deploy my image in several machine (hard disk) but when I start my new hard disk, First boot agent don’t install component like usual. It stay in: First boot agent is starting… And always turn round… What do I done to do that correctly.
    I copied all files and folders generated in “Windows embedded image” in my new hard drive.
    I think I miss something in Target designer. But I haven’t enough experiences in Windows Embedded.
    I tried to run the same image in a second partition where Windows embedded studio is installed and it works good.

    Any Idea?
    Thanks a lot

    • Hello Luc,
      Most likely the problem is because you didn’t format the disk you are trying to use correctly. Try cleaning and creating a new partition on that disk and follow the steps again to copy the image files.
      Best regards,
      Augusto

      • Hello Augusto,

        I found the problem, it was because I put disk letter (E:) and when I moved the hard disk in my new PC, it automatically take letter (C:) in default. It was why it never access to the folders. I discovered that in FBAlog.txt.

        Thank you for the help and congratulation for this blog
        Regards,
        Luc

  25. Hi Augusto,
    I have a XP embedded system music server and company went out of business. I cloned a hard drive as back up drive. Recently I tried to migrate to a SSD and to see if this will work. I am unable to boot up the system now, even with the original drive. It always look to boot from CD Rom and unable to boot from hard drive. The system BIOS is able to read the hard drive. Can you advise what is the cause and solution to this. Thank you

    Regards,
    TF Goh

    • Hello TF,
      It will depend on the cloning process you used. It makes sense if the image is not working with a different hard drive, since you will need the proper drivers for that drive within the XP Embedded image. But if you are using the exact same drive that the image had before, then I will presume is something related to the cloning process.
      You have to remember Microsoft does not support nor recommend cloning as a valid method for deploying Windows.
      Best regards,
      Augusto

      • Hi Augusto,

        Thank you for quick reply.
        The strange thing happen was that I used back the original drive. The system still won’t recognize the hard drive. In go into In BIOS mode, I can read the drive. I did not alter the original drive.

        Regards,

        TF

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s