This content has been marked as final.
Show 7 replies
-
1. Re: InDesign 5.0.2 Still crashes every time!
BobLevine Jan 30, 2008 12:18 PM (in response to Skullmaker)The hiding problems sound like Leopard incompatibilities.
Have you tried creating a new user and seeing how that works out?
Bob -
2. Re: InDesign 5.0.2 Still crashes every time!
Skullmaker Jan 30, 2008 12:35 PM (in response to Skullmaker)Thank you Bob!.
I was thinking that when I used CS2 I was using Mac OS 10.3, since I updated the system to Mac OS 10.5 (Leopard) and CS3 I started to have problems.
So I think you may be right. I will take this weekend to create a new administrator and see. Thank you for your time! -
3. Re: InDesign 5.0.2 Still crashes every time!
(Mindee_Skatfeld) Feb 19, 2008 7:20 AM (in response to Skullmaker)I just udated Indesign to 5.0.2, I'mm running Mac OS 10.4 (tiger) and InDesign crashes. I reinstall original version and still nothing. Anybody find a solution? -
4. Re: InDesign 5.0.2 Still crashes every time!
Buko. Feb 19, 2008 7:25 AM (in response to Skullmaker)I would do an Archive and Install of Tiger then use the combo updater to 10.4.11
I'm using 5.0.2 with 10.4.11 no crashes -
5. Re: InDesign 5.0.2 Still crashes every time!
(Mindee_Skatfeld) Feb 19, 2008 7:42 AM (in response to Skullmaker)http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402521&sliceId=1
I downloaded this and now all is fine
download the FixVCUIFramework.zip file.
http://www.adobe.com/support/versioncue/ts/documents/kb402521/FixVCUIFramework.zip -
6. Re: InDesign 5.0.2 Still crashes every time!
(Mindee_Skatfeld) Mar 19, 2008 3:31 PM (in response to Skullmaker)This solved my problem.
http://www.adobe.com/support/versioncue/ts/documents/kb402521/FixVCUIFramework.zip -
7. Re: InDesign 5.0.2 Still crashes every time!
(erique) Mar 25, 2008 1:05 AM (in response to Skullmaker)Hans, Mindee's solution may work for the crashing issue you're having (I couldn't say, I'm not experiencing it myself), but to get around the 'disappearing' problem (which affects many others besides yourself) see this local thread
http://www.adobeforums.com/webx/.3c057463/88
It doesn't resolve the problem (dare I call it a 'bug'?), but appears to work around it.




