Illustrator CS2 WILL NOT OPEN!

Discussion in 'Design and Graphics' started by MandolinChick, Jul 1, 2008.

  1. MandolinChick macrumors newbie

    Joined:
    Jul 1, 2008
    #1
    Hey all-
    I have a Mac Mini (os x 10.4) and CS2. My computer came with very little RAM and I designed some very large files. Illustrator and InDesign kept crashing, so I went ahead and installed 2 gigs of RAM. Illustator still will not open (the others will), so I reinstalled the entire suite. Still didn't work so I ran Repair Disk. Still not working. Any suggestions?
     
  2. flrazor macrumors member

    flrazor

    Joined:
    Jun 29, 2004
    Location:
    Saint Paul, MN
    #2
    At what point in the start-up does the crash occur (what does the splash screen's status line read before it closes)? Are you opening the document or just the application alone? Do you have any information from the crash log you could post to help diagnose the trouble?

    Sometimes it's something as simple as a corrupt font causing Illustrator to crash when it tries to read the font cache. Could also be a memory problem, but I'd hope not with all the RAM you just added in.
     
  3. MandolinChick thread starter macrumors newbie

    Joined:
    Jul 1, 2008
    #3
    It reads "The application Adobe Illustrator CS2 quit unexpectly. Mac OS X and other applications are not affected. Click Reopen to open the application again. Click Report to see more details or send a report to Apple." That's the whole message. The last thing I read before it crashes is "initializing" after it goes through all fonts.

    I've read the problem report, but nothing makes sense to me! It does say "Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000."
     
  4. flrazor macrumors member

    flrazor

    Joined:
    Jun 29, 2004
    Location:
    Saint Paul, MN
    #4
    The key part of the error message is somewhere north of that line, usually near the top of the report. It's tough to explain exactly where it occurs, but usually it tells you the error type and name before the strings of code that were running before the crash. One I have seen a lot that comes up is an "Unmapped Memory Exception" which a lot of times (not necessarily always) with CS is a corrupt font somewhere in your system. Just as a test, can you turn off all but your system fonts, restart, then try to open the program and see if that works? There's an easy way to figure out where the bad font is later, but if it still crashes then you can rule that out.

    We have several systems running Creative Suite and we've had this happen during startup before and 99% of the time it's a corrupted font we had to install temporarily for a job.
     
  5. Ozzie56 macrumors newbie

    Joined:
    Feb 22, 2009
    Location:
    north east us
    #5
    Illustrator CS 2

    I am having exactly the same problem and I was wondering if anyone was able to help with this? I have deadlines and not sure what to do. Does anyone know if CS3 would be better?
    Thanks
     
  6. MagicWok macrumors 6502a

    Joined:
    Mar 2, 2006
    Location:
    London
    #6
    OP: Try taking out the new RAM modules and see if Illustrator opens up again.

    Post above - Did you try to reinstall the suite?
     
  7. covisio macrumors 6502

    covisio

    Joined:
    Aug 22, 2007
    Location:
    UK
    #7
    I had a similar problem to this a couple of years ago. No CS app. would start fully (except Acrobat Professional which isn't really linked up with the other CS apps in the same way).
    The only thing I had done was install a new HP Designjet driver. I couldn't understand what was causing it to crash, ended up installing, reinstalling CS, reinstalling the OS, each time I did it it crashed again.
    Turned out that installing the HP driver software caused the Time Zone on the Mac to change to 'Cardiff'. For some reason this time zone causes CS to crash on load. Changing the time zone to 'London' (or any other than Cardiff), fixed it, CS loaded instantly. Very weird, and very frustrating until the cause was found out. Cost me about a day and a half.
     
  8. a cat *miaow* macrumors regular

    Joined:
    Jun 12, 2007
    #8
    Sorry I can't remember any details.. but I had what sounds like a similar problem..
    Fixing it meant removing one of the plug-ins but I can't remember which one because I upgraded since – maybe you can find some help based on this?
     

Share This Page