Resulting in no surprise at all, the Apple Store reported the iMac has no hardware problems. That's where we were once before and it resulted in a clean install of Yosemite 10.10.3 which crashed even with just a few Safari extensions installed.
Cutting immediately to the punchline, Apple cannot do a clean install for Yosemite 10.10.2 on this system and that version I know to be stable.
This was not acceptable and there is now contact with a gentlemen who is, in effect, an ombudsman for difficulties of this nature in which everyone says there is nothing wrong and yet the system still crashes.
It's conceivable all of this comes down to being poisoned by a single Safari extension incompatibility. As the system had run OK for a day before those were installed and it crashed immediately after the extensions were installed, it seems clear there must be something wrong with at least one of them. Nevertheless, it crashed even after they were uninstalled and using the Safari utility to do it.
The situation is still grim but there is a prospect and I very much appreciate Chuck's intervention. I don't know his last name and I don't suppose his first name is a security violation. Hereinafter, he shall be known as Chuck the Big Gun from Apple. He is connected and can ask for help from Engineering. They're the ones who write the code and they need to know of this situation or they can't fix it for anyone else. The system crashes so hard it leaves no diagnostic log so nothing was ever transmitted to Apple whereas the system otherwise reports every diagnostic with Apple's call-home implementation.
This may well result in a public service but, frankly, I'm a selfish bitch at this point and I just want it to run. Nevertheless, if this debugging fixes it for other people as well, so much the better.
Again I apologize but fault doesn't even matter anymore. Sometimes things will get dark with computers and you have to stay cool or you'll never get out of it. The other choice is to roll over and spend the rest of your life playing canasta. Um, thanks but no. The battle continues and I apologize it takes so long but sometimes it gets that way. As it stands, there isn't anyone who knows what's wrong with it and I'd even ask Santa Claus if I could find him. That doesn't mean it's impossible, it's just a bitch right now. Any computer can be fixed but they love to see you feel some pain first. I tell you they hate us all but that editorial can keep for another time as it's ain't particularly funny at this particular moment.
As it stands right now, kit is all over the place from switching back and forth between the computers multiple times. That leaves cables in disarray and consequently nothing much works. That doesn't mean it won't but rather there's chaos from an in-between situation. The laptop will move to the front of the house so I have some stable connection while further analysis takes place on the iMac. I will pick it up in the morning and get cracking.
Cutting immediately to the punchline, Apple cannot do a clean install for Yosemite 10.10.2 on this system and that version I know to be stable.
This was not acceptable and there is now contact with a gentlemen who is, in effect, an ombudsman for difficulties of this nature in which everyone says there is nothing wrong and yet the system still crashes.
It's conceivable all of this comes down to being poisoned by a single Safari extension incompatibility. As the system had run OK for a day before those were installed and it crashed immediately after the extensions were installed, it seems clear there must be something wrong with at least one of them. Nevertheless, it crashed even after they were uninstalled and using the Safari utility to do it.
The situation is still grim but there is a prospect and I very much appreciate Chuck's intervention. I don't know his last name and I don't suppose his first name is a security violation. Hereinafter, he shall be known as Chuck the Big Gun from Apple. He is connected and can ask for help from Engineering. They're the ones who write the code and they need to know of this situation or they can't fix it for anyone else. The system crashes so hard it leaves no diagnostic log so nothing was ever transmitted to Apple whereas the system otherwise reports every diagnostic with Apple's call-home implementation.
This may well result in a public service but, frankly, I'm a selfish bitch at this point and I just want it to run. Nevertheless, if this debugging fixes it for other people as well, so much the better.
Again I apologize but fault doesn't even matter anymore. Sometimes things will get dark with computers and you have to stay cool or you'll never get out of it. The other choice is to roll over and spend the rest of your life playing canasta. Um, thanks but no. The battle continues and I apologize it takes so long but sometimes it gets that way. As it stands, there isn't anyone who knows what's wrong with it and I'd even ask Santa Claus if I could find him. That doesn't mean it's impossible, it's just a bitch right now. Any computer can be fixed but they love to see you feel some pain first. I tell you they hate us all but that editorial can keep for another time as it's ain't particularly funny at this particular moment.
As it stands right now, kit is all over the place from switching back and forth between the computers multiple times. That leaves cables in disarray and consequently nothing much works. That doesn't mean it won't but rather there's chaos from an in-between situation. The laptop will move to the front of the house so I have some stable connection while further analysis takes place on the iMac. I will pick it up in the morning and get cracking.
No comments:
Post a Comment