No. A logic board in a MBP with a defective NVIDIA GPU is a bricked motherboard. NVRAM is just a software problem. Or do you mean a defective NVRAM chip!?
With a defective NVRAM chip.
No. A logic board in a MBP with a defective NVIDIA GPU is a bricked motherboard. NVRAM is just a software problem. Or do you mean a defective NVRAM chip!?
They do release small updates rapidly when there is a severe issue affecting lots of people. I don't think there are any major issues in 10.8.2 that require hotpatching.So what if the customer received a product that *DOES NOT* work correctly? Are you saying that Apple is so concerned with being unobtrusive that it withholds crucial updates for several months on end as a "convenience" to their customers? That makes perfect sense.
Shutdown time is much faster than previous beta here.
Safari will be snap... - better.
There are so many file system bugs and other serious issues in finder I frankly don't care if it gets to 50 beta.
imho 10.8.2 is one of the worst releases Apple has available for the last 2 years. It's like dealing with windows style issues..
![]()
I can't wait to see the stories about how many security and bugs there are in 10.8.3 after the stable version goes live.![]()
Has the lower shutdown time being more consistent on this beta?
As for me, I just want Apple to not rush this update and takes its time to make it a good one. I think that what Apple needs is to safe guard OS X's quality, which has suffered a lot since iOS took the center stage after the release of the iPad. To me I always see OS X as the insurance policy for Apple if iOS becomes a sinking ship.
Hmm second time shutdown was slow as hell again. I guess they didn't fix it..
Do these betas include a new version of Safari that renders pages faster on rMBPs? (i.e. the "Webkit" version)
This does not make any sense, what the hell are they fixing in a point release that needs ELEVEN betas??????
They already had the chance with 10.8.2 + 11 builds of 10.8.3.
I guess they don't want to fix it!
Or possibly that it's so low on the priority list that nobody is working on that one. Remember that at any time there are thousands of bugs reported for any build of OS X. These bugs get into a priority list depending on the severity. If a bug crashes hard drives and results in data loss, it's priority number 1 etc. Stuff like "the computer isn't shutting down fast enough" is extremely unimportant compared to other more serious issues.
Always an explanation.
Of course. Do you think you are the only one reporting bugs to Apple? I have reported probably 20 minor bugs after Mountain Lion. Only one was fixed so far. None of them are crucial things though. Mostly UI glitches.
EDIT Most of the issues I've seen people complain about, above, have been addressed - That being said, you'd all be complaining if they missed something in a hurry to rush this out![]()
Or possibly that it's so low on the priority list that nobody is working on that one. Remember that at any time there are thousands of bugs reported for any build of OS X. These bugs get into a priority list depending on the severity. If a bug crashes hard drives and results in data loss, it's priority number 1 etc. Stuff like "the computer isn't shutting down fast enough" is extremely unimportant compared to other more serious issues.
Well, what do your console logs show?Hmm second time shutdown was slow as hell again. I guess they didn't fix it..
Sure this is not a big issue, but pure sloppines!
And for some reason people do seem to bother. Look at the two threads dealing with this issue on Macrumors alone - they nearly received 70.000 views.
And why, because this is one of the core values of a Mac that was lost -> faster shutdown times than a PC![]()