Is this simply a case a developer signature expiring, and publishing a rerelease? If so, Is my new MacOSXUpdCombo10.6.8.dmg also going to expire? It's just nice not to have to wait to re-download something from a crappy link for hours only to discover it timed out at less than 5%. It turns out the MacOSXUpdCombo10.6.8.dmg available online is not quite the same as the one I had previously downloaded, the file size was slightly smaller, and the creation date later. I went to run the 10.6.8 update, only to get an installation failure with an "unknown error": I already had saved a copy of the MacOSXUpdCombo10.6.8.dmg on the same drive with my 10.6.2 Install Volume, and the 10.6.2 install had run smoothly. I found an identical thread: but there was no clear answer to the problem, and I did not want to go through hours of a slower-than-my-normal-internet-speed download from ![]() It was during the 10.6.8 Update Combo v1.1, after the install, that I encountered a problem. I already have an old mac mini on my desk running MacOSX10.6.8, but rather than copying over my hard drive, I decided to do a fresh install. ![]() I was looking to set it up as a media-station/test-machine, and was thinking Snow Leopard would be perfect. I recently received an old iMac 27" aluminum unibody core 2 duo (EMC 2309: 2009 model) that was having troubles with the graphics card after High Sierra installation.
0 Comments
Leave a Reply. |