Datacolor User to User Support Group.

Yes, I think that is exactly what it refers to. It is apparently part
of the Vista Windows Color System (WCS) and used for displaying sRGB
files. When I try to delete the file, Windows gives me an error
message saying it is part of the system and cannot be deleted.

The problem would appear to be that it somehow got into the SpyderPro2
list of profiles associated with the monitor, and it is not an
appropriate ICC profile for the monitor, hence the SypderPro error
message. I need to get it out of the SpyderPro list somehow.

--- In colorvision_group@yahoogroups.com, "LAURIE " <laurie@...> wrote:
>
> Doesn't D65 refer to a color monitor profile for a 6500 Kelvin color
> temperature setting on the monitor?  I do not know what you mean by
saying
> it is a system file.  It may be an inbox generic or a brand/model
specific
> monitor profile that comes with the OS.  I would assume that you could
> disassociate that profile by going to the display section of the OS's
> Control Panel under the Properties tab.
> 
>  
> 
> From: colorvision_group@yahoogroups.com
> [mailto:colorvision_group@yahoogroups.com] On Behalf Of Dan Finnerty
> Sent: Saturday, May 03, 2008 11:37 PM
> To: colorvision_group@yahoogroups.com
> Subject: [colorvision_group] Profile Chooser - bad profile list in
Profile
> Chooser
> 
>  
> 
> Using Vista 64, with dual monitors and SpyderPro2, I am getting an
> error message when I open ProfileChooser.
> 
> I get an error dialog box on the second monitor saying:
> C:\Windows\system32\spool\DRIVERS\COLOR\D65.camp - Error 2011 The
> specified color profile is invalid. 
> 
> Clicking on OK, I get two more error dialogs saying: Error 87 - The
> parameter is incorrect. 
> 
> In the list of profiles for the second monitor, I see D65 as one of
> the profiles associated with the monitor. This is a system file and
> should not be in the list, I think, hence the error messages. Any
> ideas how I remove it from the list of profiles associated with the
> monitor?
> 
> I suppose I could uninstall and reinstall Spyder2Pro, but who knows if
> that will clear the problem...
>