Still the same problems with Adobe CS3 files - Crazy Dave
Wintermute, I have hundreds of clients who work with large Photoshop and Illustrator files mounted from a server. It is simply the ONLY way to do it for some projects, especially magazines and other publications where you may have ten or twenty people working with the same material that is constantly being updated.
This practice has been working for years. I managed an advertising company with 45 designers all working from the same server only 5 years ago and they NEVER had a problem (apart from power failures, but in that case THEIR computer lost power, the battery backed-up server didn't stop working, so no files were lost. This practice is commonplace and has been for longer than I can remember. We were doing it in OS9 and all the way through till 10.3.
The fact this is broken now shows SOMETHING is wrong with Leopard. It is not user error. It is Apple or Adobe's error, breaking systems that have been working just fine for years.
Suggesting that people should change every single part of their working routine every time Apple decides to change its OS is extremely counter-productive. Maybe you are listening to Steve Jobs too much. His mantra seems to be, if you can't do it with a Mac, it's not worth doing. However the rest of the world are quickly changing their desktop publishing to Windows systems, which don't change every year at Apple's whim, and which don't suffer the compatibility problems caused when trying to network a company running a mix of G3, G4, G5 and Intel systems running anything from OS9 to OS 10.3, 10.4 and 10.5. That's not even mentioning shared folder permissions problems that only appeared with the advent of OSX, that do not plague Windows computers.
Existing users, log in. New users, create a free account. Lost password?
Still the same problems with Adobe CS3 files - Crazy Dave
Wintermute, I have hundreds of clients who work with large Photoshop and Illustrator files mounted from a server. It is simply the ONLY way to do it for some projects, especially magazines and other publications where you may have ten or twenty people working with the same material that is constantly being updated.This practice has been working for years. I managed an advertising company with 45 designers all working from the same server only 5 years ago and they NEVER had a problem (apart from power failures, but in that case THEIR computer lost power, the battery backed-up server didn't stop working, so no files were lost. This practice is commonplace and has been for longer than I can remember. We were doing it in OS9 and all the way through till 10.3.
The fact this is broken now shows SOMETHING is wrong with Leopard. It is not user error. It is Apple or Adobe's error, breaking systems that have been working just fine for years.
Suggesting that people should change every single part of their working routine every time Apple decides to change its OS is extremely counter-productive. Maybe you are listening to Steve Jobs too much. His mantra seems to be, if you can't do it with a Mac, it's not worth doing. However the rest of the world are quickly changing their desktop publishing to Windows systems, which don't change every year at Apple's whim, and which don't suffer the compatibility problems caused when trying to network a company running a mix of G3, G4, G5 and Intel systems running anything from OS9 to OS 10.3, 10.4 and 10.5. That's not even mentioning shared folder permissions problems that only appeared with the advent of OSX, that do not plague Windows computers.
Reply to This | Parent
Thursday, July 10 2008 @ 05:56 AM PDT