Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Didnt have that problem at all, basically nothing changed for me when I installed them.

It doesn't matter much either way, the point is it seems like there's no way to run the new nvidia drivers with this latest beta.
 
It doesn't matter much either way, the point is it seems like there's no way to run the new nvidia drivers with this latest beta.

Discussed here:

If you have installed a web driver from NVIDIA, it is likely that the OS update from Apple will overwrite them. Now that the stock drivers from Apple will still let your card function, this is not a deal breaker. You should NOT attempt to make drivers from one OS release work with a new OS release in general, since the drivers are closely tied to the frameworks that shipped with the version of the OS that the driver was intended for. Trying to force the 10.8.1 web driver to work with 10.8.2, for example, is just asking for trouble and will probably make your machine no longer boot to the desktop.

Granted, now that the NVIDIA driver installs side-by-side with the stock Apple driver there's less chance you'll prevent your system from booting, but the basic point still stands.
 
Yep, I'm aware that it's not recommended. But Apple's drivers are causing problems for me and honestly at this point I'm desperate enough to want to try the new ones from nvidia.
 
Yep, I'm aware that it's not recommended. But Apple's drivers are causing problems for me and honestly at this point I'm desperate enough to want to try the new ones from nvidia.

Go back to 10.8.3 then? The NVIDIA drivers will work fine on that OS release (12D78).
 
Do you use your Mac for real work, or just for startup/shutdown benchmarks?

I also don't understand what the issue is, really - I can't even remember the last time I shut down my Mac apart from when I was leaving for long holidays...and no, it doesn't take longer than some 5-10 seconds.

----------

Those articles are a bit outdated and no longer relevant. Prior to Lion 10.7.2 one could access the PW by using direct memory access (DMA) through either Firewire or Thunderbolt. However, DMA access was blocked in 10.7.2, so the software mentioned in those articles will not work if you have an updated system.

At this point a hackers only hope is to chill the RAM and quickly swap it into a compatible machine to grab the PW from RAM. I have seen Youtube vids of this on Windows machines, but never a Mac. So I think at this point we would have to call this method "theoretical."

Of course if you have a newer machine like a Macbook Air with the RAM soldered in, this method is also off the table.

Not to mention that you're talking about someone having PHYSICAL access to your computer...in other words, this would never happen unless someone actually broke into your house.
 
What you find minor is not minor to others, especially for a premium product designed to give the smoothest and cleanest experience possible. The degree of importance you personally place on it in your specific circumstance is irrelevant; it's an issue for people using a premium product, one that's persisted and is noticeable, and needs to be corrected. End of story.
I suppose our impressions of Macs and their selling points were far different then. I did not make a purchase because the device shuts down quickly. I bought my machine for the numerous other features it provides. I also don't buy the whole "I bought a premium product" argument. You bought a computer. It has bugs. Apple fixes them at their discretion based on importance and ability.
Count me out of that 'most'.
Ok.
 
I did not make a purchase because the device shuts down quickly. I bought my machine for the numerous other features it provides.

But for some of us, we bought our machines working a certain way, then Apple took something away (quick reboots/shut downs).

We aren't bitching about feature changes like merging iOS with OSX - those are by design and are inherently going to happen. We're talking about a blatant, easily replicable and totally ignored "oversight" in the code.

Granted, it's been many years since I've developed or coded but I do know this... if you can repeat a bug every time and have system logs that easily pinpoint where the problem is, you simply squash it - and don't ignore it. Perhaps coding ethics have changed but I could never work this way.
 
Those people who don't care about shutdown times, and leave their Macs in a sleep mode all day, probably don't take the Macs out of their houses. They also aren't aware that even if the Mac is encrypted with FileVault2, if a thief gets hold of the Mac in sleep mode, it is not as secure as if it were stolen when totally shut down.
Sleep mode is more likely to be used on notebooks than on desktops for the simple fact that people are on the move and it is much faster to sleep/wake the machine than it it is to boot/shutdown. It is less useful on desktops than on notebooks because they can run the entire day since they are not going to go anywhere.

Filevault 2 isn't as bad as you think it is. There are some problems because with things like whole disk encryption the decryption key is usually stored temporarily in memory. You'd need direct access to it to be able to retrieve it. There are various mechanisms that actually prevent this from happening. The machine turned off is only a tad bit better. However, there are many other ways of getting the data even with something like Filevault 2 turned on and the machine turned off. If your password isn't very strong than brute forcing it is easy.
Also, the question remains if you actually should secure your Mac this way. A thief is more likely to use the machine if there is little security that prevents him from doing so. That gives you a much higher chance of retrieving your Mac. If you want to secure certain pieces of data than you could opt for something like secured dmg or TrueCrypt (of course with a proper password or even passphrase).

Given this fact, those people who rather pompously brushed aside those who value fast-shutdown times, need to reconsider their stance.
As do people who are pointing out a security problem. There are many ways of getting into a machine and to the data you want. I do agree that shutting down a machine has definitely got its benefits (just to name something: when the machine is properly off it doesn't use power which shaves off a little bit of the electric bill). However, "fast" is very subjective which is what people here need to understand. The way it works now is fast enough for me. What I dislike is how much time it needs to boot and login when using the "reopen all windows" option. Also, the 10s delay when waking my MBA is a bit annoying at times (luckily you can influence this at the cost of a more power hungry machine when in sleepmode).

To those who lazily just put their Macs to sleep -- and, in their ignorance, BRAG about it -- educate yourself and do this google search:

mac vulnerable sleep shutdown filevault 2
Practice what you preach. If you actually search and read you'd have learned that you are exaggerating. If we are talking about security risks than there are many more, even when the machine is completely shutdown.

And whilst Apple are at it fixing ML 10.8.4, they might address this security issue that sleeping Macs have.
This shows how little understanding you have about this issue. They have already addressed it and it's all they can do. This "issue" is something that can not be fixed.
 
Last edited:
We aren't bitching about feature changes like merging iOS with OSX - those are by design and are inherently going to happen. We're talking about a blatant, easily replicable and totally ignored "oversight" in the code.

But perhaps we are. After all, how often do you reboot your iPhone or iPad? I'd say rarely to never in my case, and the slow shutdowns are irrelevant there. So perhaps Apple's new approach is we should use our comps as we do our mobiles?? (I say this facetiously)
 
... I did not make a purchase because the device shuts down quickly. ... I also don't buy the whole "I bought a premium product" argument. You bought a computer. It has bugs...

I did't buy a machine for its shut down time either. With apologies to both manufacturers, I paid for a Rolls Royce, I was delivered a Tuk-Tuk. The bugs that prevent/slow shut down were delivered as part of Mountain Lion. My gripe is the rubbish in that version of OSX that causes me to have to shut down many times a day, which has been the case and not fixed since the first release of said software. More - Crab-Apple than Apple - that is, totally unpalatable.
 
So perhaps Apple's new approach is we should use our comps as we do our mobiles??
Well, if you're saying Apple is trying to "force" people into sleeping their OSX machines I'd ask why? Macs have a much greater power draw and they are certainly not iPhones or iPads. Besides, if this were truly Apple's intent, the Power Button would behave just like an iOS device and it doesn't.

Nope. Apple screwed up and more importantly, they don't care. It's really that simple. But to your point, Shutting down Windows 8 takes a whole freaking lot of mouse clicks.

(I say this facetiously)

Understood. :)
 
:confused:

1.) Move mouse to corner - expose charm
2.) Click on "gear"
3.) Click on "power"
4.) Click on Shutdown.

I count "4" unique mouse movements.

Isn't that the same exact amount as osx?

1) Move mouse to corner
2) Click on Apple
3) Click on Shutdown
4) Click on Confirm

If there was a default way to shut down in two mouse clicks from anywhere there'd probably be a whole lot of cases of people randomly shutting down their computers.
 
Why updates past 10.8.1 suck!

My biggest gripe with updates following 10.8.1 is removal of ability to keep the MBP's internal display turned off while keep the lid open in clamshell mode.

In 10.8.1, you just had to enter "sudo nvram boot-args=iog=0x0" command in terminal to restore the screen behavior to what we had in 10.6. But Apple decided to **** it up in 10.8.2 and further releases and now it'll most likely never be fixed.

Thanks Apple!:rolleyes:
 
Have a feeling that the 10.8.4 update will release right beside OS X 10.9 developer preview during WWDC - June 10, 2013.
 
:confused:

1.) Move mouse to corner - expose charm
2.) Click on "gear"
3.) Click on "power"
4.) Click on Shutdown.

I count "4" unique mouse movements.
Sorry, I should have said 3 clicks, but it certainly isn't a 'whole freaking lot of mouse clicks' as you stated before.
Same as OS X, in fact.
 
Isn't that the same exact amount as osx?

1) Move mouse to corner
2) Click on Apple
3) Click on Shutdown
4) Click on Confirm

If there was a default way to shut down in two mouse clicks from anywhere there'd probably be a whole lot of cases of people randomly shutting down their computers.

1. Hit Power Button
2. Hit Enter.
 
Under Windows 7 [ not running 8 ATM ] Press the Power button [ configured under power settings ] and computer shuts off. That's it!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.