Yay more downloading for me...
Wow! How do you run 10.0-10.5? Virtual machines?Yay more downloading for me...
Wow! How do you run 10.0-10.5? Virtual machines?
Gorgeous.Yay more downloading for me...
We all have very little control over our lives, much less than we actually realize or admit.Apple screwed up big time here, I'm sure we all remember. Essentially though, the certification system is what's broken here.
really annoying though I find is, that the plain simple user is no more the authority over his own system.
A user should always be able to override what a system thinks is its best intent. Even if it's the wrong decision, even if I have to deal with catastrophic consequences: I (and no one else) should be able to decide, what's happening on my system. I can live with my computer misbehaving and me having to carry the consequences. but I can not live with the fact, that I no longer am in control. Admittedly, not even Microsoft gets this nowadays. at least not to the level I used to.
This is really unreliable annoying, silly, ... if this would be Windows we would all be lying on the floor laughing, ...
Recent versions of Windows do code-signing too.
in fact just recently, Microsoft had a certificate SNAFU that was far worse:
http://news.softpedia.com/news/serv...-ca-audit-data-from-its-partners-501357.shtml
Essentially they lost the audit trail for a bunch of root certificates. Because they're a root CA they threatened via automated script to remove everybody's certificates. Because they had a system failure, lost data and didn't have a recent enough backup.
What Apple did is standard operating procedure. What Microsoft just did most certainly is not.
It would be nice if they provided a process for the end user to re-sign the installers, but that would mean anyone could tamper with them and re-sign them as well.
Why the heck can't they set these certificates to expire far enough into the future that this will never be a problem?
Just set them to expire Dec 31 2099 or something. You can work around them by setting the date back anyway, so it's not like this effectively prevents installs. It's just annoying.
Unless you are located somewhere remote with no broadband or even any reliable internet.
Infuriating. I don't mind having a more secure system, its why I moved to OSX from Windows years ago. But seriously... like everyone else says... this is MY computer, and I should be able to download whichever OS I want. I just want to store the damn things so it does not matter one whit whether its currently compatible. Just makes me want to downgrade all the way to Snow Leopard (which is what my Macs came with). *GRUMBLE*
Are you saying that they are smart enought to create a new designed obsolescence but dumb enought to allow you can set the date back on computers?It's the new designed obsolescence.
Fortunately you can set the date back on computers... For now.
Are you saying that they are smart enought to create a new designed obsolescence but dumb enought to allow you can set the date back on computers?
I know I was pointing out that if they really wanted to create a planned obsolescence the first thing they would have looked at would be not allowing to set the date back...You can also download an updated signed copy of the software.
A veritable treasure trove of OS X releases. I only have images going back to OS X 10.5 Leopard. You never know when those old images may come in useful. One thing that is glaringly obvious is how much the OS X images have grown in size. OS X Tiger 2.74 GB to OS X Leopard the following release 7.63 GB. A massive bump.Yay more downloading for me...
OS X Leopard Server and OS X Snow Leopard Server will run in a virtual environment on Parallels Desktop 11Wow! How do you run 10.0-10.5? Virtual machines?
All those poor people finding themselves in the middle of the Sahara Desert and in desperate need to reinstall their Macs!Unless you are located somewhere remote with no broadband or even any reliable internet.
I haven't verified this since I came across this. But the older installers I've created from the ESD files did seem to work on the last machine I restored Yosemite onto (2 weeks back). The USB I tried creating at the end of February however wouldn't work at all. Had to dig out the older ones I made last year. The one's I had attempted recently I tried building by hand with the terminal, and through DiskMaker X 5. It would complete building, but would refuse to install.I haven't tried it but after right-clicking on the installer to show package contents and drilling down to the ESD file. Would the ESD file installer bypass the certificate? Just wondering.
All those poor people finding themselves in the middle of the Sahara Desert and in desperate need to reinstall their Macs!
This actually makes perfect sense. An up to date USB installer requires a minimal amount of updates post installation. An installer is easy to create. DiskMaker X takes the hard work out of it and v.5 is compatible with El Capitan. I've now updated USB installers for OS X Mavericks, Yosemite and El Capitan with this useful tool
http://diskmakerx.com
Sucks, but people just have to deal with the fact that you're going to need an internet connection sooner or later.You don't need to go that far to get crap broadband.
Or NO broadband.
Let's see...how long will it take me to re-download Lion, Mountain Lion, Mavericks, Yosemite, and El Capitan on my 768 kbps (at best) internet connection?
I checked my App Store on my cMP and all the OSX versions since Lion are there, but Yosemite and Mavericks say "Downloaded" and are not clickable. Even the names themselves are not clickable.
Only the re-download is disabled ! I can see them in the list of purchases (Lion, Mavericks, Yosemite and ElCap) but I can only download ElCapitan - all the others are disabled (greyed out). Any suggestions ?