- This topic has 2 replies, 2 voices, and was last updated 16 years ago by
mgb123.
-
AuthorPosts
-
April 20, 2009 at 10:38 pm #376026mgb123Participant
I’ve repackaged the entire CS3 suite minus Version cue, and I can’t seem to get it to launch without it asking to be ‘repaired’ at each launch.
So long as I’m logged in as an admin user, I’m able to do this just fine.
If I’m a normal, non-admin user the app will crash – unless I authenticate with admin credentials.
Has anyone else seen this with their packages?
I’ve attempted to repair permissions post imaging, I’ve tried rebuilding my package, and I’ve ensured that I launched each CS3 app prior to install.
No matter what I do, I can’t get it working.
For what it’s worth, I install CS3 AFTER my office package- perhaps it’s the plugin’s for office.
I thought I should reach out to you all while my image rebuilds with the packages re-ordered.
April 22, 2009 at 3:31 am #376031Patrick FergusParticipantYour issues probably lie in missing files, folders, symlinks, or Acrobat self-heal. Your intuition about Office plugins is probably right–Acrobat launches and discovers that “omigosh, Office is installed!”
To work around this, first try using [url=http://www.fernlightning.com/doku.php?id=software:fseventer:start]fseventer[/url] to watch what happens when you authenticate. Then install your CS3 package again and [i]slowly[/i] go through the changes recorded by fseventer. You’ll probably find items that need to be included in your pkg, probably multiple items. Once you find what you need, make the necessary changes to your pkg and retest.
If that doesn’t work, see the [url=http://filewave.org/viewtopic.php?t=643&sid=6dc889d4ed2e358b94ccf62876fd2328]OS X – Adobe CS3 Fileset Construction[/url] whitepaper from [url=http://filewave.com/]FileWave[/url].
If that fails, see post #5 regarding [url=https://www.afp548.com/forum/viewtopic.php?showtopic=20822]Adobe Reader[/url].
FWIW, Acrobat 8.1.4 seems to finally relent and agree to [i]not[/i] install the PDF browser plugins and Office ’08 plugins when you tell Acrobat to [i]not[/i] do it in the future. You may not need to edit the self-heal files by hand any more.
– Patrick
April 23, 2009 at 9:25 pm #376052mgb123ParticipantPatrick,
I stripped our image down to simply a CS3 install with Acrobat and Photoshop. This helped eliminate a number of potential vectors for investigation.
In the end, with a clean install of OS X.5.6, and Acrobat/Photoshop, it turns out Acrobat really, really, really wants r/w/x access to /Library/Colorsync/Profiles.
This is set to ‘REQUIRED’ in the self heal XML file in /Library/Application Support/Adobe/Acrobat/ .
If you set that required to ‘NO’ – Acrobat will still attempt to self heal, it just won’t attempt fail after seeing that it doesn’t have r/w/x access.
I’m putting Office back into our build, and it’s my hope that it won’t try to force it’s way into getting it’s greedy little self heal mitts on that as well.
If it does, we’ll simply edit the self head doc as well.
I packaged the self heal doc as it’s own pkg, just in case I do end up having to go back and make subsequent edits.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed