10.5.3 Photoshop CS 3 issues

Great work Joel Bruner1,

This has worked for me on an entire studio of Macs running their workflow over their 10.5.3 server and clients using CS3.

As you described I copied these elements from a 10.5.2 system:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwor k.framework
/System/Library/Filesystems/AppleShare/afpfs.kext

You then have to run permissions repair, which can take a while otherwise the computer would not boot again. You must make sure that you do not leave any files out as again the computer would not boot.

I logged in as root user to make these changes and then used a Leopard install disk to repair the permissions.

Thanks,

David Lee

Thanks to Joel Bruner1 in this thread the problem has been fixed.

This has worked for me on an entire studio of Macs running their workflow over their 10.5.3 server and 10.5.3 clients using CS3.

As he described I copied these elements from a 10.5.2 system:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwor k.framework
/System/Library/Filesystems/AppleShare/afpfs.kext

You then have to run permissions repair, which can take a while otherwise the computer would not boot again. You must make sure that you do not leave any files out as again the computer would not boot.

I logged in as root user to make these changes and then used a Leopard install disk to repair the permissions.

Thanks,

David Lee

Well, I am afraid to say that 10.5.4 does not fix the problem I originally had, which was Photoshop refusing to open .png, .gif or.tif. I even made a file of each in Photoshop this morning and tried to re-open them, only to be greeted with:
"Could not complete your request because Photoshop does not recognise this type of file".
Same problem and I have tried several third-party files just to be sure that the Photoshop generated files are not getting corrupted on export. They all open in Preview still, which makes me think the files are not corrupted.

On the plus side, Mail and Skype seem to have stopped crashing on start-up, which also began with 10.5.3.

Does anybody know if re-installing CS3 would be of any use? If anyone has had success here please let me know.

Cheers

Spen

If I had that many issues, I would just back everything up and start from scratch. Along the way make sure everything you install is compatible and up to date with the OS.

Don

Ditto here-
As of this OSX update (10.5.4), I can now work from our server without making corrupted files (after weeks of not being able to save a .psd file to the server). BTW- It didn't install easy- crashed, had to download it from Apple and re-run it. No other issues so far...

After updating to 10.5.4 everything works smoothly again. Install of update was easy.

10.5.4 fixed the problem. we were lucky...out of 15 designers only 2 had a series of corrupt Photoshop files (one designer still ruined a file even after I warned them to not work off of the server!).
We're good to go.
BTW the RAW import fix thingy didn't work for us. The files are gone forever.

Well, after completely removing CS3 and re-installing it, everything seems to have been fixed.

Hi,

It seems that some users still report troubles (Macfixit) :

Adobe CS3 problems persist? Though Apple's release notes indicate that Mac OS X 10.5.4 resolves an issue with various Adobe CS3 applications (Photoshop, Illustrator, etc.) in which files saved to remote servers become corrupt and can no longer be opened, some users have reported a persistence of the problem.

One MacFixIt reader writes:

"I updated to OS X 10.5.4 on a latest generation 24" iMac with Adobe CS3 on it. The iMac with 10.5 had massive problems with CS3 files since updating to 10.5.2 - frequently existing Photoshop files disappear from the server after the "Save" command, frequently "Save As" is not possible in Photoshop, sometimes Indesign crashes when files are getting saved on the server.

"On the first day with 10.5.4 at least in Photoshop exactly the same problems: Existing files disappear from the server after the "Save" command, "Save As" is often times not possible."

Another reader, Jamie, adds:

"I did the update this morning to all of our computers and our server and I’m still having the same corrupt file issue. I was all happy and giddy with excitement that this 'fix' was out."

Previously published workarounds for this issue include:

* Use "Save As" instead of "Save" It appears that this problem is a result of the application accesses an existing file to save. Using the "save as" command does not access the existing file, but creates a new one every time and thereby bypasses the processes that seem to corrupt existing files.
* Work locally Instead of saving files to a server volume and working off them, save files locally and either mirror them to a server using a synchronizing program (or applescript/automator script) or manually. When editing the files on the server, copy them locally and then edit them.