Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Building Your First Windows Embedded Standard 2009 Test Image

4/24/2012

Microsoft Corporation

March 2009

This technical article contains information about two common scenarios for building and deploying a basic test image for target hardware.

This technical article is a basic guide to creating, building, and deploying a test image onto target hardware. As a "getting started" article, it will make some assumptions about the environment you will be working in, based on two common development scenarios. It will not cover all possible types of configurations, settings, media, or deployment methods.

Scenario One has the following assumptions:

  • Windows Embedded Studio is installed locally on a development workstation.
  • The development workstation is running Windows XP or Vista x86.
  • The development workstation can connect to an IDE compact flash reader, to insert a compact flash card as a second drive.
  • A second computer is available as the destination computer.
    The destination computer has an IDE compact flash reader and compact flash card of at least 256MB.

Step 1: Create a Configuration

  1. On your development workstation, Click Start, point to All Programs, click Microsoft Windows Embedded Studio, to open Target Designer.

  2. On the File menu, click New. The New Configuration dialog box appears.

  3. Type a configuration name, for example, Test1, and then click OK.

  4. In the Category View of Component Browser (left pane), expand Software, and then expand Test and Development.

    Dd569707.5156cba6-6ab2-4958-b004-753d31770fb4(en-us,MSDN.10).gif
  5. Double-click Winlogon Sample Macro to add the component to your configuration.

Step 2: Configure Settings

  1. In the Configuration pane (middle pane), expand the Winlogon Sample Macro component.

  2. Click the Settings node, and then clear the selection for FAT and FAT Format in the Details pane (right pane).

  3. At the top of the Test1 node, select Settings.

  4. Under Target Device Settings, select Show.

  5. Verify the settings have the following values (default settings):

    Setting Value

    Startup drive

    C:

    Windows folder

    C:\Windows

    Program Files folder

    C:\Program Files

    Documents and Settings folder

    C:\Documents and Settings

    Boot ARC path

    multi(0)disk(0)rdisk(0)partition(1)

    Boot partition size (MB)

    1024

    Partition cluster size (bytes)

    4096

    Dd569707.aacd8956-9110-4971-a934-692185270162(en-us,MSDN.10).gif

Step 3: Check Dependencies

  1. On the Configuration menu, click Check Dependencies.

    The dependency check may run for several minutes or longer, depending on the performance capabilities of your computer.

  2. When the dependency check is complete, click Close.

Step 4: Build Image

  1. In Target Designer, on the Configuration menu, click Build Target Image.

    The Build Test 1.slx dialog box appears.

  2. Specify a subfolder called Test1 under the default build location: C:\Windows Embedded Images.

  3. Specify the log file name as Test1.log, in the default location.

  4. Select Build.

  5. After the build is complete, click Close.

  6. On the File menu, click Save As, and specify a location to save the configuration file.

  7. Close Target Designer.

Step 5: Prepare Media

  1. On the development workstation connect the compact flash (CF) drive from the destination computer to the compact flash reader.

  2. Click Start, click Run, type Diskpart.exe, and then click OK. In the Diskpart Command Prompt window prepare the CF as follows:

    1. List Disk
    2. Select Disk x where x is the CF drive (Use caution- do not to run the Diskpart commands on the incorrect drive)
    3. Clean (you may receive a warning "All data will be lost". Click "Y")
    4. Create partition primary
    5. Active
    6. Format fs=FAT quick
    7. Exit
      Dd569707.7f07f1f5-84e5-4fd4-acb7-abe9d614b57d(en-us,MSDN.10).gif

Step 6: Deploy Run-Time Image

  1. In Windows Explorer, locate your run-time build directory, for example, C:\Windows Embedded Images\Test1.

  2. Copy the contents of the build directory to your compact flash drive.

  3. After copying is complete, remove compact flash drive and reinsert in the destination computer.

Step 7: Run Setup

  • Start the test computer.

    The Windows XP splash screen is displayed and First Boot Agent (FBA) starts.

    FBA restarts as soon as Setup is complete and you see your run-time image desktop.

Scenario Two has the following assumptions:

  • Windows Embedded Suite of Tools is installed locally on a development workstation.
  • The development workstation is running Windows XP or Vista x86.
  • A second computer is available as the destination computer.
    This computer has an IDE or SATA hard disk that has Windows XP Professional installed on the first partition (C:).
  • A second, empty partition of 1G is formatted NTFS.
  • This computer has a USB slot, and the developer has a USB Flash Drive (UFD).
  • The destination computer can connect to a network share or can be connected to the development workstation.

