It installed apparently fine clicking the Open button for iMovie in the Updates panel of App Store starts the app, although (unlike on the MBP) there is no iMovie icon in Applications on the Mac Pro. This morning, when I booted my Mac Pro to run the daily incremental backup of my MBP using Retrospect 12.5, I saw-as I had expected-that App Store was showing iMovie 10.1 as being available for the Mac Pro. 0-meaning its own bugs have not yet been fixed. Also, in last paragraph, changed two references to OS X 10.11.0 in order to emphasize that this initial release of OS X 10.11 has (implicit) "bug fix suffix". P.S.: Added little clarifying words, plus parenthetical remark in next-to-last sentence about non-Retina displays seeming to be a problem for OS X 10.11.0. ![]() ![]() So I could upgrade, but the App Store problem is not important enough for me to make it worthwhile. Other threads in this forum seem to indicate that many of the problems are with apps that have not yet been updated for OS X 10.11, and that many of the other OS X 10.11.0 problems are with hardware features that I don't have (but my MBP is non-Retina, which is a non-feature that seems to be a problem). I see no reason to make an exception to my policy for OS X 10.11.0. You can call that fuddy-duddyism I call it 25 years of experience as a Mac OS user. My explanation of why I do not intend to update to OS X 10.11 at this time will fit in one short sentence: it has long been my policy not to update to a new not-limited-to-bug-fixes version of Mac OS X until the bug fix suffix for that version is at least. So Apple must fix the App Store so that it will still be able to handle Updates to OS X < 10.11 machines using App Store App 2.0, and I trust it will once people like me have made it aware of the problem. I exclude the possibility of Apple's intentionally causing this problem to force all users to update to OS X 10.11 even Brand M has learned to avoid the user backlash from their attempts to pull stunts of that sort. This, IMHO, is likely to be caused by either (a) a coding change in the App Store to accommodate Mac OS X 10.11 or (b) a mis-reconfiguration of the App Store-probably inadvertently resulting from (a)-causing the App Store to no longer be able to handle Updates to OS X < 10.11 machines using App Store App 2.0. (3) Thus we are led to a problem with the App Store itself. Are you hypothesizing parallel bit-rot on both copies, or an emerging date-related bug? Barring those remote possibilities, it's not likely to be a problem with the App Store App. (2) The App Store App 2.0 worked fine for downloading and installing Updates on both my MBP and my Mac Pro until the week before last. I will, however, search for a free VPN-which I didn't realize existed. (1) Per my second paragraph quoted in this post, it's not likely to be a local networking problem. I only posted the problem because other people running OS X < 10.11 might be hurt. One thing to keep in mind per the last sentence of my first paragraph quoted in this post, I don't particularly care if this problem is fixed quickly. With my prodding them, Apple will fix it eventually. I suspect this problem, too, is an example of a complicated "conceptual bug" resulting from changes to App Store for OS X 10.11. As I said, that problem cleared up after about a week, despite my not having done anything about it. The temporarily-difficult-to-grasp (for Apple) concept being that someone might use the App Store for free downloads but never buy anything there. covered by Verizon.īTW, thank you in your post for unintentionally classifying the problem I had with App Store in July as a canonical example of a "conceptual bug". So maybe "confined to the area you are in" is true, if you define "the area you are in" as anywhere in the U.S.A. OTOH years ago Hawaii used to be covered by GTE, but I think GTE's phone system was subsequently sold to Verizon. So this is not "likely to be a local networking problem confined to the area you are in". And Iowa-where LtKernelPanic who reported also having the problem in a post just after yours resides-is also a long way from NYC. It may not look that way from across the Pond, but Hawaii-where Carhole (as linked to in my second post in this thread) resides-is a long way from New York City. The fact is I don't use GarageBand even on my MacBook Pro I just like to keep my apps updated. As you-Joel_B-should well know by now, my little two-room apartment LAN is connected to DSL from big old Verizon. ![]() I think my youngest brother has Time Warner. Given that the MacBook Pro is a laptop, I could eventually haul it up to one of my brothers' apartments and try accessing App Store from there. Since I am retired, I don't have access to a VPN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |