Compact Embedded 2012 os design doesn't see Windows Virtual PC RRS feed

  • Question

  • I successfully got Compact Embedded 2013 to build an example OS design. I installed Windows Virtual PC on my Windows 7 workstation. So today I tried to load the OS design into the virtual machine. No dice. The OS design does not appear in the Target device connectivity options -> kernel download ->  Settings windows. It is selected in the Target device connectivity options -> target device pull down menu.

    The Virtual PC starts, but acts like it can't get an IP address from DHCP. That may be part of the problem. There are two adapters on this PC. The first is not connected. The second is a wireless WIFI connector. Virtual PC displays:

    Reboot and select proper boot device.

    or Insert Boot media in the selected boot device.

    I have been following the instructions on:

    Any ideas ?



    Randy Seedle

    Sunday, September 20, 2015 12:04 AM

All replies

  • Try to follow ...

    Configure a Virtual PC
    After you have built an OS image for the vCEPC BSP, you create a virtual hard disk
    (VHD) and a virtual machine to run that OS image. Because the steps to create the
    VHD and virtual machine are different for Windows Virtual PC (for Windows 7) and
    Virtual PC 2007 (for Windows Vista and Windows XP), choose the appropriate set of
    instructions for your version of Virtual PC.
    Windows Virtual PC
    To configure Windows Virtual PC to run a vCEPC, you create a new virtual machine and
    configure this virtual machine to use the included vCEPC hard disk image.
    To configure Windows Virtual PC to run a vCEPC
    1. If you have not already done so, download and install Windows Virtual PC
    2. Start Windows Virtual PC. When Windows Virtual PC starts, it opens and displays
    your Virtual Machines folder.
    3. Click the Create virtual machine menu on the menu bar of the Virtual Machines
    folder window.
    Getting Started with Virtual CEPC 6
    © 2011 Microsoft
    4. In the Create a virtual machine dialog box, type a name for your virtual machine
    in the text box next to Name. In the following examples, we use “VCEPC” for the
    virtual machine name.
    5. In the text box next to Location, you can accept the default location for your virtual
    machine file or click Browse to navigate to a different location. The default location
    is the Virtual Machines folder, which is located at
    C:\Users\<user name>\AppData\Local\Microsoft\Windows Virtual PC\Virtual
    Click Next.
    6. In the Specify memory and networking options dialog box, you can adjust the
    amount of RAM that the virtual machine will use or you can accept the default size
    of 512 MB. To change the amount of memory, type the number of megabytes in the
    text box to the right of RAM. Click Next.
    Before you can boot an OS on your virtual machine, you must add a new or existing
    VHD image. A VHD image is a .vhd file that is stored on your physical hard disk. The
    VHD contains a boot loader and may also contain an OS, applications, and data files
    used by your vCEPC.
    To add the vCEPC virtual hard disk
    1. After you click Next in step 5, the Add a virtual hard disk dialog box appears.
    Select the option Use an existing virtual hard disk.
    2. In the text box next to Location, type the following path. Alternately, you can click
    the Browse button, navigate to this location, and then click Open.
    3. Click Create.
    If you chose the name “VCEPC” for your virtual machine, the VCEPC.vmcx file appears
    in the Virtual Machines folder.
    To start Virtual CEPC, double-click your virtual machine file (for example, VCEPC.vmcx).

    Boot the Virtual CEPC
    After you have built an OS design image that supports the vCEPC and you have
    configured Virtual PC with a virtual machine and VHD image that supports a vCEPC, you
    are ready to boot the vCEPC. To boot the vCEPC, you prepare Platform Builder to
    download your boot image, connect Platform Builder to Virtual PC, and then download
    your boot image into Virtual PC.
    Prepare Platform Builder for Boot Image
    Platform Builder downloads your OS design image (nk.bin) to a vCEPC boot loader
    running in Virtual PC. After the boot loader transfers the OS image from Platform
    Builder to Virtual PC, it boots this image in Virtual PC.
    To prepare Platform Builder for download to Virtual PC
    1. In Visual Studio, click the Target menu, and then select Connectivity Options.
    2. In the Target Device Connectivity Options dialog box, click Add Device and
    type a target device name under New target device name. For example, you
    could use “VCEPC” for your device name. For Associated OS Design/SDK, select
    Windows CE, and then click Add.
    3. Select the Kernel Service Map service configuration (if it is not already selected).
    Under Target Device, select the name of your device name (for example,
    4. Under Kernel Download, select the Ethernet option.
    5. Click the Settings button under and to the right of Kernel Download and open the
    Ethernet Download Settings dialog box as shown in Figure 3:
    Figure 3 - Ethernet Download Settings
    If you see a Windows Security Alert dialog box with the message, “Windows Firewall
    has blocked some features of this program”, you can click the Allow Access button
    Getting Started with Virtual CEPC 10
    © 2011 Microsoft
    to allow the Platform Builder CE Service Host to communicate with domain and
    private networks. Leave the Ethernet Download Settings dialog box open and
    proceed through the following steps.

    --- Misbah

    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India)

    Wednesday, September 23, 2015 11:59 AM
  • Follow Misbah's answer. In addition, you can check this link (link : ) and, as you are telling about DHCP IP problem, be careful on step 11 there :

    (PS : This is for Compact 7. Hope it holds good for Compact 2013 too.)

    Pasted here:

    11. Click on "Networking" and verify that the VirtualPC is sharing the correct network (This is important, because the virtual PC needs a DHCP server for downloading the OS image from the PB.

    Keshava G N, Software Engineer, iWave Systems, Bangalore ( ). mail - keshavagnATiwavesystemsDOTcom , blog - ,

    Wednesday, September 23, 2015 12:57 PM
  • Hi Randy,

    The Virtual PC and PC need to be on the same network so Wifi is often very bad for this.  There are a number of ways to do this but I make a closed network within my PC so that they are in the same subnet.

    As this is Compact 2013, I assume you are using the steps at  Look at the virtual switch & virtual networking setup and I suspect that will solve your issue.



    Wednesday, September 23, 2015 6:11 PM