Learn how to optimize Photoshop for maximum speed, troubleshoot common issues, and keep your projects organized so that you can work faster than ever before!
In fact I am seeing a huge speed boost over 10.2.8. Everything. Especially screen redraw and file I/O! My old machine feels as responsive as it did with OS 9.
Yes. If photoshop is healthy update system to 10.3.4 then photoshop won’t launch I assume the 10.3.4 or its installer mucked with something that it shouldn’t have.
that much is obvious. How to fix is the question. How many others have same problem and what are the commonalities? (I have PS on another volume, for instance)
I know it’s not Photoshop. I have another boot drive with 10.3.2 and Photoshop CS works just fine if I boot from that. You’d think I would have learned after the 10.2.8 disaster. But no.
Roland your computer is F’d up the system update works fine as do Photoshop 7 and CS. You most likely need to do an Archive and install to get a clean system. then apply the 10.3.4 update. everything works as it should, its just your setup.
That may well have been the problem. It seems that OSX does not like you to move things from their appointed place: applications need to be in the Applications folder for example.
I’ve actually gotten Photoshop (7) that is installed on a 10.2.8 volume to run by invoking it from the 10.3.4 partition on which no applications have yet been installed.
Turns out no combo of utilities or re-running installer worked. The first install stepped on a file that PS needed. Only cure was to re-install PS. All ok now. It’s not surprising that many didn’t have the same experience. Installers have been known to do different things to different setups.
Same problem. I tried re-installing CS, didn’t work. Tried dumping prefs in CS. I booted up from OS 9.2 and the Photoshop 7 I have there works just fine.
Did you (a) trash the prefs before attempting to reinstall? (b) Did you remember to Repair Permissions before and after installing any new software (including the OS and Photoshop) at each step of the way?
might have just been superstitious, but I ran every utility I had before reinstalling PS and I installed it on a different volume. I was afraid that installing directly over an old install might not get it fresh.
I also reinstalled the 10.3.4, killed all caches, and jumped up and down on one foot while patting the top of my head.
coulda been just resinstalling PS on a different volume, but you never know. It might have been the head pats.
there are several places to look, but in the prefs, look for .plist with files related to photoshop. I went through looking for prefs files and nuked a few of them.
Trashing the .plist files and reinstalling worked. Any preferences I had will have to be reset as copying them back causes Photoshop to not load again.
I don’t don’ t know if the OS X 10.3.4 updater effected the other apps in the suite – InDesign seems to launch okay.
3 hours was about my total effort also. As I posted before, I was also jumping up and down on one foot and patting my head for good luck. I think that a prior suggestion that one wear wingtips while updating has merit. I’m sure it would speed things up.
I have no way to prove this (long distance), but your pattern and seriousness of problems leads me to think you have a hardware problem or a font problem.
Delete every vestige of photoshop and its support and prefs files. Delete the plist files again.
Do a search for "adobefnt." Delete all of them. But don’t delete "AdobeFnt.db" Take all fonts off your machine other than Adobe Type I. Get FontAgent Pro. Use it to check (and manage) the fonts you keep. Discard any fonts it finds damaged.
Get Cocktail. Run ALL the utilities it has, including re-prebind and repair permissions.
Restart. Reinstall Photoshop. Run Cocktail again.
If the problem still happens, I’m afraid it IS a hardware issue such as a memory stick that just can’t handle Photoshop (although every other program on your machine may run ok). Or a marginal connector or drive issue. Unfortunately, Photoshop has (in addition to its known attributes) become the supreme non-destructive hardware test for Macs.
I wouldn’t jump to hardware. I started this thread when 10.3.4 hosed Photoshop and had to discover by trial and error (and supertitious rituals) the things that lead to a happy ended. Hardware was not the problem. 10.3.4 and/or the last security update seem to step on files sometimes and corrupt them. Cleaning out prefs, running utilities, nuking caches, etc., and then reinstalling worked for me.
Buko, The point of the thread is that the update steps on one or more files that Photoshop needs in SOME cases. Declaring that ‘your system is messed up’ isn’t helpful. Helping determine what steps might be taken to return PS to functioning IS helpful.
I disagree. Other than a hardware problem, Eden’s system IS messed up, and may need a complete reinstall to clear out the corrupt file(s). But we also haven’t heard whether logging in as a new user has any bearing on the problem.
In the few cases (now, more than just my own), the files that the OS updater stepped on affected all users, so that’s not a worthwhile test. The files were fixed by some vigorous housecleaning, removal of prefs, and reinstall of PS.
But for the majority of users, (my unofficial, unscientific, pseudo-random poll of various sites reporting experiences with the update) the update has IMPROVED performance. This leads me to believe that on systems experiencing problems, corrupt files already existed that caused the updater to stumble.
We can get into all kinds of valid discussions about the updater’s needing to be dependable and robust enough to test the target system for integrity before trying to install. But absent that capability, we DO have utilities like Cocktail which gets our house in order before something as significant as an OS tweak.
I believe that people having problems at this time had system problems which simply had not surfaced (yet) or hardware problems waiting to rear their ugly selves.
If we have learned nothing else during the evolution of OS X and Photoshop, and especially their existence together, EVERYTHING about hardware and software has to be squeaky clean. Sometimes in ways even the engineeers had not anticipated.
housecleaning prior to system update is good counsel. Cocktail and other utilities in that class are good ideas. system update does make many things a bit smoother and faster, even with the one conflict with some Photoshop files
If you don’t do your housecleaning before an update and have a problem, one path of solution is to run the housecleaning utilities after, and reinstall the update and then reinstall the apps whose files may have been stepped on.
Yes, engineers can’t anticipate all combinations and permutations and sequences of prior installations and updates and their consequences, so there are often minorities of people who don’t have broken systems, but do have bad experiences with after.
Buko’s point is that you have to have a healthy system to begin with. Just because you don’t appear to have problems before an update – and they surface afterwards – doesn’t prove the update is the problem.
If you have an undetected heart problem that causes a heart attack during sex, is it fair to say that sex cause heart attacks?
Nothing "stepped on" here. And I’ve never removed a single dfont. 😉
I’m confused. I thought this thread was about the subset of people for whom the OS update messed with Photoshop. Trying to help them figure out how to make PS whole again.
I started the thread, found a solution, published it here. Stuck around to see if I might help other people who had the same problem to see if the same solution might work for them, too.
I get a Photoshop splash, it opens and then waits patiently for me to do sumptin’. Of course, I only launch Photoshop about once a week or so, since I just leave it running.
I realize those frustrated with problems don’t always appreciate the "works great here", posts. But it’s not necessarily gloating and they CAN serve a purpose. It lets others know that the problems they’re having just might be specific to their machine. Personally, if I was having problems I’d WANT to hear from those who have smooth running machines. "I’m having the same problem too" may make you feel better, but how does it help fix the problem?
if things worked before updating OS and didn’t work after, you do have a likely suspect in custody.
Right, and the very likely suspect is the user who has failed (now and/or in the past) to Repair Permissions before and after installing the OS or any other application that uses the installer.
Ramón G Castañeda "Repair Permissions BEFORE AND AFTER installing software (for the FAQs?)" 6/1/04 5:44pm </cgi-bin/webx?14/0>