Step 1: Analyze Hardware

  1. Copy Tap.exe from C:\Program Files\Windows Embedded\Utilities to the UFD.

  2. Insert the UFD in destination computer and run Tap.exe.

    A file named Devices.pmq is saved to the UFD.

  3. Insert the UFD in your development workstation.

Step 2: Create a Configuration

  1. On the development workstation, click Start, point to All Programs, and then click Microsoft Windows Embedded Studio, to open Target Designer.

  2. On the File menu, click New. The New Configuration dialog box appears.

  3. Type a configuration name, for example, Test2, and then click OK.

  4. On the File menu, click Import.

  5. Locate the Devices.pmq file on the UFD, select it and then click Open.

  6. When the Import File dialog box appears, click Start.

  7. As soon as the import has finished, click Close.

  8. Select List View in Component Browser (as shown in the following figure).

  9. Scroll to Kiosk/Gaming Console macro and double-click to add it to the configuration.

    Dd569707.d2506702-c114-415a-83b4-e737cbf3a898(en-us,MSDN.10).gif
  10. In the Component Browser's Search text box, type the first few letters of the Administrator Account component. As soon as the file is highlighted, drag it into the configuration pane.

  11. Add the Windows Logon (Standard) component in the same manner.

Step 3: Configure Settings

  1. At the top of the Test2 node, select Settings.

  2. Under Target Device Settings, select Show.

  3. Verify the settings have the following values (default settings):

    Setting Value

    Startup drive

    C:

    Windows folder

    D:\Windows

    Program Files folder

    D:\Program Files

    Documents and Settings folder

    D:\Documents and Settings

    Boot ARC path

    multi(0)disk(0)rdisk(0)partition(2)

    Boot partition size (MB)

    1024

  4. In the Configuration pane expand the Kiosk/Gaming Console component.

  5. Click Settings and clear the selections for Dialer Application, Dial-up Networking Common Libraries, and Dial-up Client for Windows in the Details pane.

  6. In the Configuration pane, expand the Administrator Account component.

  7. Click Settings, and enter a password in the text box in the Details pane.

Step 4: Check Dependencies

  1. On the Configuration menu, click Check Dependencies.

    The dependency check may run for several minutes or longer, depending on the performance capabilities of your computer.

  2. When the dependency check is complete, view the Tasks tab in the Output pane at the bottom of Target Designer.

  3. Double-click each dependency task, on the Tasks tab, that could not be automatically resolved by Target Designer because it requires a choice by the user.

    Enter values for each task as follows:

    Setting Value

    The HAL component (for example: ACPI Multiprocessor PC, Standard PC)

    Select NTFS

    Regional and Language Options

    Select English Language Support

    User Interface Core

    Select NTFS Format

    Windows Logon (Standard)

    Select Explorer Shell

  4. Rerun a dependency check to resolve the dependencies of the newly added components.

  5. Complete any additional Tasks as needed.

Step 5: Build Image

  1. In Target Designer, on the Configuration menu, click Build Target Image. The Build Test2.slx dialog box appears.

  2. Specify a subfolder named Test2 under the default build location: C:\Windows Embedded Images.

  3. Specify a log file that is named Test2.log, in the default location.

  4. Select Build.

  5. After the build is complete, click Close.

  6. On the File menu, click Save As and specify a location to save the configuration file.

  7. Close Target Designer.

Step 6: Deploy Run-Time Image

  1. In Windows Explorer, locate your run-time build directory, for example, C:\Windows Embedded Images\Test2.

  2. Share the Windows Embedded Images folder and make sure that the destination computer has permissions to the share.

  3. On the destination computer, connect to the Windows Embedded Images share.

  4. Copy the contents of the Test2\DriveD folder to the second partition on the destination computer.

    Dd569707.afd1ca26-3aa6-4bf8-9255-e39100772c05(en-us,MSDN.10).gif

  1. On the development workstation, connect the hard disk from the destination computer to the IDE slot of the development workstation.

  2. Copy the contents of the build directory to the second partition of the destination computer’s hard disk.

  3. After the copy is complete, remove the hard disk and reconnect it to the destination computer.

Step 7: Run Setup

  1. Restart the destination computer.

  2. Change the C:\Boot.ini file as follows (this file is a system file and may be hidden):

    [boot loader]
    timeout=15
    default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Embedded Standard" /fastdetect
    
  3. Save the Boot.ini file and restart the computer.

    The boot options will display for 15 seconds, then the system will start into the Windows Embedded Standard image.

    The Windows XP splash screen is displayed and FBA starts.

    FBA restarts as soon as setup is complete and you see the logon screen for the run-time image.

What you have learned

By using the information in this technical article, you should now have a better understanding of building and deploying basic test images for target hardware.

Show:
© 2015 Microsoft