It's been a while since I got the "We don't support networked computers" from Adobe. They still aren't it would seem, or is this just a minor glitch?

Hey- Adobe- 1998 called and they want their statement about not supporting networked-based workflows back.

[Okay, in this case, it's probably an Apple bug since it worked okay in 10.5.2, but Adobe needs to stop pulling that statement out of their a** and start supporting reasonable workflows.]

Why are we blaming Adobe for OS X issue? Unless they did a huge hack (which seems unlikely), this is a OS X core issue. A program tells OS "Put file to this location" and doesn't care about the rest, it is OS'es job to do it right.
This is the second time Adobe using professionals getting hit by updates from Apple. I like to remind that Adobe pros having close relations to Adobe can easily switch to Windows versions of same programs via cross-grade.
Apple and Adobe should come with a technical explanation about this issue since it has potential to hit other programs or companies using Network storage. (large resource data?)
EDIT: A large newspaper admin friend of mine says Quark users are effected there. I suggest zipping/stuffing file before putting to network so potential of resource issue is gone.

Quote

Ilgaz wrote:
Why are we blaming Adobe for OS X issue? Unless they did a huge hack (which seems unlikely), this is a OS X core issue. A program tells OS "Put file to this location" and doesn't care about the rest, it is OS'es job to do it right.
This is the second time Adobe using professionals getting hit by updates from Apple. I like to remind that Adobe pros having close relations to Adobe can easily switch to Windows versions of same programs via cross-grade.
Apple and Adobe should come with a technical explanation about this issue since it has potential to hit other programs or companies using Network storage. (large resource data?)
EDIT: A large newspaper admin friend of mine says Quark users are effected there. I suggest zipping/stuffing file before putting to network so potential of resource issue is gone.

Quote

Ilgaz wrote:
Why are we blaming Adobe for OS X issue? Unless they did a huge hack (which seems unlikely), this is a OS X core issue. A program tells OS "Put file to this location" and doesn't care about the rest, it is OS'es job to do it right.

I've been managing large graphics offices for years. Actually since before apple introduced appleshare. I've had almost every server Apple has ever sold. I have never seen a corruption issue like this and for Adobe to blow it off with this lame "networks are unstable crap" is total BS. Every network I've set up is packet tested including my home network and I've just experienced this problem. As best as I can tell after a quick look at the evidence the problem revolves around an issue with Adobe temp files and network permissions. InDesign for example saves a temp file to the directory where the original file resides. The problem crops up when during the save InDesign doesn't have permission to read the temp file because of some apparent bug in Adobe apps ability to correctly save permissions over a network. My guess is since Apple's wide use of ACL on OSX server happened about the same time these Adobe issues came up is that they are related. I've also noticed that "for me anyway" using the OS save dialog and not the default Adobe save dialog has eliminated the problem except in InDesign.

ADOBE, wright all your temp files to the LOCAL directory and fix your apps to correctly save with both standard UNIX and ACL permissions!