Recent RAW update crashes Ps

Did you Repair Permissions before AND after the update?

Routine maintenance is imperative.

I still advocate Repairing Permissions (with Apple’s Disk Utility) before AND after any system update or upgrade, as well as before AND after installing any software that requires an installer that asks for your password.

I have seen software installations go sour because the installer did not find everything as and where it should be.

I have also seen software installations go bad because the installer did not clean up after itself properly and did not leave everything as and where it should be.

This is just my own personal opinion and practice based on my own observations. Others may disagree and that’s OK. I can only base my routines and my advice to others on my own experience and conclusion. I don’t pretend to know why others believe otherwise.

Repairing Permissions after the fact (i. e. not immediately before and after an install) seldom helps.; Try it anyway, though.

====

Additionally, if your machine does not run 24/7 so that it runs the daily, weekly and monthly Cron Scripts in the middle of the night as intended by Apple, run Cocktail (shareware) as well.

Cron Scripts are maintenance routines designed by Apple to run on a daily, weekly and monthly basis in the middle of the night.

If you don’t run them, you WILL run into trouble, sooner rather than later.

Here’s an excerpt from the Apple tech doc <http://docs.info.apple.com/article.html?artnum=107388>

Mac OS X performs background maintenance tasks at certain times if the computer is not in sleep mode. If your computer is shut down or in sleep at the designated times, the maintenance does not occur. In that case, you may want or need to run these manually.

Mac OS X periodically runs background tasks that, in part, remove system files that are no longer needed. This includes purging older information from log files or deleting certain temporary items. These tasks do not run if the computer is shut down or in sleep mode. If the tasks do not run, it is possible that certain log files (such as system.log) may become very large.
Also, from: <http://docs.info.apple.com/article.html?artnum=106978>

The disk activity generated by find is a normal part of file system maintenance, used for tasks such as removing invisible temporary files that are used by the system. It is scheduled to occur early in the morning at 03:15 everyday, 04:30 on Saturdays, and 05:30 on the first day of each month.

NOTE: There have been comments to the effect that Apple "fixed" this in 10.4.2 and later versions of the OS, but I have not been able to verify this to my satisfaction. The reference in the 10.4.2 release notes are far from explicit on this subject.

= = =

If you have DiskWarrior, run it regularly too.

Incidentally, the ACR 4.5 is fine.

I generally leave the computer running 24/7. The past couple of weeks I’ve been putting it in sleep mode when not using it. I’ll leave it on tonight to see what happens.

Thanks for the info.

I’ve tried to reinstall Ps, but that doesn’t help.

Reinstalling while keeping your prefs will do you no good.

See if Photoshop works correctly in a new user.

If it does trash the prefs in the old user.

Still happening. I’ve managed to launch Ps by double clicking an image in Bridge. Once I close the image, Ps will hen crash. Changes made in the RAW window are saved.

I’ll try to delete the old preferences. (Say good bye to my actions)

I’ve deleted the old preferences (Adobe Photoshop CS3 Prefs.psp). No crashes since. Thanks for your help.

Also, suspect your Fonts as "It happened after I … had turn on a bunch of fonts in Fontbook".

FontAgent Pro would find and quarantine duplicated or damaged fonts.

Sorry: Double post.

Good advice. Thank you.

I’ve since realized that activating the text tool was the cause of the crashes. If it wasn’t active when Ps was launched, then no problems. If launching when the text tool was active or launching and subsequently activating the text tool, then Ps would crash.

There is a previous thread dealing with this that has good information. Essentially, as noted by Ann, FontAgent Pro will take care of things.

Garry,

I’ve since realized that activating the text tool was the cause of the crashes.

Then suspect a bad (corrupt or duplicate) font, of course.

Neil

Exactly. It’s simple, but I don’t use the type tool a lot.

BTW: I didn’t take care of it. FontAgent Pro did!!! A nice application. Works like a charm.

Now if my #%@&% server would let me access the ftp all would be well.

but I don’t use the type tool a lot.

A problem font can cause a crash even when the type tool is not active and there is no text in the image. :/