>> Am I the only person who *doesn't* have this problem with Adobe
>> software? I have thousands of students and several hundred staff
>> who do this all the time from their network home directories...
> Count me in. At my current gig the users have been working off the
> servers for years now with Adobe and Quark documents with no issues.
The only major problems we've had with working from the network home
directories have been with Macromedia apps and Microstation.
If you have the file open in a Macromedia app and attempt to copy it
somewhere, you often end up with a zero size file, without any errors.
From memory when I was testing this, you get the same behaviour when
copying an open file from a local filesystem to another local
filesystem, but not when copying an open network file to a local
filesystem, or an open local file to a network filesystem.
Does anyone have a link to Adobe actually saying this isn't supported?
This resource article seems to suggest that it is only suggested to
work from a local filesystem, not that it is mandatory.
http://www.adobe.com/support/techdocs/320771.html "When you want to save an Illustrator file to a network or removable
drive, Adobe *recommends* you first save the file to an internal hard
disk, then close the file and use the Finder to copy the closed file
to the external or network drive."
This seems to just be a basic performance suggestion.
Whenever possible, store InDesign documents, fonts, and graphics that
you use regularly on a local hard disk rather than a removable disk
or network volume.
"Data transmission across a network can be affected by many
variables, including file servers, routers, bridges, network cards,
software, cables, connector, power cables, and power supplies. While
accessing documents, font files, or graphics over a network, you may
encounter network-related problems, such as line noise or packet
collisions. These problems can lead to slow performance or, in
extreme cases, document damage."
In the case of Framemaker on OS 9.x, it looks like it is supported...
If a FrameMaker document is on a network, FrameMaker tries to create
a lock (*.lck) file to prevent multiple users from simultaneously
editing it. If the filename has more than 27 characters, FrameMaker
cannot create this lock file and returns an error.
anyway, I'm getting bored of searching the Adobe info base. I would
have thought that if opening/saving to a network filesystem were
unsupported, these articles would say so...
Nigel Kersten [Senior Technical Officer]
College of Fine Arts, University of NSW, Australia.
CRICOS Provider Code: 00098G