For those that are unaware:
Essentially Photoshop doesn’t recognize files after saving them to a server, as it would seem, ruining your file.
Only I’m experiencing this problem in saving files to an external FW drive. The weird thing is that in addition to the PSD files not being recognized, the JPEGs I saved from these PSD files to a new folder is completely gone as well. No trace of it on my system and I know for a fact I did not delete it.
Now rather than finishing up work on my latest stock photo project I’m wasting my time backing up a drive to clear and install OS X 10.4 on. My only hope is that I’ll somehow be able to read these files that come up as unreadable in 10.5.3. If that doesn’t work I’ll stick to redoing last weeks work from 10.4 until things are stable again in 10.5.x. What a pain. This is by far the worst bug I’ve ever experienced with an Apple operating system.
[tags]Apple, OS X, 10.5.3, bug, Adobe, Photoshop,[/tags]
can you just use cs2 instead?. . .
I also saw this noted on Digital Grin: http://dgrin.com/showpost.php?p=839709&postcount=3273
@bloopy (aka Bryan) I’ll have to try that. From what I’m reading the problem lies in how Photoshop writes the file in a save and how Apple’s OS supports that… or doesn’t as it would seem.
@Steven thanks for the link
Pingback: A Fresh Cup » Blog Archive » Double Shot #225
I had a different experience with iPhoto 2 days ago.
I just drag’n’drop 15 photos to iPhoto when it “just crashed”.
Since it wouldn’t restart – I rebooted my Mac Book.
My FW external drive was gone.
After about 6+ hours working hard on getting it back (Disk Utility,First Aid,Diskwarrior,Drive Genius,fsck_hfs) I managed to get 2 out of 3 partitions (slices) back.
-> Damn it, these would have killed 254 gb of photos and my personal collection of about 12 gb mp3s (altough, the mp3 I don’t care so much, since I got all audio cds anyway).
But if I’d lost all my photos – Apple would have had a real problem.
Very un-funny – the drive works. After reformating and stress-testing it – any f##king bit can be written and read again.
Looks to me, that there is something in 10.5.3 that has a problem with firewire external hdds.
Read this a day too late – I let my machine update to 10.5.3 yesterday. Does this impact files that were saved prior to 10.5.3 – or is it that you shouldn’t save to externals after the update?
@Mark words is use Save As vs Save. Also save locally. I wouldn’t risk saving it out to an external drive or a network server. And to answer your question this impacts people using Adobe CS products with 10.5.3 after the update. I found it amusing that in my call to Adobe Tech Support they told me to follow John Nack’s blog on this topic for updates.