14279 Views 81 Replies Latest reply: Aug 12, 2011 5:33 AM by Nicholas Roberts
Currently Being ModeratedMar 25, 2011 3:18 AM (in response to A A P L)I've got that beat–I don't even plug them in!A collection of clinking, clanking, clattering caliginous junk., Mac OS 8.6 or Earlier, PDP11
Currently Being ModeratedMar 25, 2011 3:27 AM (in response to a brody)Not to be too snarky but Peter and a couple of others are on to something about credibility. Straight from the TOU:
"5. Test your answer. When possible, make sure your Submission works on your own computer before you post it."
I think this is why some folks limit themselves to answering only in forums where they have the requisite hardware, software and experienceA collection of clinking, clanking, clattering caliginous junk., Mac OS 8.6 or Earlier, PDP11
Currently Being ModeratedMar 25, 2011 3:30 AM (in response to R C-R)Doh! Missed this before I replied but you are spot on.A collection of clinking, clanking, clattering caliginous junk., Mac OS 8.6 or Earlier, PDP11
Currently Being ModeratedMar 26, 2011 6:25 AM (in response to benwiggy)
The fact that only some people experience the bug is not necessarily an indicator that the update is blameless. Plenty of bugs affect only some combinations of hardware and software.
True, but often the bug is not in the update & instead somewhere in a common set of third party softwares that many users have installed.
Sometimes the only way we discover this is through user reports that include info about what they have installed on their Macs more detailed that the common "all my software is up to date," which may be true but doesn't automatically preclude it all as the source of the problem. The same sometimes applies to the bugs that really are in an update & affect only some hardware/software combinations.
It is like any other murder mystery: the more info we have to work with, the better are our chances of solving the mystery.2008 iMacs: 24"/3.06 GHz + 20"/2.66 GHz; White MacBook/2.4 GHz, Mac OS X (10.6.7), Kensington Trackball; Airport Extreme 802.11n; assorted iPods and older Macs
Currently Being ModeratedMar 26, 2011 9:37 AM (in response to a brody)I have been a Mac user and advocate since the Mac Plus. And it
does seem like as time went on, there seemed to be more and more
problems with OSX. Well yes, the number of problems have increased
but put a little perspective on it.
OSX is made up of millions of lines of code. There are thousands of
applications out there for the Mac. Many of them with 100's of thousands
of lines of code. There are many more configurations of Mac hardware now.
Multiply all that by the millions of Macs out there. Then multiply that by the
number of users on those Macs.
So with that said, statistics would tell you that you could get thousands of
users with problems. Any engineer will tell you, no matter how well you design
something, there will always be someone who will break it. Even Rolls Royces break down!
So, as the original poster stated, you should just have a plan because you may
be the unfortunate one to have a problem.2.4 GHz Macbook (early 2008), Mac OS X (10.6.7), iMac 24"(9.1),Mac Mini(2010),iPod touch(3G),Airport Extreme802.11N
Currently Being ModeratedMar 26, 2011 7:11 PM (in response to woodmeister50)Well most of the updates lately are not osx but having osx work with iphones, iosx, etc etc.
That is all good. I have not updated to 10.6.7 just because I am not in a hurry to. Will let some time go by. Read the forums and do it when I feel good about it.imac intel 3.06, Mac OS X (10.6.3), windows switcher 3/8/05
Currently Being ModeratedAug 12, 2011 5:33 AM (in response to woodmeister50)
I have exactly the same freezing problem with MacMini(2010)/iTunes/hdmi/Dolby from 10.6.7. Hoped Lion would fix it but no. Did you find any solution? I have given up on iTunes and now use Plex.