I guess I have come up with an answer for my problem. The result still registered as FAIR but now IDCS6 works as it did before with no noticeable delays.
So I removed any low priority and overly greedy login items from my system and a few hardly-used 3rd party System Preference Panes. I opened Activity Monitor and TinkerToolSystem 5 and ran a few tests looking at memory usage. Having done some more research this afternoon on memory management and Sierra I have discovered that woodmeister50 had given me a great lead. I can now work with it with a modicum of patience. It has improved but not totally fixed the problem. I have completed a, b and c and removed a few suggested apps that eat memory and cpu time. Some here have claimed to be able to use CS6 in 10.11 without incident, others haven't.Ī) launch the InDesign application from the applications folder ( this will not work on a shortcut or the dock icon) while holding down SHIFT+CTRL+OPT+CMDī) try using the application from a newly created account that has administrative rightsĬ) reinstall the CS6 package and if the application asks for JAVA use this version:ĭ) roll back to an instance of your computer where the OS and the Application were stable if you have a time machine backup of that point in time. However, I noted this info on Apple Community support by Jimm圜MPIT's Profile | Communities :ĬS6 and 10.11 have not been claimed by Adobe to be compatible at this time. You are correct about it not being supported from El Capitan onwards. I have got InDesign CS6 to work with macOS Sierra but have to allow time for the panels to work. If ever there was a application what was ripe for serious competition (Quark dropped that ball long ago) it's InDesign.Thanks, Willi. This is VERY shoddy for high-end software, but I guess this is what we can expect from an arrogant manufacturer that enjoys a dominant position in the market.
Indesign mac torrent cs6 software#
I personally suspect that the server it is trying to connect to is Adobe's own validation server, which would explain why it happens even when not opening a document locally. Rate this 5 (Best) 4 3 2 1 (Worst) Adobe® InDesign® CS6 software is a versatile desktop publishing application that gives you pixel. Every now and again if I restart indesign the problem happens again, but a complete shut down and leaving it off for 10 mins or so seems to do the trick. Nobody seems to know the cause and least of all Adobe, which can't seem to fix the issue if it's even trying. I eventually tried shutting down the computer (not a restart), left it off for 10 mins and started up the mac, and opened Indesign CS6 it started and performed normally.
In an 8 hour day it could easily crash a dozen times. It can happen at any time and happens fairly frequently for many people. It will happen even if you are working locally and not using a remote server. From CS6 Adobe introduced a range of bugs to torment book designers! The bug that is fixed at flaming last is the fatal error InDesign Must shut down if you dare to change the page size with anything locked on the page, but they have introduced an extra level to the main bug, as a book designer a mechanical is made by making the document the page width + page width + spine! the height is the height, to change the spine you add or take away from the default spine width, but whereas anything in the slug used to move randomly, the get around was to group the items, not bless their cotton socks they have made the App randomly move thing regardless of if they are grouped or not! This is a major BUG as far as book cover designers are concerned we have to change spines all the time, so this breaks every workflow out there, to have these bugs present for so long is a disgrace! But at least we do not have the fatal error now, instead if the folds are locked InDesign just moves them anyway - IDIOTS!Ī serious crashing bug exists with this version (and perhaps others) that has been widely reported in the Adobe Forums and elsewhere, where InDesign reports that "the connection to the server has been lost" and then shuts down completely, generating a crash report.
0 kommentar(er)
