Re: Monitor Profiles Missing
Re: Monitor Profiles Missing
- Subject: Re: Monitor Profiles Missing
- From: Doug Brightwell <email@hidden>
- Date: Mon, 06 Aug 2001 13:58:22 -0700
Several people contacted me off-list, and I wanted to thank them and bring
you all up to date in case this is of interest/benefit to others:
Following up on Neil's kind offer to inspect the profiles, I sent him two of
the ones that were not showing up in the Monitors control panel. Got his
response back this morning:
On 8/6/01 1:17 AM, "neil snape" <email@hidden> wrote:
>
Doug, I looked everywhere I could. Profile Manager said everything was fine
>
and Colorthink as well. I tried then to edit the profiles in Linocolor and
>
it said the A2B0 tag was missing. Don't know that that's important as in
>
reality perceptual doesn't really exist for monitors.
>
I deleted the private tags in Ben Griffith's profile editor and low and
>
behold they're back. Now I'll just have to reset my Mitsu to where it was!
I copied the profiles that Neil edited into my ColorSync folder, and right
away, they showed up in Monitors. Hurray! Thank you Neil!
Of course, I will re-calibrate and move on with my life. The monitors were
due for re-calibrating anyway. I just want to understand how this all works,
and how I can avoid it in the future.
Neil found two tags in the profiles named "TCPt" and "mmod" and both labeled
as "private (secret sauce)".
Shane at ColorVision tech support has never heard of those tags, and said
that Optical doesn't place them in the profile. His speculation was that
perhaps my previous system, Mac OS 9.0.4, had created them at the system
level for some system function, and that my new system OS 9.1 works
differently and hence couldn't read the profiles.
Does that make any sense or sound plausible? Doesn't make sense to me unless
there are a lot of Mac users out there discovering when they upgrade to 9.1
that all their monitor profiles no longer work. Anybody ever seen those tags
or know what do they do? If Optical doesn't create those tags, what does? Is
it typical behavior of the Mac OS to create new tags in profiles as part of
its management duties?
Shane also didn't like the fact that I didn't have the Optical startup
extension in my new system folder. I told him I didn't have it in my old
system folder either, because I vaguely remember someone on this list
mentioning that it was unnecessary, and in some situations undesirable to
have it. Also, I was trying to reduce my system to as few extensions as
possible to keep the newly released PhotoShop 6.0 from crashing on launch,
and when Adobe tech support was denying that there were any bugs that would
cause it to crash in the manner I was experiencing. Interestingly, the 6.0.1
update works just fine. But, I digress.
The question is: should I use the Optical Startup extension or not?
In either case, I don't think that was the cause of the profiles not being
recognized, because once Neil removed the private secret sauce tags, the
profiles worked without the extension in place. It seems clear to me that it
was the presence of those tags that caused the problem. If I knew how they
got there, I could prevent this from happening again.
Finally... Is there a freeware or shareware profile inspector out there that
I can use to inspect the new profiles I create to see if and when these tags
reappear?
Thanks again for everyone's thoughts, and my apologies for being long
winded...
Doug
--
Doug Brightwell
email@hidden