Quark 6 Profile Processor Error

glenno · #1 09-09-2004, 04:16 AM

I am running Quark 6 on OSX 10.3.5. When opening, saving and printing from Quark docs i always get an error message stating Profile Processor Error: Bad transform, each time followed by a number, starting with (10055) and increasing by one each time, ie (10056), (10057). I have tried to upgrade to Quark 6.1 but it doesn't work either. I have searched the Quark.com support database without luck. Anyone have any ideas?

silver · #2 09-15-2004, 05:27 PM

I got the same error after messing around with my monitor display profiles. I changed my profiles back to previous locations and settings, but the error concists. My setup is exactly the same as yours.
When quitting Quark, I get the error twice before it quits... Another reason for looking to InDesign... sigh.

silver · #3 09-15-2004, 05:55 PM

problem resolved?
I deleted User Cache, System Cache, System Logs, Application Logs, Temp files and Virtual Memory files followed with a restart and the problem was gone.

you can use onyx to do these operations easy:
http://www.versiontracker.com/dyn/moreinfo/macosx/20070

update:// the error is back opening a document saved when the error was present. now I get the error three times upon quiting quark...

update:// tried deleting Xpress Preferences, didn't work, deleted Quark CMS Preferences, didnt work. But then I deleted ALL the Quark Preferences, restarted Quark, updated the profile manager, defined new path for Auxiliary Profile Folder, leaving ALL the profiles ON, then the PROBLEM IS GONE!

update:// Forget it, the error is back...

silver · #4 09-15-2004, 07:53 PM

I think it might have something with the Euroscale Coted v2 profile... I'll try to investigate some...

glenno · #5 09-23-2004, 05:26 AM

The only way to get rid of it is to turn off quarks cms, but than you can't color manage files. Recreating your colorsync profiles doesn't help. i am so tired of this.....

silver · #6 09-23-2004, 05:52 AM

I am totally with you. Have tried everything. I think it has to do with corrupt profiles as the problem occured for me when I fixed my profiles (...). trashing of all prefs and trying with two different xpress´ and doing all system fixes known to man doesn't seem to work.

please please keep posting any info of this. it's sooo annoying.