Leopard and InDesign 2.0.2
InDesign 2.0.2 (yes! not CS2!) seems to be working fine on my MacBook with OSX 10.5.2 but I really want to upgrade my Mac Mini to Leopard and that's where I work most with InDesign and I don't want to find myself suddenly not being able to use it.
I can't find anything from anyone in these forums or any others saying they've had problems with version 2.0.2 and I found one posting that said it was working fine with Leopard, which is my experience so far, even though people are having problems with some of the later CS versions. Plenty of people are complaining about Photoshop 7 not working with Leopard and that was in the same box as InDesign 2.X.X, so I would have expected to find something. (BTW, I've bought myself Photoshop Elements 6 rather than upgrade the current full Photoshop.)
Is there anyone else working with this 'ancient' version and if so, have you encountered any problems with it on Leopard? Adobe says that there 'may be' problems and it's shown as incompatible on their compatibility chart but you wonder if that's just a ploy to get people to upgrade (cynical? moi?).
No-one had any problems with this? Really? I've looked further, and apart from Adobe (mentioned already) I can't find anything saying there could be and (again as mentioned) just one person saying it worked fine for them.
Would there be any reason that the really old version I have would have fewer problems running on Leopard than some of the later CS versions of InDesign, which I've read do have the odd glitch?
Similar Messages
-
Snow Leopard and Indesign CS5.5 compatibility
I have just paid for a CS5.5 Indesign upgrade on my Mac OSx 10.6.7 that is running Snow Leopard and it apparently is not supported on this type of Mac. The processor is a 1.5 GHz Intel Core Solo. Why is it not working????
PLEASE HELP QUICKLY!!The System requirements for the InDesign CS5.5 are following. So, it should work. You need to contact Adobe Technical Support for any issues that exists.
Mac OS
Multicore Intel processor
Mac OS X v10.5.8 or v10.6
1GB of RAM (2GB recommended)
2.6GB of available hard-disk space for installation; additional free space required during installation (cannot install on a volume that uses a case-sensitive file system or on removable flash storage devices)
1024x768 display (1280x800 recommended) with 16-bit video card
DVD-ROM drive
Adobe Flash Player 10 software required to export SWF files
Broadband Internet connection required for online services and to validate Subscription Edition (if applicable) on an ongoing basis* -
Is Adobe Photoshop and Indesign (version cs3) compatible with "Montain Lion"?
Please answer me, otherwise I'd rather stick to my loyal and "Snow Leopard"Welcome to Apple Communities
It's supported http://www.adobe.com/products/creativesuite/faq.html#lion-os -
Illustrator CS2 and InDesign CS2 not starting - here is how it was solved.
This document is merely a compilation of information found at the sources named at the bottom of this document.
Basically running older Adobe CS2 Software on a MacBook Pro 10.6.x Snow Leopard - probably like many of you that either can't afford the upgrade to CS3, CS4 or CS5, or maybe don't see the need to do so. It's running good but it is slow since it is using Rosetta, but it does work - well, used to work.
Illustrator CS2, InDesign CS2, Photoshop CS2, etc. were all running fine after the upgrade to Snow Leopard (under 10.6, 10.6.1 and 10.6.2). Then the update to 10.6.3 was installed. At the same time a bunch of other updates - including the Acrobat 8.2 update - were installed. Not really sure what did it, but all of a sudden Illustrator CS2 stopped responding at the start up screen - no longer started up and InDesign CS2 popped the registration/licensing screen. When trying to enter license info on first key press the application quit entirely.
So maybe the 10.6.3 update was the culprit. Never even thought that it could be the Acrobat 8.2/8.2.1 updates. Then I found this thread here:
http://forums.adobe.com/thread/613287?tstart=0 (good reading)
Which ultimately pointed me the the instructions here:
>start quote from http://kb2.adobe.com/cps/534/cpsid_53468.html
Replace the corresponding files present in the “ /Library/Application Support/Adobe/TypeSpt/Unicode/Mappings/” folder with the one attached to this document.
Download the attached Mac.dmg (http://kb2.adobe.com/cps/534/cpsid_53468/attachments/Mac.dmg) file to a machine where the issue is seen.
Close all Adobe applications
Double Click the Mac.dmg file to mount it.
Copy Mac folder from mounted image. Paste it to /Library/ApplicationSupport/Adobe/TypeSpt/Unicode/Mappings/.
A message appears to confirm to replace the existing 'Mac' folder. Replace the 'Mac' folder.
Launch Illustrator or InDesign CS or CS 2.
The Mac folder attached to this KB document already has the correct permissions set, so it should not be necessary to complete the steps below. However there may be cases where the permissions for the Mac folder get overwritten. In such a case, the original issue can reoccur. To solve this issue, complete the steps below:
Follow Solution 1 and make sure that all Adobe applications are closed.
Right or Control click and select 'Get Info' on the Mac folder in “ /Library/Application Support/Adobe/TypeSpt/Unicode/Mappings/”, which you have copied from the .dmg file attached to this document.
Verify that under 'Sharing and Permissions' all users listed have no write access
If a change is required, click the padlock symbol and provide your Administrator credentials
Select the user which has Write access and change it to 'Read Only'.
Ensure the user 'Everyone' is set to 'No Access.
To check if the issue has been solved, launch Acrobat 8.2 and then Illustrator or InDesign CS or CS 2.
< end quote
Even after following the instructions still "no love" from Illustrator CS2 or InDesign CS2. InDesign did no longer show the registration screen, but it didn't continue launching, and Illustrator progressed further along in the start up sequence but also never finished launching.
Then I found another article on the adobe site. I am just quoting the part performed and which ultimately did the trick.
>start quote from http://kb2.adobe.com/cps/326/326388.html
Steps 1 and 2 are not relevant so no need to do them
3. At the Finder, choose File > Find.
4. TypeAdobeFnt10.lst (Illustrator CS2), select the system drive, and then press Return.
5. Delete all AdobeFnt10.lst files found.
6. Restart the computer.
7. Restart Illustrator. Illustrator creates a new Adobefnt10.lst or AdobeFnt07.lst file.
< end quote
So, this solved the problems at least for the time being. Hope this helps someone else a bit.
Download files:
http://kb2.adobe.com/cps/534/cpsid_53468/attachments/Mac.dmg
Sources:
http://forums.adobe.com/thread/613287?tstart=0
http://kb2.adobe.com/cps/534/cpsid_53468.html
http://kb2.adobe.com/cps/326/326388.htmlIllustrator CS2 stopped working for me on Snow Leopard as well. What it all boiled down to was not to update to 12.0.1. Not sure which release of Snow Leopard I was on when I figured that out but I keep up-to-date, am now at 10.6.6 and CS2 still works fine. I keep getting prompted to update to 12.0.1 from time to time but just cancel it.
I'm fairly sure I was at 12.0.1 already when I moved from Leopard to Snow Leopard and it was that, not a Snow Leopard update, that "broke" CS2 12.0.1. If I remember correctly, if you now try to apply the update, it won't go through with it anyway. -
Anyone else having a Problem with Leopard and Photoshop CS3?
I'm using CS3 with Leopard 10.5.4 at work and there are some very aggravating anomalies, that I'd like to nail down to a cause. Most frequently, when switching from apps to P'Shop, the menu bar stays for the previous app, i.e. when going from Finder to P'shop, the menu bar still says Finder and has Finder options. Changing from Lightwave to P'Shop, the menu bar remains Lightwave.
Occasionally, an Adobe app - P'Shop or InDesign - will simply disappear and not come back. The icon in the dock shows it as active, but no amount of clicking, Command-Tabbing will reveal the app and I have to Force Quit, losing unsaved changes.
I have a feeling it's Leopard, since, I've used CS3 on Tiger and CS4 on Tiger and never had a problem.
I'm wondering if upgrading to the latest Leopard would make much of a difference.
Has anyone come across this and found any kind of answers?
Thanks for any suggestions.
-Vincent> Just because it doesn't happen to Phil (who may not use all of the same features of the Suite that others do anyway) does NOT mean that these problems are not real and are not mere PEBCAK.
Right. If someone is having a problem associated with Tiger, it's PEBAK. If Leopard is involved, it's automatically because of Leopard. Apparently, with Apple's latest OS, trouble shooting problems are no longer necessary - just blame it on Leopard and call it a day.
b FUD
I find the dynamics here really interesting. This thread would have been very different if Vincent had posted with problems involving Tiger. Would have gone something like this:
After admonishing him for not providing more information about his setup by posting the obnoxious big blue link on how to ask questions (ahem - we know NOTHING about his machine or configuration, such as which machine, how much RAM, scratch disk or attached peripherals), there'd be all kinds of trouble shooting advice given - "try a new user", "repair permissions", "run DiskWarrior, and on and on ...
But no, since he mentions Leopard, none of that is apparently necessary and the completely, utterly
b irresponsible
advice is given ... "that's just the way Leopard is".
Those are some serious problems he's reporting that have nothing to do with Leopard. Something is obviously hosed!
As for discounting my experience because I don't use every app in the suite as extensively as I do Photoshop, I'm FAR more qualified to discuss Leopard and CS issues than Ann or Neil who do not use Leopard at all (and have never used it as far as I know.)
"Others have problems with it", is their battle cry but it's extremely weak. Do I really need to remind you all that these forum are ALWAYS filled with people who have problems, regardless of version or OS? You act as if this forum was a ghost town when Tiger and CS3 were current!
Gee, Ann ... people are STILL reporting problems with 10.5 and CS3? How shocking! Guess what - people are STILL reporting problems with 10.4 and CS3 too! Let me make a prediction - people will have problems with 10.8 and CS9!
Vincent-
> I don't really deal with fonts anyway ...
Yes. You do. Even if you never type a single line of text, every application uses fonts to create menus and other GUI items. If one of those fonts are bad, it can create all kinds of problems, including the very problems you mention.
The fact that you don't seem aware of this and you're still using 10.5.4 leads me to believe you're not familiar with the basic practices of maintaining a healthy system. Again, how did you install Leopard on that machine?
Look, if you're simply trying to justify using CS4, go right ahead. It's a worthwhile upgrade in it's own right. However, if you install it on that machine in it's current state, CS4 will NOT fix your problems because you do NOT have a healthy system.
You asked for experiences with Leopard - I can launch every application in both CS3 and CS4 suites
i simultaneously,
and STILL not have your issues. I haven't experienced anything like your CS3 problems in Leopard - on both a 2006 Mac Pro and a 2008 Macbook.
If you'd like help to try and figure out the real problem, I'm more than happy to help. If not, Adobe will gladly take your money ...
-phil -
Printing problem with Epson R290 Illustrator and inDesign
I am running CS2 on Leopard and have recently purchased an Epson R290. The first time I used it with Illustrator and InDesign it worked fine but now whenever I print anything it prints a tiny version (about a sixth of the real size) of the design in the top left corner of the page. It does this both with new documents and old ones that used to print ok.
Since I posted the message about this problem I have discovered that it can be worked around by choosing a higher quality print. ie if you choose plain paper when printing from Illustrator or InDesign the printer prints a reduced size image but if you choose Ink jet mat or glossy the print comes out fine. I don't have this problem with Photoshop but that may be that I always print high quality from that application. I don't use Appleworks Draw so don't know whether this solves the problem for that application but iWork documents print ok.
-
I've been using a 24" iMac (originally purchased in mid-2006) to do graphic design with Adobe Creative Cloud, primarily Photoshop, Indesign, and Illustrator. I am also starting to do some very ametuer video prep (like iMovie) etc. With just Photoshop and Indesign alone, what is the minimum Mac I should upgrade to, if I am still concerned about performance, but budget and mobility could come into play too? For instance would the 13.3" Mac Book Pro with Intel Graphics be sufficient for doing my usual print design, with a little iMovie thrown in? At that price, I could afford a big display to plug into when I am at my office desk.
I like the idea of mobility (which I haven't had before with the big iMac), but don't want to notice a horrible lag in performance if I get a weaker machine. The guy at PeachMac said that when it came to display the Retina (in the Macbook Pro, 13.3 in edition) made a high difference despite the lack of a dedicated graphics processor. I don't do heavy-duty, memory-intensive graphics work but about once every two years anyway, and my iMac only has 2GB of RAM to begin with. I just want to make sure that true designers who have switched from older iMac machines to Macbook Pro's (not the most expensive models) didn't regret it when trying to run Photoshop, et al.
(My absolute budget is "no more than $2,000" which is why I am considering the new iMac vs. the MacBook Pro 13.3" and getting a nice external display.)
Thanks!To run the new Studio you need Leopard and it will not spec'd to run on Tiger (Leopard 10.5.6 [specs here|http://www.apple.com/finalcutstudio/specs>) I have run it in Leopard and Snow Leopard, and both seem fairly similar, though I generally like my Leopard machines a bit more. Still breaking in the Snow Leopard and getting various kinks out of it. It seems I have some more little things go wrong in Snow Leopard.
Overall I like the upgrades in the Studio and you may just want to make another boot drive with clean Snow Leopard and the new Studio to work with until you feel you are happy with how it is performing. Bascially that is what I do until I am fully comfortable with the system and always have my rollback plan in place in case something goes awry and I need to get things done.... -
Snow Leopard CS2 - InDesign crashes on print
Hello!
I am hoping some one can send me in the right direction in figuring this out. I have googled this problem until my fingers are sore and have yet to see anyone with this issue. I have gone through the many many documents about not being able to export to pdf and have followed all of those directions hoping that maybe there was some correlation - still nothing.
So what's happening is we open a standard document create either text or regular box then click file print and get the crash (Problem report from InDesign below)
we can print repeatedly with only a box on the page. sometimes it will allow us to view the print preset dialogue and some times it will almost allow us to create a new print preset.
it gets REALLY buggy when you click the text tool - some times as soon as you click the tool it crashes and sometimes when you click the page. The below Problem report from InDesign was from printing with text on the page.
This is a fresh install and software update to 10.6.5, fresh install of CS2 and I have not added any fonts, this also happened before the OS upgrade. Photoshop and Illustrator seem to work and do not even stutter when printing, This is only happening in InDesign. After trying to read through the badly labeled post on here I saw one almost similar post about a printing error and there was no help offered.
I have read many times that CS2 should not run with snow leopard and have seen just as many post that CS2 does run with snow leopard. If by chance you can please offer ANY advice or support it would be greatly appreciated! We are a fairly small publishing company and this software is our only option.
Thank you in advance!!!
Here are the computer specs:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 4
L2 Cache (per core): 256 KB
L3 Cache: 8 MB
Memory: 6 GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: MP51.007F.B03
Process: Adobe InDesign CS2 [621]
Path: /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
Identifier: com.adobe.InDesign
Version: 4.0.5.688 (4050)
Code Type: PPC (Translated)
Parent Process: launchd [91]
Date/Time: 2010-11-19 16:34:02.617 -0600
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6
Interval Since Last Report: 6312 sec
Crashes Since Last Report: 4
Per-App Interval Since Last Report: 1141 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID: 6561D05F-71AF-4389-BE34-19D7D208BB97
Exception Type: EXC_CRASH (SIGTRAP)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x80239522 __pthread_kill + 10
1 libSystem.B.dylib 0x80238dcf pthread_kill + 95
2 com.adobe.InDesign 0xb80bfb30 0xb8000000 + 785200
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 1:
0 libSystem.B.dylib 0x801430fa mach_msg_trap + 10
1 libSystem.B.dylib 0x80143867 mach_msg + 68
2 com.adobe.InDesign 0xb819440f CallPPCFunctionAtAddressInt + 206231
3 libSystem.B.dylib 0x8017085d _pthread_start + 345
4 libSystem.B.dylib 0x801706e2 thread_start + 34
Thread 2:
0 com.adobe.InDesign 0xb815acc0 spin_lock_wrapper + 90152
1 com.adobe.InDesign 0xb8179c5b CallPPCFunctionAtAddressInt + 97763
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 3:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 4:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 5:
0 com.adobe.InDesign 0xb815aa8b spin_lock_wrapper + 89587
1 com.adobe.InDesign 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 com.adobe.InDesign 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 com.adobe.InDesign 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8aace226 0 + 2326585894
Thread 6:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 7:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 8:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 9:
0 com.adobe.InDesign 0xb815a8c8 spin_lock_wrapper + 89136
1 com.adobe.InDesign 0xb8176d61 CallPPCFunctionAtAddressInt + 85737
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145c1d spin_lock_wrapper + 3973
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 10:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 11:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145c1d spin_lock_wrapper + 3973
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 12:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 13:
0 com.adobe.InDesign 0xb815a8ff spin_lock_wrapper + 89191
1 com.adobe.InDesign 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.adobe.InDesign 0xb80c6b13 0xb8000000 + 813843
3 com.adobe.InDesign 0xb80c0037 0xb8000000 + 786487
4 com.adobe.InDesign 0xb80dd8e8 0xb8000000 + 907496
5 com.adobe.InDesign 0xb8145397 spin_lock_wrapper + 1791
6 com.adobe.InDesign 0xb801ceb7 0xb8000000 + 118455
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x802fc540 ecx: 0xb7fff9ac edx: 0x80239522
edi: 0xb8211640 esi: 0x00000005 ebp: 0xb7fff9d8 esp: 0xb7fff9ac
ss: 0x00000023 efl: 0x00000286 eip: 0x80239522 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x80239518
Binary Images:
0x80000000 - 0x8005dff7 com.apple.framework.IOKit 2.0 (???) <A769737F-E0D6-FB06-29B4-915CF4F43420> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x8007d000 - 0x800e7fe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x80142000 - 0x802e9ff7 libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <62291026-D016-705D-DC1E-FC2B09D47DE5> /usr/lib/libSystem.B.dylib
0x8036a000 - 0x804e5fe7 com.apple.CoreFoundation 6.6.4 (550.42) <C78D5079-663E-9734-7AFA-6CE79A0539F1> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x805dd000 - 0x805ebfe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <3CE8AA79-F077-F1B0-A039-9103A4A02E92> /usr/lib/libz.1.dylib
0x805f0000 - 0x805fcff7 libkxld.dylib ??? (???) <F0E915AD-6B32-0D5E-D24B-B188447FDD23> /usr/lib/system/libkxld.dylib
0x80600000 - 0x80646ff7 libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
0x80653000 - 0x807d5fe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <35DB7644-0780-D2AB-F6A9-45F28D2D434A> /usr/lib/libicucore.A.dylib
0x80837000 - 0x808e4fe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <DF8E4CFA-3719-3415-0BF1-E8C5E561C3B1> /usr/lib/libobjc.A.dylib
0x808f8000 - 0x808fbfe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <321A99FE-F169-91AE-66FF-B4CD007B3E9A> /usr/lib/dyld
0xb8000000 - 0xb81defff +com.adobe.InDesign 4.0.5.688 (4050) <6437A74D-607F-7339-5F7E-F6B0EF81C25D> /Applications/Adobe InDesign CS2/Adobe InDesign CS2.app/Contents/MacOS/Adobe InDesign CS2
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <62291026-D016-705D-DC1E-FC2B09D47DE5> /usr/lib/libSystem.B.dylib
Translated Code Information:
objc[621]: garbage collection is ON
NO CRASH REPORT
Model: MacPro5,1, BootROM MP51.007F.B03, 4 processors, Quad-Core Intel Xeon, 2.8 GHz, 6 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.36.1)
Bluetooth: Version 2.3.8f7, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 5770, Display, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 931.51 GB
USB Device: hp LaserJet 2420, 0x03f0 (Hewlett Packard), 0x2917, 0xfa200000
USB Device: Hub in Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x1003, 0x1d100000
USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0x1d110000
USB Device: Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x020b, 0x1d130000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000
FireWire Device: built-in_hub, Up to 800 Mb/secI can work in CS2 Indesign on my iMac running 10.6.5 with no clichés (so far), but like this thread, InDesign crashes and shuts down when attempting to print.
However, I have no problem making any type of pdf from InDesign, and my PDF's print without any problems. So, for now, I work in InDesign, and when I need to print, I make a PDF of my document and then print it. I know it's a pain, but for now, it's all I can do to keep using CS2.
I realize the solution is updating to a CS package that will run flawlessly with 10.6. (anyone have a few hundred dollars to give to this worthy cause?).
But if anyone out there figures out a way to print from Indesign CS 2 on 10.6, please let me know. My actual needs are minimal, so CS2 does all I really need it to do for now . . . if you don't count that I can't print from it. Ha ha . . . not funny.
This is an update on my progress to resolve my problem (it's now two hours later than the text in this post above). I had a copy of InDesign CS 3 that I never installed. I decided to give it a try so I installed it. It installed with no problems and I updated it using the InDesigns update feature.
I can now print with no problems using the print dialog box from within InDesign. However, my specific print features from my brother printer dialog box won't function. All said, I rarely use those features so it seems I now have a copy of InDesign (CS 3) on OS 10.6.5 printing adequately, provided I only use the print dialog box from within InDesign CS3, which suites me fine.
Good luck everyone. -
Continuing font encoding and tag issues with snow leopard and CS4oI
I am looking for help with a font handling issue with snow leopard and cs4 Indesign. Despite numerous calls and hours on the phone neither Apple nor Adobe has been helpful. I have had this issue open with Adobe since oct 5 but they remain totally unresponsive to date. I need to be able to use Type 1 fonts and do the following , export a pdf from Indesign with the following attributes: 1) xml tags for stories and objects. 2) have the fonts encoded as ansi and embedded.
Some additional information - exporting to ps is not an option as it destroys the xml tags. and doesn't guarantee that the fonts won't become CID or some other odd encoding.
As it stands now,
Leopard (10.5.8) and CS3 creates ansi encoded fonts with xml tags.
Leopard (10.5.8) and CS4 creates ansi encoded fonts with xml tags.
Snow leopard and CS3 creates ansi encoded fonts and xml tags
Snow leopard and CS4 creates custom subsetted fonts and some xml tags.
If any one has any advice on how to force specific font encodings from CS4 pdf exports so that i can preserve the tags and get the correct fonts I would be grateful.The font encoding is not a function of the OS version, but rather of how a font is internally encoded and the content you are representing with the font.
If you are seeing a difference between MacOS 10.5 and 10.6 with the same Adobe software, it probably has something to do with use of a system font that is somehow different from one version of the OS to another. InDesign does not use any of the OS' font handling software.
Assuming that the fonts are embedded, subset or not, what is your issue with whether a font is ANSI-encoded, custom-encoded, or CID-encoded? It should make no difference for purposes of workflow beyond InDesign for software that adheres to the PDF specification (including all versions of PDF from 1.3 and up to 1.7 plus ISO 32000-1 PDF and all versions of PDF/X and PDF/A).
Neither InDesign or any other Adobe application provides user choices for the encoding since it shouldn't make a difference. The encodings chosen by Adobe's core technology components are for a combination of optimization and to support proper text search, copy, etc.
- Dov -
CS6 Photopshop, Illustrator and Indesign crash upon opening Window 8 64-bit.
Runnning Genuine CS6 Photopshop, Illustrator and Indesign crash upon opening without any error message... worked fine then stopped working. Running it on Window 8 64-bit. Have tried opening without 3d party plugins, resetting preferences, and uninstalling and reinstalling.
did you clear the caches?
and onthe off-chance that ID got far enough to leave something behind, find the InDesign Recovery folder (a hidden folder, I think, since Snow Leopard or Lion) and empty it if there's anything there.
Access hidden user library files | Mac OS 10.7 Lion -
Since upgrading I am unable to open InDesign documents via the File:Open dialog. Opening from the Finder is fine but not from the Open dialog where the ID docs appear 'greyed out'. Furthermore if I want to import a Swatch from a previous donor document I am UNABLE to do so from the open dialog box.
I have tested the same situation with Snow Leopard and there is no problem with opening documents or importing the Swatches.
I will contact Adobe tomorrow but in meantime has anyone else seen this?I thought I deleted it by using app zapper but could it be that some parts didnt' get deleted? idk...
Any time you choose to use a third-party software removal tool instead of the vendor's own process, you run a risk of it failing in subtle and annoying ways. Generally speaking, you're better off without tools like this. -
Leopard and CS3 - Are they ready for prime time?
Trying to revive this thread, I manage 130 Macs at an art school and I am starting to research what I am going to do this summer as far as OS and CS versions. Currently we are on 10.4.9 and CS2 and about 15% of our Macs are Intels. I am concerned as I am not hearing good things about Leopard and I am wondering if CS3 is ready for prime time. I should note that stability is my first priority NOT the latest OS and App versions. So the question is are they ready for prime time or should I stay with CS2 and Tiger or should I go CS3 and Tiger.
Summer is a long way off, so hard to guess. I would say that if they don't have the kinks out by then, they probably never will, but still a gamble at this point IMO. I have one of the new Mac Pros (early 2008) w/CS3 Apps installed. I have been using all the below listed apps for the past two weeks without any major problems so far, but I also know that I may be living on the edge right now. I don't feel confident enough to switch to Leopard on my other two computers yet. My restarts on the new machine take about 30-seconds between selecting Restart and ready to start work again (vs about 1.5-2 minutes on my Dual G5). Apps like Photoshop CS3 launch in about 1/3 the time. But all of this speed means absolutely nothing when you slam into an incompatibility - that is the real time trap - I spent the last 8 hours doing nothing but tracking down a Permissions problem in Leopard that none of the utilities will currently fix.
These appear to be working for me so far...
Photoshop CS3
Illustrator CS3
InDesign CS3
Flash CS3
Dreamweaver CS3
Bridge CS3
Lightroom
After Effects CS3
Contribute CS3
What doesn't work yet...
Acrobat Pro & Acrobat Reader (fix was expected from Adobe last month)
Other issues encountered so far...
Most Photoshop and After Effects Plugins required paid upgrades to function in Leopard/CS3 (over $1500 for me the past week)
Monitor calibrator software (such as Artisan) dead with no fixes, but to buy all new hardware calibrators/software - again! - another $1000 bucks
I purchased the Silverfast Leopard upgrade ($105) to get the Epson 4870 scanner plugin to work with Photoshop CS3, but having problems - I think it is a Leopard problem
Adobe UPDATES menu item is dimmed out in all CS3 apps.
Having lots of Leopard User Permissions problems - hopefully 10.5.2 will help? -
Hi,
Any other developers trying to develop using idsdk5 for CS3 using Snow Leopard and XCode 3.2.1 ? Adobe says it is an unsupported configuration.
I don't like to downgrade, and am wondering if there are others with the same issue and possible solutions?
Thanks,
Remco>> SLow Leopard (the old one)
LOL!
Thanks for the other tips - most are news to me.
Let's comparing some more notes!
Here's a few things I believe (I won't say 'I know' - I have no hard proof, and I don't have a budget to investigate getting hard proof )
I had extremely frustrating debugging issues with Xcode 3.1 - most of the time breaking into assembly code instead of showing the source code. No clear pattern: same breakpoint hit the first time shows the source code, second time assembly code. Fiddling with 'back arrows' sometimes got the source code to show up. It got so bad that I often had to revert to command-line debugging using gdb. Also a lot of 'mumble mode' - things just ................ coming to a pizza-colored cursor for no ................ apparent reason.
As a result, I've gotten into the habit of doing my coding and debugging on Windows XP with Visual Studio - once you get rid of the C-compiler RSP files and put the include paths into your project file instead, it works rather nicely, and to me it feels much faster than Xcode, even in a virtual machine.
I still do a lot of coding and debugging with InDesign CS on Windows/VS2003 - turnaround times (launch/debug/exit/...) are so much faster.
With Xcode 3.2.x on Snow Leopard things seem to work much better - so I might start to gravitate back to Mac-based debugging; time will tell.
CodeWarrior is over for me - I only use it to generate release versions (I still have some PowerPC macs around 'just in case' I need to debug something with CodeWarrior, but it's not been necessary).
As to Windows debugging: I use both Parallels and VMware, and my gut feeling is that Parallels seems to work quite a bit faster. Totally subjective, and probably unfair (the virtual machines have different histories, etc...) - but currently I find myself a lot in Parallels, with a virtual machine stored on an external USB drive connected to my laptop - I have heaps of virtual machines around, too many to store on the internal HD. Even with the slow USB bus 'underneath' it all, it works well.
With VMware I get a lot of mumble mode - machine non-responsive for minutes at a time, even with the virtual machine on the internal HD. Parallels has not done that to me (yet).
Another thing (might be fixed in Snow Leopard) - but have you ever had it happen that your InDy CS3 and CS4 plug-ins suddenly get a folder icon instead of a plug-in icon? Typically, all plugins will exhibit that behavior when it happens.
It's something with the package/bundle stuff, and the Finder getting confused. This is my unconfirmed theory: the Finder accepts a whole host of bundle formats, and the bundle structure used by the Adobe sample projects is 'iffy' - the Finder supports it, but occasionally, the Finder gets confused, and shows these plug-ins as folders (and that then further leads to customer support requests).
Now, if you go into the plugin package, it looks different from most other packages I've seen.
Here's how I fixed it: I added another build phase to the target - a 'Run Script' called 'Restructure Bundle'. I've put in the following shell script (using /bin/sh):
rm -rf $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
mkdir $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
echo InD3InDn > $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents/PkgInfo
mv $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Resources/Info.plist $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
mv $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Versions $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
mv $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Resources $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
mv $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/$PRODUCT_NAME $TARGET_BUILD_DIR/$PRODUCT_NAME.InDesignPlugin/Contents
That 'restructures' the plug-in bundle and makes the problem go away - AFAIK the Finder has never gotten confused with one of my home-grown bundled plug-ins.
The whole point might be moot, though - for all I know the original problem of the Finder getting confused might be long fixed... -
InCopy and InDesign files viewing differently
I am currently running a project to change a magazine publisher from a Quark platform to an InDesign and InCopy workflow. One problem that keeps occuring is that when an editor manually alters the paragraph style to make the copy fit in InCopy, (ie, altering the tracking and/or leading), this change does not show when the same file is opened in InDesign.
For example, a heading that an editor has reduced tracking -5% to make fit into one line in the InCopy file, will still look like two lines when the InDesign file is opened. This is particularly dangerous for pages of text, as we keep losing lines from the bottom of the page and this can be easy to miss during output for press.
I've checked, and all staff are following workflow, and updating assignments - so it's not human error (as far as I can see).
Is this happening to anyone else? And is there a fix for it? The only one I can think of is to add more paragraph styles with different trackings etc, but this is not ideal and does not cover all the variables.
We are using CS4, and the Snow Leopard platform – Please help!As an update to this, I have found what I believe is the cause, and, hopefully a fix, to this problem.
The cause seems to be that in the original Quark template, the font has a horizontal scale setting of 95%. When the template is converted to InDesign, everything looks fine. However, the font doesn't seem to be recognised as a true font, and this has resulted in the word and character spacing looking completely different between InCopy and InDesign. This has been causing problems such as;
1. Headings showing in one line in InCopy but flowing onto two lines in the InDesign file
2. Body text showing completely different spacing throughout - causing uneven window and orphans and resulting in paragraphs being in different places in the InDesign and the InCopy files. This has made it impossible for the editors to fit copy on page.
Note that any written changes by the editor (ie, change to the words) has worked fine.
The fix seems to be to go back to the original template in Quark, and make sure all the font/text settings in the paragraph and character styles are set at 100%. Then make the template conversion again. I have run some testing this afternoon, and everything seems to be running ok now - touch wood!
Thought I'd send an update anyway in case anyone has the same problem. -
Slow Using Photoshop and InDesign
We have several 2GHz C2D Mac minis with 2GB RAM running Leopard. The users are complaining that using Photoshop CS4 and InDesign CS2 is slow. Is this to be expected? Would it be better to upgrade the PowerMac G5's we also have to Leopard, and use the software on that instead? Thanks.
Photoshop and InDesign both need a lot of room in RAM to run at a decent speed. Between just what the OS and Photoshop need, 2 GB of RAM isn't enough. You're getting a lot of page outs to disk in order to run these apps. Even worse if you have both PS and InDesign running at the same time. You really need at least 4 GB of RAM to see good performance.
So yes, since the Mac Minis can't have more than 3 GB of RAM installed, you'd be much happier with the performance of these apps on the G5s. But you'll still have to have more than 2 GB of RAM installed, or you essentially won't see any difference. You would want to have at least 4 GB of RAM installed on the G5s.
Maybe you are looking for
-
Computer Crash - how to deactivate so I can install on a new computer
My computer just crashed and therefore I will be buying a new computer soon. I had the adobe suite on my old computer along with lightroom and was wondering how to go about deactivating them on that computer so I can reinstall them on my new computer
-
Standards data migration process from Hyperion Enterprise to HFM 11.1.2.1
Client currently has HEM and we are implementing EPM v11. I am wondering if there is any standard process to migrate historical data from HEM 6.5 to HFM 11.1.2.1?
-
I have been trying to set up my new 8500A printer all afternoon. It keeps asking for a e-mail address for the printer but when I try to access it, there is nothing there. When I use the touchscreen to find it, the word "connecting" comes on the scree
-
I tried Sharepod, and that did not help. Neither did running a command to check it. Help!
-
Find Query Name in Transport Request or In TR what are Queries.
Dear All, I would like to find a Query Name in Transport Request(DEVK.....) or Vice-Versa in Transport Request (DEVK........), what are the queries are included. I created SAP Query using SQ01 and assigned the InfoSet. The query is succesfully e