Still the same problems with Adobe CS3 files - Crazy Dave

Definitely report these problems to Apple at their feedback website:


Apple don't care, but at least there will be a record of all derogatory correspondence if a whole bunch of people decide to take a class action lawsuit against them one day. It's happened to them before, remember the class action when people bought OSX then found that it didn't have half the features of OS9 and they couldn't even play a DVD.

You're not the only person considering jumping ship and changing to Windows. At least Windows has a great deal of consistency. It's becoming almost impossible to get REAL work done on a Mac. It's great for the iPhoto and iTunes crowd, but people who have jobs and get paid just can't rely on Leopard.

Being a Mac consultant, every day now I have to deal with compatibility issues now ranging from apps that only work with 10.3, apps that only work with 10.4, apps that work with 10.3 and 10.4 but not 10.5, apps that work with 10.4 on a G4 but not a G3 or Intel, apps that only work with Intel on 10.4, apps that work with G3 on 10.3 but don't work on G3 with 10.4, people who still need to use Classic applications but find that Leopard disables Classic, and of course people who have 3 year old computers who can't use online banking because Java hasn't been (and never will be) updated for 10.3, which I assume will start happening to 10.4 users now that Leopard is nearing a year old. The latest version of Safari is out for Windows but it's not available for Tiger. Probably never will be. That's a sign of how much Apple DON'T care about their existing user base. They are only interested in converts now.

My friend just bought a new MacBook but she's thinking of going back to her PC because Facebook doesn't work well with Leopard (you can't upload photos using 10.5.3) and she can't even play DVDs on her new laptop, which she could with her old PC laptop (AnyDVD for WinXP plays Sony Arcoss protected DVDs, but her MacBook just locks up and she has to restart if she tries to play them)

Apple are frantically rushing to finish Snow Leopard, yet they haven't even fixed Leopard. I'm guess it will NEVER be fixed. And come Snow Leopard's release, you can expect to have to update almost every single program on your computer yet again, for bug fixes/incompatibilities/inability to open apps.

Never thought I'd say this, but after 16 years, I now hate Macs.

Reply to This

Saturday, July 05 2008 @ 12:35 AM PDT

Still the same problems with Adobe CS3 files - w i n t e r m u t e--2008

If you are experienced at using design apps, you should realize that it is always better to save your files locally (to your computer's hard drive) and then transfer the files to the server later via the Finder. Many design apps create a temp file on the drive where you last saved your current file resulting in a lot of excess data traffic to and from the server. Furthermore, saving directly from an application to a server over a local network can require a lot of bandwidth and Server I/O time... especially if you are dealing with large graphic files on a slow network with multiple users. Congestion of this sort can result in corrupted files, lousy performance, etc. This is not Adobe or Apple's fault... this is a case of a user not knowing about best practices when dealing with design applications. Just save locally and transfer the file later.

Reply to This

Tuesday, July 08 2008 @ 08:36 PM PDT

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

Thursday, July 10 2008 @ 05:56 AM PDT