The reporting has been remiss and I'm duly apologetic as people have been camped-out on the sidewalk all night, pitifully wailing for the future of the new used iMac in particular and Apple in general.
Everything looked somewhat ok as I switched to Google Chrome and the system stayed up for six continuous hours and, for this one, that's like running the Boston Marathon on your hands.
The machine was just screwing with me again as I booted it about four a.m. and it came up quick and clean, something which is notable due to the number of times it has crashed the moment the system opened to the Finder. Boom. Down again.
The point of failure for half a dozen or so crashes was the same. I had written the previous blog article, pondering for however long that took, and there were no problems. During that time confidence grows that maybe Safari really is the bad guy.
However, the system crashed when I tried to post the update. I booted and that re-opened windows which normally isn't a problem but it crashed again going back to complete the update. This took place three times and it was repeated because there is not typically a pattern so it's not unreasonable to expect it to be different on the next boot.
The last move was to boot into Safe Mode and the purpose was to remove document files from the system disk and that's just text but it poofs if I erase the system and start over. There is not much interest in doing that as I have no reason to believe installing Yosemite 10.10.3 again would accomplish anything as there's no reason to believe it works and there's ample testimony from multiple people to show it doesn't.
It looked like there might have been some improvement but then it started crashing all over again. It's repeated since each time I restart it so I gave up. This is coming to you from Yevette's machine as the new used iMac is close to unusable.
For all the things I've been advised to remove, none of them made any difference. In general, your machine has to be at or near stock or any problem will be assumed to be caused by third-party software. For my own machine, almost nothing is left but there is one piece and maybe for some twisted reason that causes a problem with Yosemite 10.10.3 when it never had a problem with anything previously.
(Ed: isn't this just debugging the problem for Apple?)
Yes and it's the most brazen example of it I've ever seen. All of this should have been flushed out in their beta testing and quality control prior to release. You see what happened. You couldn't find a more shallow install if you did it on Mars.
In systems programming, a 'shallow install' is one that received insufficient analysis prior to implementation and, regrettably, blew off the power grid for the entire Eastern seaboard. This premise came from the Great Goddess of All New England Systems Programmers: Susan. I did not know her but learned of her from those who did and there are many terrible things one can hear in one's life. A life sentence in jail … very bad. Your dog just died … very sad.
But when the Goddess Susan said your install was shallow the only appropriate response was the walk off into the Outback and die alone and in shame. You're such a miserable waste of oxygen that you wouldn't even qualify to be a Fox News journo as you would only be the one to fetch their coffee because SUCH is your disgrace.
That all this came behind an 'incremental update' is the shallowest part of all as that kind of system change is never supposed to introduce such sweeping changes. Apple couldn't have botched this any harder if that had been their design to start.
There is no good answer just now as I wait for tech support from Techsmith on how to remove their software from the system. They did something 'clever' and that cleverness may screw me into a clean install to get rid of it. For the moment, only this advisory applies: don't install anything from Techsmith as their support software adds something which may be impossible to remove without breaking the system worse. The specific module is com.techsmith.TACC.
The Patience Gene is having some troubles as part of me is reviewing just what it would take to zero the iMac system disk and put a clean copy of Yosemite 10.10.3 on it. Then do absolutely nothing to it and observe. This could be a priceless diagnostic at the expense of one hell of a lot of work. The Patience Gene needs to get working hard on this one as everything screams for it.
Had this been a new release, the implementation steps would have been different and I damn sure would not have let Apple auto-update me into it. After such a release, the approach is to bring up one piece of the system at a time and evaluate it. After some appropriate period of QA, bring up the next piece. It's extremely slow but it identifies immediately any compatibility problem.
So, sign me Not Completely Screwed as I still have ganja that works and a guitar that works.
Everything looked somewhat ok as I switched to Google Chrome and the system stayed up for six continuous hours and, for this one, that's like running the Boston Marathon on your hands.
The machine was just screwing with me again as I booted it about four a.m. and it came up quick and clean, something which is notable due to the number of times it has crashed the moment the system opened to the Finder. Boom. Down again.
The point of failure for half a dozen or so crashes was the same. I had written the previous blog article, pondering for however long that took, and there were no problems. During that time confidence grows that maybe Safari really is the bad guy.
However, the system crashed when I tried to post the update. I booted and that re-opened windows which normally isn't a problem but it crashed again going back to complete the update. This took place three times and it was repeated because there is not typically a pattern so it's not unreasonable to expect it to be different on the next boot.
The last move was to boot into Safe Mode and the purpose was to remove document files from the system disk and that's just text but it poofs if I erase the system and start over. There is not much interest in doing that as I have no reason to believe installing Yosemite 10.10.3 again would accomplish anything as there's no reason to believe it works and there's ample testimony from multiple people to show it doesn't.
It looked like there might have been some improvement but then it started crashing all over again. It's repeated since each time I restart it so I gave up. This is coming to you from Yevette's machine as the new used iMac is close to unusable.
For all the things I've been advised to remove, none of them made any difference. In general, your machine has to be at or near stock or any problem will be assumed to be caused by third-party software. For my own machine, almost nothing is left but there is one piece and maybe for some twisted reason that causes a problem with Yosemite 10.10.3 when it never had a problem with anything previously.
(Ed: isn't this just debugging the problem for Apple?)
Yes and it's the most brazen example of it I've ever seen. All of this should have been flushed out in their beta testing and quality control prior to release. You see what happened. You couldn't find a more shallow install if you did it on Mars.
In systems programming, a 'shallow install' is one that received insufficient analysis prior to implementation and, regrettably, blew off the power grid for the entire Eastern seaboard. This premise came from the Great Goddess of All New England Systems Programmers: Susan. I did not know her but learned of her from those who did and there are many terrible things one can hear in one's life. A life sentence in jail … very bad. Your dog just died … very sad.
But when the Goddess Susan said your install was shallow the only appropriate response was the walk off into the Outback and die alone and in shame. You're such a miserable waste of oxygen that you wouldn't even qualify to be a Fox News journo as you would only be the one to fetch their coffee because SUCH is your disgrace.
That all this came behind an 'incremental update' is the shallowest part of all as that kind of system change is never supposed to introduce such sweeping changes. Apple couldn't have botched this any harder if that had been their design to start.
There is no good answer just now as I wait for tech support from Techsmith on how to remove their software from the system. They did something 'clever' and that cleverness may screw me into a clean install to get rid of it. For the moment, only this advisory applies: don't install anything from Techsmith as their support software adds something which may be impossible to remove without breaking the system worse. The specific module is com.techsmith.TACC.
The Patience Gene is having some troubles as part of me is reviewing just what it would take to zero the iMac system disk and put a clean copy of Yosemite 10.10.3 on it. Then do absolutely nothing to it and observe. This could be a priceless diagnostic at the expense of one hell of a lot of work. The Patience Gene needs to get working hard on this one as everything screams for it.
Had this been a new release, the implementation steps would have been different and I damn sure would not have let Apple auto-update me into it. After such a release, the approach is to bring up one piece of the system at a time and evaluate it. After some appropriate period of QA, bring up the next piece. It's extremely slow but it identifies immediately any compatibility problem.
So, sign me Not Completely Screwed as I still have ganja that works and a guitar that works.
No comments:
Post a Comment