Ask a Tech Expert Now- JustAnswer
Mac OS X 10.5.4 (#5): Adobe CS3 problems persist?; Random problem? Try re-applying the combo updater first; more
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.
Random problem? Try re-applying the combo updater first As we've reported innumerable times, reapplying the current Mac OS X combo updater can resolve a surprisingly high number of problems after incremental system updates. This amusing note from MacFixIt reader Mark Horner is exemplary:
"Mail_Crashes_when_I_Type_A_space_in_the_message_box. Fixed by a combo update."
Reapplying the combo update can also fix general issues with poor performance after an incremental update, such as those noted by Michael Lee:
"After update hung at restart for 20 min. Had to force shutdown. Running very slow after update - profiler says that 10.5.4 is installed."
Install fails partway through (or freezes) Several readers have reported failed installation of Mac OS X 10.5.4, which sometimes necessitates a full re-install (Archive and Install) of Mac OS X 10.5.x from the original media source (CDs or DVD).
Remember to avoid performing any other processes while the Mac OS X 10.5.4 update is taking place in order to lessen the chances of this issue.
MacFixIt reader Tim Travelstead writes:
"My computer is stuck on the install process for Mac OS X 10.5.4. Its been running installer script for an hour and a half."
Another reader writes:
"Just upgraded from 10.5.3 to 10.5.4. Had a problem after installing when it said 'running installer script.' Was just staying there for a long time."
If you are able to successfully restart after forcing a shutdown subsequent to a failed installation, make sure to reapply the Mac OS X 10.5.4 combo updater aforementioned.
"Connect to Server" problems? Check incoming connections Some users have reported problems with sharing after the update to Mac OS X 10.5.4, including an inability to use the "Connect to Server" command.
MacFixIt reader Gabriel Dorado fixed this issue on his system via this process:
- Open System Preferences
- Navigate to the "Security" pane
- Select "Firewall"
- Check the box for "Allow all incoming connections" on the target Mac.
Dorado said that after making this change and allowing a single successful connection, the setting could be changed back to other options (such as "Allow only essential connections"), and connectivity remained intact.
Startup problems when external devices are connected If you are experiencing problems with startup after updating to Mac OS X 10.5.4, try temporarily disconnecting external devices.
If startup still fails, reset your system's NVRAM/PRAM via this process: Shut down your Mac, then start it back up while immediately holding the following keys: Command, Option, P and R. Hold the keys down until the computer restarts and you hear the startup sound for the third time. NVRAM and PRAM can sometimes harbor problematic data that lingers after disconnecting the offending device.
Clearing caches, removing specific kernel extensions and other workarounds listed in the following tutorials can also prove effective for device-caused startup failure:
Previous coverage:
- Mac OS X 10.5.4 (#4): Spotlight problems; random shutdowns; poor performance; more
- "syslogd" process taking 100% CPU under Mac OS X 10.5.4
- Mac OS X 10.5.4 (#2): issues fixed by reinstalling with standalone updaters; iSync problems
- Mac OS X 10.5.4 released; fixes Adobe CS3 save issue; update recommendations
:%20Adobe%20CS3%20problems%20persist?;%20Random%20problem?%20Try%20re-applying%20the%20combo%20updater%20first;%20more%20%7C%20MacFixIt%20-%20CNET%20Reviews&srcUrl=http://reviews.cnet.com/8301-13727_7-10329646-263.html){kind=small}
Apple can only do so much to the system and now it may well be a compatibility issue with photoshop itself which needs an update to work better with the current system version.
I've had several errors preventing me from saving changes to a photoshop photo.....even just saving a psd file as a jpg file.....you can't do it!! THIS IS A MAJOR BUG
The specific symptoms are slightly different than the CS3/10.5.3 bug. I don't remember the details, but I believe this (the low space bug) caused files to be saved with zero space used (or similarly obviously little space).
Now 3-5GB isn't much for free space on a server, but it's certainly not low enough that I'd expect data loss on reasonably small files.
Increasing the free space solves the problem, although the corrupt files are gone forever.
Is your "low space" situation where you have about 10% left?
Traditionally, BSD Unix only allows root to use that last 10% of disk space, to avoid disk-full conditions, which get pretty nasty.
That could apply to MacOS X too.
- by Help Us All July 10, 2008 5:41 PM PDT
>This is a reply to a previous comment by macaholic
- Like this Reply to this comment
-
(6 Comments)Yes, but that doesn't change the fact that many have worked live off Mac servers for years without such an issue.
If your network/storage is robust, it's very easy for users to get comfortable. Version Cue Server may be Adobe's answer, but it's a dramatic change in work-flow.
The fact that Apple specifically highlighted this 10.5.4 fix indicates a certain level pervasiveness.