The browser version you are using is not recommended for this site.
Please consider upgrading to the latest version of your browser by clicking one of the following links.

Intel® Embedded Media and Graphics Driver (Intel® EMGD) FAQ

Intel EMGD Configuration EDitor (CED)

Intel® EMGD Configuration EDitor (CED)

1.  What is the Configuration EDitor (CED)?

CED is a compatible graphical user interface point and click application configuration editor compatible with Windows* XP and Windows 7 (32-bit) for the Intel® Embedded Media and Graphics Driver (Intel® EMGD). It helps make setting up and building the various driver elements, including video BIOS (VBIOS), much easier.

CED allows easier pre-installation configuration and generation of the drivers and VBIOS.

Note: Although CED can be used to build Intel EMGD drivers for any target operating systems listed below, the actual CED application runs only under Windows XP and Windows 7 on the host platform.

  • DOS support (IBM PC* 2000, MS-DOS* 6.22)
  • Windows* EmbeddedCE 6.0 R3
  • Windows Embedded for Point of Service (SP3)
  • Windows Embedded Standard 2009
  • Windows Embedded Standard 7
  • Windows 7
  • Windows XP (SP3)
  • Windows XP Embedded (SP3)
  • EFI Video Driver*
  • Embedded Pre-OS Graphics (EPOG)

2.  When I attempt to run CED, it displays an error message indicating there is already a copy of CED running, but there is not—what do I do?

No. The GOP driver (also known as EFI video driver in some Intel EMGD documentation) is a replacement for legacy video BIOS and enables the use of UEFI pre-boot firmware without compatibility support module (CSM). The Intel EMGD GOP driver can either be fast boot (speed optimized and platform specific) or generic (platform agnostic for selective platforms).

This condition can occur if CED is not properly shut down. It will leave a semaphore lock file that is designed to prevent multiple copies from running. Go to the folder of Intel EMGD that you are running and open the \workspace folder and delete the .lock file you will find there. CED will run properly after you remove that .lock file.

3.  CED takes a long time to start. What is going on?

You probably have a virus scanner set to operate at runtime. CED has many files involved in loading, and the virus scan will greatly slow down the launch of CED. You can either live with the delays (safest) or instruct your virus scan program to ignore everything in the Intel EMGD directory; the latter should be done only at your own risk.



Embedded and IoT

Find in-depth documentation, tools, and resources for embedded and IoT developers.

Start designing

Contact Intel

Access technical and sales assistance, register for an account, or manage your account.

Contact us