1. What is the Configuration EDitor (CED)?
CED is a Windows* XP-compatible graphical user interface “point and click” application configuration editor for the Intel® Embedded Graphics Drivers. It replaces the more cumbersome and manual profile configuration file (PCF) method of configuring and building Intel Embedded Graphics Drivers. It helps make setting up and building the various driver elements, including video BIOS (VBIOS), much easier. It replaces the PCF/PCF2 Intel Embedded Graphics Drivers configuration process. Online help and logically grouped features, plus error checking, assure your configuration is right the first time built.
The Configuration EDitor (CED) allows easier pre-installation configuration and generation of the drivers and VBIOS.
Note: Although CED can be used to build Intel Embedded Graphics Drivers for any target operating systems listed below, the CED application runs only under Windows XP on the host platform.
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?
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 Embedded Graphics Drivers that you are running, then go into 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 Embedded Graphics Drivers directory; that should be done only at your own risk.
4. How do I see the configuration file that is generated by CED?
Sometimes, for debugging purposes, you would like to know which configuration file is generated by CED. By having access to the config file generated by CED (iegd.inf, xorg.conf, user_config.c, iegd.reg), you can rule out configuration issues. This feature is also useful when you just need the configuration file (especially in VBIOS) and not the whole driver / VBIOS package.