Mac OS X 10.6 Snow Leopard Shipping in September: $29 for Leopard Users

[macuserx86]

If you can claim that there are a million legal ways to acquire full bandwidth HD content (not some pirated Handbrake'd rips) please post some URLs. I'm interested.

I don't think he meant legal.

 

[HyperZboy]

Tiger (10.4.11) is a stable and powerful OS, and one that I still find useful on a daily basic.

It will be nice to have SL on my primary unit, but chances are, you're not going to need the most up-to-date system on every computer you own.

These are very valuable points and the very reason for Snow Leopard's creation....... BLOATED SYSTEM.

I have Panther, Tiger, & Leopard partitions on multiple Macs and TIGER by FAR runs the BEST on every PowerPC Mac I own.

Since the 10.5.7 update, the Leopard kernel panics & most of the other anomalies have stopped and Leopard is stable on every PowerPC Mac I own, but it's hardly as lean and mean as Tiger and nowhere near as fast on any of my PowerPC machines.

Snow Leopard appears to be a FIX for the BLOATED SYSTEM problem, by shedding PPC files and support. Once again, I think its great for INTEL machine owners, but 20-25% of the Mac population still are NOT INTEL Mac owners.

 

[RebootD]

If you can claim that there are a million legal ways to acquire full bandwidth HD content (not some pirated Handbrake'd rips) please post some URLs. I'm interested.

Make sure that they have the original menus, extras, and other bits. And of course, the original lossless 7.1 channel 96 KHz/24-bit soundtrack.

EXACTLY! Plus I create digital media for a living so I cannot condone the illegal ripping/torrent downloading of videos on the net because it is stealing someones income. If I asked them if going into a Best Buy and taking a few movies off the shelf and walking out is wrong they will say "Yes!" but stealing them off the net is fine? Hypocrites.

Moral (or lack there of) issues aside right now there isn't even the infrastructure in place to handle BD quality video/audio downloads or streaming in the US outside of FIoS and that is 50 Mb/s (doubt it is sustained speed while downloading), while BD push up to 25-40 Mb/s video and 1.5-7 Mb/s audio so it would eat nearly 100% of your bandwidth to stream a single film. I've watched someones torrent of 'HD' and it looked like garbage. Even Comcasts' HD OnDemand looks like a poorly upscaled DVD compared to BD movies.

I'd be happy to get rid of physical media but until we can get upwards near 100 Mb/s & average consumers have small server farms with 10TBs of hard drive space to store all of these films I don't see people burning their movies in the street and sitting around downloading Blade III HD for 6-12hrs before they can watch it.

 

[Ben Logan]

This is the type of comment that makes Windows and Linux users scoff at Mac users. "I just want a pretty interface, but instead they did a major internal overhaul, boosted performance, and set the stage for massive multicore support. What a gyp!" A new UI is not worth $129 to most sane people; it's something I could see people legitimately calling a service pack.

Alrighty. Guilty as charged! Just being honest though: that rumored marble interface was what had me most excited for Snow Leopard. I'm a windows and linux user too. My mac certainly has the best workflow. I love the idea of having the mac workflow wrapped up in a new visual package. Still hoping for it. Boo-ya!

 

[quinntaylor]

Apple made a big hoo-ha about 64-bit computing when the G5 machines first sprouted. But those machines will never get to see a 64-bit kernel. Slight irony there, I think.

A slight irony, yes, but not so meaningful as it might appear at first. The reason Apple made a big deal of 64-bit back then was the ginormous memory space, which is truly a big deal for scientific applications and others that need to map load of memory. However, a 64-bit kernel is much less beneficial for a PPC machine. Can anyone arguing for SL on PPC (particularly G5s) actually pinpoint what benefit they'd expect to see from a top-to-bottom 64-bit OS?

For people that have truly large investments in G5s (such as clusters or large labs full of them) they don't really care about the kernel, or probably even 64-bit Cocoa in Leopard — they care about the 64-bit Unix layer in Tiger, and cranking out computation with extremely large data sets. On the flip side, those with older PowerPC machines have pretty much accepted the fact that there's a glass ceiling beyond which their hardware won't be supported. Remember the "hoo-hah" when G3's weren't supported in Leopard? That was a big deal in 2007, but 2 years past that and G4 and G5 are on the chopping block.

Sure, it would be nice if old hardware could run the newest software unmodified, but that's unlikely to happen. Remember that Apple is a hardware company. Driving new hardware sales is not ripping off consumers. If your old computer suddenly ceased to function at a deadline of Apple's choosing, then you'd have a case. As it is, people who complain about being left in the lurch with (for example) $10K of latest model PPC hardware (some of which was purchased after the Intel transition was announced) leave me wondering if they pay any attention to technology trends. Misguided assumptions of support timelines on the user's part does not constitute a breach of trust on Apple's part, end of story.

 

[HyperZboy]

Leopard for PowerPC is pretty stable for me at 10.5.7 finally, but...

Why do I get this mess every time I run disk permissions in Disk Utility?

"Repairing permissions for “MacOSX”
Reading permissions database.
Reading the permissions database can take several minutes.

Permissions differ on "System/Library/Frameworks/CoreVideo.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/AirPort Base Station Agent.app/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
User differs on "Applications/Utilities/AirPort Utility.app/Contents/MacOS/AirPort Utility", should be 0, user is 501.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/MacOS/AirPort Utility", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
Permissions differ on "System/Library/Components/CoreMediaAuthoringPrivateComponents.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaAuthoringPrivate.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/AVC.plugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/IIDC.plugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/MPEGAudioDecoder.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/MPEGLayer2AudioEncoder.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/Tundra.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions/A/Resources/VDC.plugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/QuickTime Player.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/MacOS/QuickTime Player", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/MacOS/QuickTime Player", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AnnotationInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/AnnotationInspector.propPane/Contents/MacOS/AnnotationInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AnnotationInspector.propPane/Contents/MacOS/AnnotationInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AudioSettingsInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/AudioSettingsInspector.propPane/Contents/MacOS/AudioSettingsInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AudioSettingsInspector.propPane/Contents/MacOS/AudioSettingsInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/DataRefInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/DataRefInspector.propPane/Contents/MacOS/DataRefInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/DataRefInspector.propPane/Contents/MacOS/DataRefInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/HintTrackInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/HintTrackInspector.propPane/Contents/MacOS/HintTrackInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/HintTrackInspector.propPane/Contents/MacOS/HintTrackInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/NetworkInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/NetworkInspector.propPane/Contents/MacOS/NetworkInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/NetworkInspector.propPane/Contents/MacOS/NetworkInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/SettingsInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/SettingsInspector.propPane/Contents/MacOS/SettingsInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/SettingsInspector.propPane/Contents/MacOS/SettingsInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/VisualTrackInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/QuickTime Player.app/Contents/PlugIns/VisualTrackInspector.propPane/Contents/MacOS/VisualTrackInspector", should be 0, user is 501.
Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/VisualTrackInspector.propPane/Contents/MacOS/VisualTrackInspector", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "System/Library/QuickTime/QuickTimeComponents.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTimeJava/QuickTimeJava.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTime3GPP.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeH264.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeIIDCDigitizer.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeImporters.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeMPEG.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeMPEG4.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeStreaming.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/QuickTime/QuickTimeVR.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Library/Internet Plug-Ins/QuickTime Plugin.plugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Library/Internet Plug-Ins/QuickTime Plugin.webplugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/Frameworks/QTKit.framework/Versions/A/Resources/QTKitIBPlugin.ibplugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/Spotlight/QuickTime.mdimporter/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Library/Audio/Plug-Ins/HAL/iSightAudio.plugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/Frameworks/QuickTime.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTMediaKeys.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTMime.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTTransport.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTPlugIn.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegister.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegister.prefPane/Contents/Resources/QTAbout.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTStreaming.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTUpdate.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
User differs on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/MacOS/InternetUtilities", should be 0, user is 501.
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/MacOS/InternetUtilities", should be -rwxrwxr-x , they are -rwxr-xr-x .
User differs on "Applications/iTunes.app/Contents/Frameworks/iPodUpdater.framework/Versions/A/iPodUpdater", should be 0, user is 501.
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/iPodUpdater.framework/Versions/A/iPodUpdater", should be -rwxrwxr-x , they are -rwxr-xr-x .
User differs on "Applications/iTunes.app/Contents/Frameworks/iPodUpdater.framework/Versions/A/Resources/UpdaterBackEnd", should be 0, user is 501.
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/iPodUpdater.framework/Versions/A/Resources/UpdaterBackEnd", should be -rwxrwxr-x , they are -rwxr-xr-x .
User differs on "Applications/iTunes.app/Contents/MacOS/iTunes", should be 0, user is 501.
Permissions differ on "Applications/iTunes.app/Contents/MacOS/iTunes", should be -rwxrwxr-x , they are -rwxr-xr-x .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/Components/AudioCodecs.component/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
Permissions differ on "System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .

Permissions repair complete
"

This kind of sums up to me that Apple has work to do still with Leopard.
This mess obviously adds insult to injury with all the bug fixes and optimizations in Snow Leopard.

Oh, and yes, I did the 10.5.7 combo update and yes, these disk permissions errors come up on all my PowerPC macs and the are repeatable too.
The disk permissions are never fixed. Makes no sense to me.
(not to mention it takes 10 minutes to repair disk permissions, but we won't go there, grrrrr)

Anyone have an explanation or solution?

 

[satcomer]

Open CL will not work on my macbook. It has an Itel GMX3100

Neither will my Mac Pro with a Radeon 3870.

 

[macuserx86]

Leopard for PowerPC is pretty stable for me at 10.5.7 finally, but...

Why do I get this mess every time I run disk permissions in Disk Utility?

*snip*

Anyone have an explanation or solution?

Uh, because the permissions on those files differ from the norm?
The point of a permissions repair is to fix those permissions. All the means is that Disk Utility is doing it's job, it's not a Leopard problem. Would you prefer to have to defrag your drive all the time, and do fresh installs ever few months?

 

[OrganMusic]

Are you switching to the Finder (click on the finder icon in the dock ) and then invoking FQ or are you trying to invoke FQ when the screwed up app still have primary control over the menus/display?

If your app completely dies there may be no process for FQ to kill off. I suppose if that leaves some attached devices in some voodoo state then a reboot is all you have. Or power off that device and then turn it on again.

Not sure, but I definitely got the force quit dialogue to come up. It listed FCE as "not responding" and no amount of selecting it and clicking "force quit" had any effect.

I ran FCE all day today with my mBox disconnected -- no problems at all, so it must have been something flakey with the mBox drivers. I'll have to look into this matter when I have more time.

So to put a positive spin on things, I really have had very few things hang since I switched to mac. And at least some of them seem to be hardware-related, so one can't necessarily blame the OS. Plus, even when FCE went zombie everything else was still working OK (for a while at least.)

 

[deconstruct60]

A slight irony, yes, but not so meaningful as it might appear at first. The reason Apple made a big deal of 64-bit back then was the ginormous memory space, which is truly a big deal for scientific applications and others that need to map load of memory. However, a 64-bit kernel is much less beneficial for a PPC machine. Can anyone arguing for SL on PPC (particularly G5s) actually pinpoint what benefit they'd expect to see from a top-to-bottom 64-bit OS?

Putting in objects in memory versus on the disk beats the slop out of the alternative (dropping them down to the disk layer ) no matter what the architecture.

Somewhat of a chuckle how 64 bit kernels for PPC are much less beneficial when taking a look at Power5 and Power6 that is pretty much what you see.

Besides SL has GCD which would help PPC also. If get rid of some of the threading overhead all archs go faster. There is no reason why PPC wouldn't benefit equally from that.

Certainly if only had < 2GB sized problems then 64 bits doesn't do much for you on either a Intel or PPC. Don't have to convert pointers when dropping down into the kernel perhaps.

On the flip side, those with older PowerPC machines have pretty much accepted the fact that there's a glass ceiling beyond which their hardware won't be supported. Remember the "hoo-hah" when G3's weren't supported in Leopard? That was a big deal in 2007, but 2 years past that and G4 and G5 are on the chopping block.

It isn't that PPC was to be supported forever, it is that these G5 are being cut short early. As someone previously stated systems purchased at the end of the window are still covered by Applecare. How can something that is under an Applecare contract be "too old to support" by Apple's standards? Normally for Apple systems they get OS updates for 1-2 years after Applecare coverage ends. Go back and look at Apple's track record. That isn't user behaviour that is apple behaviour.

The Core Solo were just as technically obsolete when Apple released them in the exact same time frame as the last G5 were release. The Core was also in the middle of an announced transition. So riddle me this why if use the same rationality of "you should have known it was a transition and not bought anything" not being applied to skipping the 32-bit SL ( and correspondingly having to do 32 Finder and the other 1000 projects they converted to 64 bit purportedly )?

Driving new hardware sales is not ripping off consumers. .... Misguided assumptions of support timelines on the user's part does not constitute a breach of trust on Apple's part, end of story.

Where is the misguided when Apple sells you a support contract that covers 3 years and then says oooh but when it comes to the software for this not too old to support hardware ... it is too old.

I'll give there is no hard contract saying you OS upgrades are required for anything under Applecare. However, to say there isn't a reasonable expectation that stuff currently covered under Applecare won't be classified as a legacy system 'not worth the effort' or that Apple is building trust in that context, is out of the ordinary in the market.

This isn't as much of a problem if Apple simply stretched out security updates for Leopard a bit longer. The problem isn't so much that G5 isn't getting SL. The problem is more so that historically chops off updates to versions "2 version back". If they treat SL as a Leopard extension and don't cut off PPC updates to critical issues that would help.

It is a dual edge sword when there is a transition. Apple has responsibility also. They also knew they were going to get to a point was it was a bit less convenient to support the PPC owners who bought in the transition. Apple has the flexibility to duck their responsibilities here. Cry poverty ... oh where would we possibly find the money....

Mystifying why folks who could have all collectively introduced an Osborne effect on Apple ( skipped buying both Core Solo and G5 stuff for months and set Apple on the rocks because the technology projections said that stuff was a "dead end" ) should get stuck. In the past transitions Apple has taken measures to stick with folks who trusted them.

Driving customers to new hardware. LOL.... you sound like folks from GM from back in the 70's and 80's. Don't build a good car that will last. Build something that is going to crap out in 3-4 years so they HAVE TO come back and buy a new car.

A trustworty vendor offers you something that has more stanstantive value so that you will make the choice to move up. Only cheesy folks with little value to offer want to coerce you to do something without offering a substantive value proposition. ( "I'm going to hold something back from you" is not a value proposition, unless you are in Iceberg Slim mode. )

 

[John Jacob]

Uh, because the permissions on those files differ from the norm?
The point of a permissions repair is to fix those permissions. All the means is that Disk Utility is doing it's job, it's not a Leopard problem. Would you prefer to have to defrag your drive all the time, and do fresh installs ever few months?

Yeah, but it happens every time you run a repair permissions, which means Disk Utility is not doing its job because the permissions are not getting fixed.

 

[gnasher729]

The solution to your problem is very easy: Don't run "Repair Permissions".

Seriously. Why are you running it?

 

[Trinity]

The solution to your problem is very easy: Don't run "Repair Permissions".

Seriously. Why are you running it?

Seriously, why, a personal computer needs permissions?

 

[HyperZboy]

Uh, because the permissions on those files differ from the norm?
The point of a permissions repair is to fix those permissions. All the means is that Disk Utility is doing it's job, it's not a Leopard problem. Would you prefer to have to defrag your drive all the time, and do fresh installs ever few months?

I can repair permissions over and over and I still get the same results and every time I reboot.

Next.......​

 

[swiftaw]

I can't find any mention of Rosetta in Snow Leopard, I assume it must still be there, right?

 

[jmpage2]

Not really. More physical media to mess with, and store. I'm perfectly content to wait online streaming/availablity and take full advantage of the goodies that are already available in this area. If you know what to look for you can avoid wasting your money on Blu ray physical media.

The only way to get the same quality as Blu-Ray without actually getting a Blu-Ray is to download an exact copy through a torrent.

This is called stealing, so let's just come right out and say it, shall we?

 

[Sky Blue]

I posted these here, but no one really goes there.

Not my screens.

The copy dialog now offers a "keep both" option when two files have the same name:

Auto time-zone:

Services are more useful now under contextual menus:

As well as the regular location:

Another example of contextual menus services, set the desktop image from a right click:

Almost everything is 64-bit, these are still 32-bit still (Carbon I suppose):

Airport in the menubar actually shows signal strength, opt+click brings more details than before:

Flash Player is included by default:

If you have an Apple Bluetooth KB, it shows a percentage now instead of the bars:

Preview annotations have received a major upgrade. Lots of things you can customize and do now:

Search result options finally have more sorting options (and you can see screenshots have more useful names):

Movie/Audio/Screen recording in Quicktime 10:

Clippings can finally be copy/pasted and Quick Looked:

You can delay the unlock screen after sleep/screensaver:

Finder can be set to search the current folder by default now:

DMG icon finally 512px:

 

[Sambo110]

The only way to get the same quality as Blu-Ray without actually getting a Blu-Ray is to download an exact copy through a torrent.

This is called stealing, so let's just come right out and say it, shall we?

What about the service that is coming to the 360. Meant to be able to stream full 1080p HD movies, would they be blu ray quality? Hate to think how much of your quota it would eat up though.

 

[danny_w]

I can't find any mention of Rosetta in Snow Leopard, I assume it must still be there, right?

It's there. The latest build before the one released this week had it set for an automatic install if/when needed. I think you can also choose it as a custom install option.

 

[Sambo110]

Clippings can finally be copy/pasted and Quick Looked:


Finally! That annoyed the hell out of me!

 

[MacBrim]

@ skyBlue

great screens thanks!

Is the last beta 10A380 stable enough to use as your main computer?
How is the speed differnce compared to leopard?

 

[Eric S.]

The Core Solo were just as technically obsolete when Apple released them in the exact same time frame as the last G5 were release. The Core was also in the middle of an announced transition. So riddle me this why if use the same rationality of "you should have known it was a transition and not bought anything" not being applied to skipping the 32-bit SL ( and correspondingly having to do 32 Finder and the other 1000 projects they converted to 64 bit purportedly )?

Core Solo and Core Duo systems are next. Expect 10.7 to run only on 64-bit CPUs.

 

[EmperorDarius]

The only way to get the same quality as Blu-Ray without actually getting a Blu-Ray is to download an exact copy through a torrent.

This is called stealing, so let's just come right out and say it, shall we?

What about buying a Blu Ray disc and then downloading the torrent?

 

[jmpage2]

What about buying a Blu Ray disc and then downloading the torrent?

I would have absolutely zero problem with that, but honestly what percentage do that? 1% if you are lucky.

What's worse than people doing said illicit activities is the wink/nudge/smiley that accompanies their acknowledgment of such activity.

BD is expensive because it is the premium audio/video experience currently available. Prices will come down over time, assuming that "starving students" who feel no guilt about ripping off said content don't manage to kill it first.

 

[InvalidUserID]

A reasonably priced Apple product?