For some time now, i have been getting the following message when i open bridge "Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation" so, i have found that under "tools" and purged individual folders as i needed to work on. I have been using CS5 with no problems for a long time and love it. I do not want to upgrade to anything else. I have an I Mac OSX desktop. I also have CS5 on my Mac Book Pro and its working just fine. I am an artist and do all my work with photoshop CS5 but am not a techie!!
Any ideas about how to fix this?
thank you for your prompt reply! i had the same thought so last week, i
moved a ton of photos to an external hard drive..........i have a 999.86
GB hard drive and now i have 778.62 GB free........
what else can i do?
What is the size of the cache? Where is it located?
If you moved the pictures to another drive the cache probably has to be rebuilt. Mac does have a problem with cache like you state and if purging does not work you might have to delete it manuallly. This is in a hidden directory. Probably find it with web search to find fourm comment on issue.
well, i'm making progress in understanding that i need to "dump the cache
and start again".......but those instructions were for CS6 and i wonder "
if its different for CS5.......i can't seem to find the
library/cache/adobe/bridge ..........and bridge plist file as
well...........if you look at the pict , can you tell me if i'm on the
where do you live? wish you could just come over and fix it for me
Not a mac user but look at this doc. As I said the library you want is hidden by Apple. http://macs.about.com/od/usingyourmac/qt/Os-X-Lion-Is-Hiding-Your-Libr ary-Folder.htm
Re: Bridge stopped working.... i have CS5OK!! and hurray! i think i got it handled and
thank you for your staying with it ! i finally found the library in a
simpler way than going through terminal, etc. (by calling mac tech
support) and deleted the cache files and now bridge seems to be working
just fine!! sending the route along in case anyone else has this same