1. VideoWinCE301001.zip Driver
2. FAQ.TXT File Contents

FAQ.TXT Driver File Contents (VideoWinCE301001.zip)

************************************************************************
* 
* 
* Information in this document is provided in connection with Intel 
* products. No license, express or implied, by estoppel or otherwise, to any
* intellectual property rights is granted by this document. Except as
* provided in Intel's Terms and Conditions of Sale for such products, Intel 
* assumes no liability whatsoever, and Intel disclaims any express or implied 
* warranty, relating to sale and/or use of Intel products or this document, 
* including liability or warranties relating to fitness for a particular 
* purpose, merchantability, or infringement of any patent, copyright or other 
* intellectual property right. Intel products are not intended for use in 
* medical, life saving, or life sustaining applications. 
* 
* Intel may make changes to specifications and product descriptions at any 
* time, without notice. 
* 
* 
* Copyright(C) Intel Corporation 2001. 
* 
*   *Third-party brands and names are the property of their respective owners. 
* 
*
************************************************************************

Frequently Asked Questions:
----------------------------------------------

Q. Will this driver work with Microsoft Windows* CE version 2.0? 
A. No, this driver was developed and tested with Microsoft Windows CE 
version 2.12 and 3.0.

Q. Does this driver work with Intel's 69000/65555 video controller
chip? 
A. No.

Q. How do I install this driver? 
A. The installation procedures are described in the "Installation" section 
of the release note - release.TXT.

Q. Why does the resolution change to 1024x768 mode when I use the loadcepc /D:2 switch?
A. The driver reads the Registry settings for the CxScreen and CyScreen, you need to modify the settings based on the resolution you wish. Refer to the release.txt file for the settings.

Q. Will the driver work in 24 bit per pixel mode? 
A. Yes, the registry entry for "Bpp" can be changed to 18 which will run in 24 bits per pixel. Check the release.txt file for the settings which can be selected.

Q. Is there a way to change my video settings while running Windows CE.
A. No. You must change the registry settings prior to building the image.

Some common problems and their solutions:
-------------------------------------------------------------------------

Problem 1: - Downloading the Microsoft Windows CE image from the
development system to a target system fails.

Solution 1: 
- If your target system is a PC, make sure your BIOS has the
  PARALLEL PORT set to bi-directional. 
- If your target system is a PC,
  check that the LOADCEPC.EXE utility that came with Microsoft Windows CE
  version 2.12 or 3.0 is the one loaded on the hard drive. 
- Check the parallel cable. The parallel cable may be at fault. Disconnecting 
  the parallel cable with power on either end will damage the cable.


Problem 2: 
- The Microsoft Windows CE version 2.12 or 3.0 image fails to boot
  properly and it displays an error message which indicates it does not
  fit into memory.

Solution 2:
- If your target system is a PC, remove any statement which loads 
  SMARTDRIVE from the CONFIG.SYS and AUTOEXEC.BAT files.

Problem 3:
- The resolution will not go to anything but 640x480 16 bit per pixel mode.

Solution 3: 
- Check the registry for the "CxScreen" and "CyScreen" and "Bpp" settings; 
  if any of them are incorrect the driver will default to 640x480 16 bit per pixel mode.
- If there is not sufficent video memory then the default mode is automatically 
  selected (640x480 16 bit per pixel mode).

Problem 4:
- I do not get the refresh rate that I specify in the registry.

Solution 4:
- The refresh rate setting only works in CRT mode, if you are using Simultaneous 
  mode (CRT and Flat Panel together) then the refresh rate is 60Hz.
- Change the "DisplayDevice" registry setting to 0:CRT to enable 
  support for various refresh rates.

Problem 5:
- I cannot find the \installdir\PLATFORM\CEPC\TARGET directory.
Solution 5:
- The TARGET directory does not get created until the first time you create a build. Use the default MAXALL project and run the blddemo program, once you do this the TARGET directory will be created.