percepts
05-23-2010, 06:15 AM
Just got a new and very basic monitor for an old W2K setup I run.
Monitor works fine but....
I have generated a new .icm profile for the monitor using adobe gamma. Saved the profile into WINNT/SYSTEM32/SPOOL/DRIVERS/COLOR
When the profile is saved it is immediately active and makes the monitor look as I want.
Control Panel/display/settings/advanced/color manangement is set to pick up the new profile.
Problem is that when I reboot, the system is not using my new profile. It is picking up a default sRGB profile from somewhere but I have no idea why or where it is getting it from.
So I booted in safe mode and copied my profile into dllcache and into all the other copies of it on my pc. But still the problem occurs.
So my question is, how do I stop this from happening and where is W2K getting the profile it's using from.
I over wrote the original srgb.icm but have replaced it with my new profile in all copies of it on my pc.
I'm really stumped on this one. It worked fine on my old monitor.
Monitor works fine but....
I have generated a new .icm profile for the monitor using adobe gamma. Saved the profile into WINNT/SYSTEM32/SPOOL/DRIVERS/COLOR
When the profile is saved it is immediately active and makes the monitor look as I want.
Control Panel/display/settings/advanced/color manangement is set to pick up the new profile.
Problem is that when I reboot, the system is not using my new profile. It is picking up a default sRGB profile from somewhere but I have no idea why or where it is getting it from.
So I booted in safe mode and copied my profile into dllcache and into all the other copies of it on my pc. But still the problem occurs.
So my question is, how do I stop this from happening and where is W2K getting the profile it's using from.
I over wrote the original srgb.icm but have replaced it with my new profile in all copies of it on my pc.
I'm really stumped on this one. It worked fine on my old monitor.