Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Releases Mac OS X 10.6.8

Hirth said:
Personally, I find posts complaining about other people's posts or post "types" to be lamer than the posts the complainer is complaining about. Such posts tend not to solve the original irritant and instead spawn a meta-discussion about the futility of posting to stop people posting. Then that spawns a discussion about the futility of posting to stop people posting to stop posting. And so on. Metas all the way down. Cheers. :)
Click to expand...

I like that someone dislikes this post.
 
peapody said:
Well I updated my macbook pro 2.4ghz 8600m GT...

When it was on 10.6.7 it was flawless. I just started doing the software updates for it today..

And then downloaded the latest release and my screen got strange dark ripples on the bottom half. I know my mbp has the faulty chip. After going back to 10.6.7, screen looks perfect again. Hard to say if this is the chip problem or a problem with the update. Who knows. Will be testing and following closely for a while.
Click to expand...

I had this problem some time ago. I fixed it with the following procedure. It never occurred again....

Press Control - Shift - Eject.
After the display goes to sleep, wake it by pressing any key on the keyboard.
 
10.6.8 issue

I am frustrated with 10.6.8 while running x-plane 9.70 the sim loaded and ran perfectly on 10.6.7 and as soon as 10.6.8 was ready to go, I get an error code saying problem opening/loading OpenGL and the sim 9/10 times crashes or 1/10 runs but very slow and then crashes.


any way to go back to 10.6.7? I have a timemachine backup, yet only of current 10.6.8 due to disk being full. how can i go back to 10.6.7 and then transfer what i want OR transfer everything yet enable 10.6.7?


thanks

* i called apple but PST is annoying so have to wait until tomorrow, also emailed xplane tech support
 
boneske said:
You may not of brought Microsoft Windows into the conversation, but it is a perfect example to understand the difference between marketing names and product versioning numbers. It is actually a very easy concept that you seem to fail to grasp, so here is a list of the Windows NT family that list both its versioning numbers and marketing names:

http://en.wikipedia.org/wiki/Windows_NT#Releases

We can play the numbers game all day long, but in the end it's up to the developers(or a company in this case) to decide what is consider a "major release" and what is a "point release."
Click to expand...

Since you quoted wikipedia, Apple seems to disagree with you..

http://en.wikipedia.org/wiki/Software_versioning

Apple
Apple has a formalised version number structure based around the NumVersion struct, which specifies a one- or two-digit major version, a one-digit minor version, a one-digit "bug" (i.e. revision) version, a stage indicator (drawn from the set development/prealpha, alpha, beta and final/release), and a one-byte (i.e. having values in the range 0–255) pre-release version, which is only used at stages prior to final. In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with "final" being considered the zero stage), thus writing 1.0.2b12, 1.0.2 (rather than 1.0.2f0), and 1.1 (rather than 1.1.0f0)
 
AidenShaw said:
But its not "NT(n)/2000/XP/Vista/7/",
it's
Microsoft Windows NT™
Microsoft Windows 2000™
Microsoft Windows XP™
Microsoft Windows Vista™
Microsoft Windows 7™​

Makes sense to me, or at least as much sense as
Click to expand...

Or as little.

At least the Mac OS X named releases have been clearly associated with a progressing series of 10.1, 10.2, 10.3, etc.

Apple OSX Cheetah™
Apple OSX Puma™
Apple OSX Jaguar™
Apple OSX Panther™
Apple OSX Tiger™
Apple OSX Leopard™
Apple OSX Snow Leopard™
Apple OSX Lion™​

As if the name really matters! And ignore the idiots who claim that Win7 is Windows NT 6.1 - they're clueless from the get-go.
Click to expand...

Let's not talk for now about Linux history of numerology...
 
Improvements for me. 10.6.8 seems to work fine on my 2008 MBP (logic board already replaced for Nvidia chip of death by the way), and on my 2011. On the Early 2008, it was a 275MB download and uneventful. On the 2011, it was a 475MB download, and it restores clamshell mode and deep sleep with my external monitor through a DVI adapter although the switching on after sleep is still a bit glitchy.

I noticed an earlier posting commenting on inaccurate reporting of percentage, battery power from Bluetooth devices. A few weeks ago I had noticed that while the OS was still on 100 percent, iStat was reporting the 80s, then the 70s, then the 60s. Now I'm noticing that the OS is currently giving a battery power report in the high 70s, while iStat reports it in the high 40s. Interesting. I wonder what the difference is.
 
