To illustrate the required process, Kennett uses an example of a device that has a display, but no standard input. Handling this situation might require replacing certain Core DLL components that depend on standard input, according to Kennett. For example, modules such as "ShowErr" expect to put up a dialog box and get input when error conditions occur. Thus, it becomes necessary to replace ShowErr with a version that simply outputs a message without expecting input.

Learn more about customizing Windows CE 6.0, by reading the complete whitepaper:


Replacing a COREDLL component in Windows CE 6.0

---

Related stories:

• Understanding Windows CE "SDKs"
  
• Windows CE6 drivers: what you need to know
  
• What is virtual memory?
  
• Memory marshalling in Windows CE
  
• Differences between Windows CE 5.0 and Windows CE 6.0
  
• Video introduces 3rd-generation Windows CE kernel
  
• Understanding the Windows CE variable tick timer
  
• Online videos and labs introduce Windows CE 6.0
  
• Understanding memory sections and the OEMAddressTable in Windows CE 5.0 and 6.0
  
• Will Windows CE 5.0 apps run on Windows CE 6.0?
  
• Understanding Windows CE 6's device driver model
  
• Online video shows how to build Windows CE 6 OS images