Sounds like there are at least two reasons why you may not get the colors from PTE that you expect: When you use a puck and its software on your display, the software guides you to adjust display settings such as brightness and contrast and it creates a profile file for the display. The profile contains two classes of data: global settings (such as gamma values) to be loaded into your video adapter and tables, coefficients, etc. that programs can use to map colors from an image's color space to the color space of your display. To get the most accurate colors possible on a display, you need to: 1. Run the puck's software to set the display's settings to the right values and create a profile 2. Arrange that the global settings in the profile will be loaded into your video adapter hardware. (The puck's software will typically do this. On Macs, it just has to set the profile as the default profile for the display. On WinXP, it sets up a program to run at startup to do it -- that is why you may see your display color change at some point during startup.) Of course, this assumes that if you load the settings into the video adapter, it will use them. Evidently, some ATI adapters ignore the settings for some or all of the 3D operations that PTE uses. This is the first reason that PTE may not give the colors you expect. As noted in other posts in this thread, turning off 3D can be used to see if this is happening for you. 3. Arrange that when an image is displayed, the RGB values are mapped from the image's color space to the display's color space. That is, for each pixel in the image, a color engine uses the profile that defines the image's color space and the profile that defines the display's color space to map the pixel's RGB value in the image to the RGB value that will produce the same color on the display. The easy way to achieve #3 is to use a color management aware (CMA) program, such as Photoshop, which is aware of the color spaces of the image and the display and does the mapping on-the-fly whenever it sends the image to the display. Unfortunately, most programs are color management naive (CMN) -- they just send the RGB values from the image to the display. In order to see as-accurate-as-possible colors with a CMN program, you have no choice except to convert the image to the display's profile _before_ presenting it to the program (e.g. make a copy of the image, use Photoshop's Convert To Profile command on it, then give it to the CMN program). From empirical tests, I have determined that PTE is CMN. (Igor: please correct me if I am wrong.) Thus, the second potential reason that people don't get the colors they expect is that they don't realize that PTE is CMN. For example, you have an AdobeRGB image that looks right when viewed in PS, but not in PTE. The workaround is to convert the image to the display's color space as described above. Similarly for the photo club projector issue: if you are using PTE for your presentation, you should generate a copy of the presentation from images that you converted to the _projector's_ color space. Note: this is what you should do to display the most accurate colors. In practice, just having the display or projector calibrated (that is, the display's settings are properly set and the global settings from the profile are loaded into the video adapter) will often result in acceptable colors. Of course, it depends on how similar the image's color space is to the display's color space. I hope that a future version of PTE will be CMA so that we will no longer need to have multiple copies of our images. A third reason you may not get the color you expect is out-of-gamut colors. This is especially likely in the projector case since typically projects have smaller gamuts than computer displays. Well, I've rambled on enough for now.... Cheers Karl