CS3 will not run on Lion. If you cannot upgrade to CS5, then you will need to downgrade back to Snow Leopard:
Downgrade Lion to Snow Leopard
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Install Snow Leopard.
This will erase the whole drive so be sure to backup your files if you don't have a backup already. If you have performed a TM backup using Lion be aware that you cannot restore from that backup in Snow Leopard (see below.) I suggest you make a separate backup using Carbon Copy Cloner 3.4.1.
If you have Snow Leopard Time Machine backups, do a full system restore per #14 in Time Machine - Frequently Asked Questions. If you have subsequent backups from Lion, you can restore newer items selectively, via the "Star Wars" display, per #15 there, but be careful; some Snow Leopard apps may not work with the Lion files.
Well, it's not really an Apple issue. Users need to determine if their mission critical software will be compatible with an OS upgrade before undertaking the upgrade. Although I empathize with your situation, I would say this was something you should have considered before undertaking the upgrade to Lion. This is a paramount consideration for any enterprise situation because of the costs associated with making the mistake of upgrading. And, this is one of the major reasons why enterprises seem to be behind in upgrading or choose not to upgrade.
Well, I strongly feel it is an Apple issue. Granted I should have done more research before I upgraded, but I (naively) thought that Lionwould be another instance of Apple improving their product, and enhancing its capabilities. In this I was wrong. But then why produce an OS that's incompatible with a large block of your user base?
(1) OS-makers set the rules, and it is incumbent on them tobehave in a gentlewomanly/manly fashion. It seems inconceivable that it's in Apple's best interests to prevent Adobe products from working. Yet that seems to be the case here. It's like Bloom returning home in Joyce's Ulysses: it's dark and all the furniture has been moved.
And fellow-software makers should help each other out: when there's a flood in anoffice building (as there is here) everyone drops what they're doing to pitchin.
Maybe this was all a product of a *******-match between Adobe and Apple(recall the PDF support issues on the iPad), but from a users' perspective this is irrelevant. It's the argument that was made in the Financial Times recently about the fall of Netflix: Customers don't give a fig what your internal business priorities are, they want the products that they bought from you to work and be priced well.
(2) The very kludgy work-arounds to this issue, involving deleting or hiding PPDs in the system library (specifically inOS/Library/Printers/PPDs/contents/Resources/), suggest that what is causing the InDesign CS3.x to crash is minor in nature. I.e. a patch could easily bewritten.
(3) Adobe CS3.x applications are the first generation of "Universal" apps. Okay, maybe their implementation was not ideal (as this shows) but they were written to the rules at Apple laid out for them, rules that are still in place now. As with my first point (1) it's unfair to change the rules on Adobe after the fact.
(4) Who could expect that the step from 10.6.x 10.7.1 (the.1 presumably meaning that some initial kinks had been worked out) would be so traumatic? We are not talking here about a step from Classic or PPC. (I remember these, but because they were structural changes everyone, at some level, was prepared for the change.) This is not about getting Rosetta to work on 10.7.
(5) We are not talking about a minor set of applications here either. Considering the long-standing use of Macs by the design community, in print, production, and photo, the support of Adobe apps should have been aconsideration for Apple. But when you look at the list of issues with this upgrade (http://kb2.adobe.com/cps/905/cpsid_90508.html) it's hair-raisingly long. And note these are CS5.5 apps: the very newest software you can get from Adobe. If part of your argument is that it's incumbent on people to keep their software up-to-date, then here's a set of OS issues that are affecting users of software that was released just this spring.
(6) Even if Adobe CS5.5 was fully supported (see (5)), it's unreasonable to expect everyone to upgrade all of their software packages each time the OS is upgraded (as opposed to completely revised: again, as in (4)10.6.x was not Classic). All of my personal software is up-to date, but I cannot say the same of my clients and my employer: they hold to older computers and software packs as long as they can because the software was so expensive.CS5.5 Design Premium is $1900. For any organization this is a big chunk of cash to doll out regularly. My employer is a non-profit: should they replace their software because I have upgraded my laptop? Or should I stop upgrading my software because they can't afford to get CS5.5 (even if it was properly supported)?
And, what if we buy a new Mac? Presumably this will come with Lion. It's clear with this that this is no longer a $4000 proposition, but a $10,000 proposition, since all the other copies of CS3.x would have to be upgraded.
I work for a printer manufacturer and come across the upgrade issue constantly. Customers will upgrade their OS without checking compatibility and blame the printer manufacturer for not upgrading drivers and PPDs fast enough.
The blame does fall on the person deciding to upgrade their computer to a newer OS and not thoroughly researching compatibility. This includes applications, printers, scanners, etc. It's up to the individual/company to see if their mission-critical applications will work with the new OS before an upgrade is done or if an upgrade of the mission-critical applications is needed. Also, this isn't just an Apple issue, I have customers in the Windows environment that have the same issues.
The issue is Adobe and software manufacturers want you to buy their upgrades. If Adobe didn't want you to buy an upgrade to Creative Suite, then they would have created upgrades to CS3 to work with the newer operating systems. You also can't expect the software companies to give away upgrades either. It's expensive to develop, test and finally market a software upgrade. These software companies need to employ software engineers that constantly evaluate the software to make sure it works with OS upgrades, both major and minor.
I feel badly that you are so frustrated, but you don't need to jump on an upgrade. It makes better sense to install the OS upgrade, on a separate disk or partition, then dual boot and test your applications. Then if all applications works as expected switch to the new OS.
How is it users fault when new macs come shipped with Lion? This makes the "upgrade responsibility" argument null and void. Macs used to be user friendly. What the **** happened? Mr Jobs must be spinning in his fresh little grave.
Another disgruntled user with discs full of unusable expensive CS3 software.
Has anyone found a work around besides going backwards in OS which will no doubt present a whole set of "new" problems.
remove adobe PDF PPD from the following folders:
I did this and now I can print just fine in Adobe InDesign CS3 running on Mac OSX Lion