Unfortunately, shortly after upgrading, my machine became unusable. I considered that I might as well upgrade and make sure everything was configured right, before adding those products into the mix.Īll are good and fair reasons. So, this last 24 hours of pain-in-the-butt has been all for you! You're welcome.įinally, I'm about to get started on a big project that will require loading a pile of new software.
I write about new technology and if I don't eat my own dog food, I won't be able to tell you about my experiences. These naggings were interrupting my flow and my thinking was that since I hadn't heard many complaints about upgrading to Yosemite, I might as well just do the deed. It's incredibly annoying to get an upgrade notice from Parallels, for example, every time you need to launch a Windows VM. The biggest is that a number of the Mac applications I use every day have started to nag me with upgrade notices, even while running on Mavericks. I upgraded to Yosemite for a few reasons. Then, a day or so ago, I moved to Yosemite. I started it on Mountain Lion, waited until Mavericks seemed to have most of the kinks worked out of it, and then moved to Mavericks. Until this hard crash, I've been surprisingly satisfied with the machine. I've told you a lot about the heavily configured non-Retina iMac that I bought just about 13 months ago.
Making it work: Four displays on a monster iMac.Open letter to Tim Cook: it's time to call Mavericks beta.From Mavericks back to Mountain Lion: so much for that plan.Why I chose a maxed-out iMac over a powerful PC.Why I bought a tricked out iMac instead of a Mac Pro.Maxed-out iMac: just how far can we push this thing?.