motulist said:
Okay guys, if you wanna make stupid jokes, then fine, but don't mischaracterize what I said. I CLEARLY posed it as a REQUEST, not a command. And I was very polite about it. If you don't want to be not annoying, then you're free to be a douche if you so please.
Click to expand...

I find no matter how polite I'm being, people don't like me telling them what to do... even if I phrase it in the form of a request.
 
ABG said:
Same here.
Click to expand...

My Time Machine is working perfectly and doing so over the network on a drive connected to my G4. The update has created a total of 1.36GB of extra data on the HD total after install for TM to backup.
 
AidenShaw said:
Does that mean that 10.6.8 works on PPC Apples, but not Intel Apples?
Click to expand...

HUH? 10.6 doesn't even run on PowerPC. re read my post. It says over the network on a drive connected to my G4. The drive backs up the Intel MacBook.

You posted before I edited to make it more clear.
 
Avalontor said:
Since you quoted wikipedia, Apple seems to disagree with you..

http://en.wikipedia.org/wiki/Software_versioning

Apple
Apple has a formalised version number structure based around the NumVersion struct, which specifies a one- or two-digit major version, a one-digit minor version, a one-digit "bug" (i.e. revision) version, a stage indicator (drawn from the set development/prealpha, alpha, beta and final/release), and a one-byte (i.e. having values in the range 0–255) pre-release version, which is only used at stages prior to final. In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with "final" being considered the zero stage), thus writing 1.0.2b12, 1.0.2 (rather than 1.0.2f0), and 1.1 (rather than 1.1.0f0)
Click to expand...

LOL, not really since I said and I quote "We can play the numbers game all day long, but in the end it's up to the developers(or a company in this case) to decide what is consider a "major release" and what is a "point release.""

Apple has a very different product versioning number and marketing name scheme than Microsoft, but it is still very easy to comprehend. With Apple 10.x is a major release and gets a marketing name while 10.x.x is a point release and doesn't get a marketing name. With Microsoft, Windows NT 5.0 and 6.1(or XP and 7 in marketing names) are major releases and get marketing names, while service packs are point releases and don't get marketing names. See not that hard to comprehend.
 
Last edited:
bconeill said:
Anyone else having printing issues since this update? Each print in the queue pauses and gives me the "!" in front of the printer.

Anyone? Anyone? Bueller?
Click to expand...

Another one here.

In two different Macs, I lost the capability to print to my Konica Minolta c353 printer. The Macs are: mid-2010 Macbook Pro 15" and a mid-2010 Mac mini Server. "Printer paused" is what happens. The logs say:

Backend returned status -8 (crashed)
Printer stopped due to backend errors

Interestingly, in the Macbook Pro I have a Windows 7 running on top of Parallels and the printer works just fine from any Windows program.

Hope Apple is reading this, as well as the Feedback I also sent them.

I have already seen 3 cases of this over the web:

https://discussions.apple.com/thread/3137602?tstart=0
 
AidenShaw said:
Which "Linux" - there are quite a few, and none of them use the same naming conventions....
Click to expand...

There's only 1 Linux. Unless you mean those things called Distributions...

Anyway, the kernel versioning itself is all over the place. 2.6 is an especially nasty tree of major/minor releases all mixed up together.
 
AidenShaw said:
Just go back to the most recent "system restore point", and wait for the bozos at Apple to fix their cock-up.
Click to expand...

:)

zen.state said:
My Time Machine is working perfectly and doing so over the network on a drive connected to my G4. The update has created a total of 1.36GB of extra data on the HD total after install for TM to backup.
Click to expand...

Working fine on my three MBP's, all of which use the same Readynas as a time machine drive.

AidenShaw said:
Does that mean that 10.6.8 works on PPC Apples, but not Intel Apples?
Click to expand...

See above :)
 
Did the update...boring. Nothing to report...which is good. :)

Gonna take this restart opportuniy to do a final spring clean/maintenance of my mac.
 
Eidorian said:
The network storage for Time Machine is more than likely running on a G4 based machine but it is not Snow Leopard itself on that remote machine.
Click to expand...

Exactly. The G4 is running 10.5.8. It has 3.5 TB storage in it so what better place to backup my MacBook and the G4.
 
Just installed it, no problem...as usual :)

A side note worth mentioning as I see others are having problems with Time Machine, I have the Time Capsule and Time Machine is working fine. Its backing up the download now.
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back