I am going to have one splintered OS family in my household.
My 2006 MacPro 1,1 will end its journey at Lion. My MacBook Air currently runs Mountain Lion (DP). However, I need to keep my company MacBook Pro at Snow Leopard.
I'm sure all those cats will get along.
I wonder what the limitations are that prevent the older Macs from running ML?? Does ML require THAT much horsepower just to haul it around?
Too bad, my old late 2006 MBP is still running like it was new. However I never did upgrade it from Leopard since it only has 2Gb of RAM. I wasn't too sure it would be very spunky on the newer OSX versions.
By distributing new versions of OS X solely on the Mac App Store, Apple has also drawn a line in the sand, since Macs not capable of installing at least OS X Snow Leopard 10.6.8 won't be able to access the App Store.
Did this make anyone else besides me scratch their heads?
All intel Macs can run Snow Leopard. I do not understand the point they are trying to make with this paragraph.
By the way this new forum totally sucks. I can't edit my posts, it took me 10 minutes to find where the sig editor is. It does all this crazy inline editing bullshit. Like OS spell check is over written by the forums built in copy and paste functions. Why would you even need copy and pasted built into the web app when every OS natively supports copy and paste. This sucks. FYI.
I wonder what the limitations are that prevent the older Macs from running ML?? Does ML require THAT much horsepower just to haul it around?
Too bad, my old late 2006 MBP is still running like it was new. However I never did upgrade it from Leopard since it only has 2Gb of RAM. I wasn't too sure it would be very spunky on the newer OSX versions.
It's an entirely artificial limitation, as per usual with Apple, trying to force people to upgrade. Only thing is, there's so little in ML that people really need, they're not gonna plonk down $2000+ to upgrade a perfectly usable (and fast) 2006/7 Mac Pro to some "new" Mac Pro that's not been updated in years, which may well end up being unsupported three years down the line. Back in the classic OS period, Macs were supported for 7 years or more, now you're lucky to get 4. Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
There's no reason Apple couldn't either fix the firmware on the Mac Pros they claimed back in 2006/7 to be fully 64 bit, to really be fully 64 bit, or include a 32 bit kernel with ML. It's possible to run 64 bit Windows and Linux on the 32 bit EFI systems, so why can't Apple get OS X to run?
Cost to Apple to update integrated graphics drivers to 64-bit: $50,000
Cost to 1000 customers forced to upgrade their still useful hardware: $1,000,000
Benefit of this policy to Apple executives and shareholders: $1,050,000
Apple to customers: "Screw you."
Customers to Apple: ?????
Forced to upgrade? You mean Apple is holding a gun to your head or your 5+ year old Mac will suffer a seizure and stop working on the day ML comes out?
Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
To quote from an Ars Technica article concerning Windows 8 minimum requirements, "there’s a wide gap between a system that can run Windows 8 and a system that can run it well." From their perspective, the run it well machines would be in the neighborhood of 5 years old and earlier. I've been running Windows 8 preview on a Dell Inspiron e1705, circa 2007 and I'd classify it as run it mediocre. As such, I'd be reticent to tout Microsoft's support for old machines.
Even Macs that can run Mountain Lion are not all able to enjoy all the features. Many 2010 Macs that can install 10.8 still won't be able to run Air Display to mirror the Mac screen via Apple TV to their HDTVs. I was looking forward to that but sadly have a mid 2010 MBP.
By the way this new forum totally sucks. I can't edit my posts, it took me 10 minutes to find where the sig editor is. It does all this crazy inline editing bullshit. Like OS spell check is over written by the forums built in copy and paste functions. Why would you even need copy and pasted built into the web app when every OS natively supports copy and paste. This sucks. FYI.
Absolutely nothing to do with that at all. Upgraded Mac Pros don't work when they have GPUs that support OpenGL 4.
It's an entirely artificial limitation, as per usual with Apple, trying to force people to upgrade. Only thing is, there's so little in ML that people really need, they're not gonna plonk down $2000+ to upgrade a perfectly usable (and fast) 2006/7 Mac Pro to some "new" Mac Pro that's not been updated in years, which may well end up being unsupported three years down the line. Back in the classic OS period, Macs were supported for 7 years or more, now you're lucky to get 4. Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
There's no reason Apple couldn't either fix the firmware on the Mac Pros they claimed back in 2006/7 to be fully 64 bit, to really be fully 64 bit, or include a 32 bit kernel with ML. It's possible to run 64 bit Windows and Linux on the 32 bit EFI systems, so why can't Apple get OS X to run?
The longer they continue to distribute both a 32-bit kernel and a 64-bit kernel, the longer they'll need to spend money developing for and testing both configurations. By limiting themeslves to only the 64-bit code base, they can be more agile responding to future maintenance of the product, while at the same time needing to devote fewer development resources to the task.
Apple supports booting 64-bit Windows on a 64-bit-CPU/32-bit-EFI Mac via Boot Camp because the 32-bit EFI first boots into a BIOS emulation layer, and then the BIOS emulator boots 64-bit Windows. The same technique can be used to install 64-bit Linux on a 64-bit-CPU/32-bit-EFI Mac. In this case, a second-stage bootloader (aka the BIOS emulation layer) interfaces directly with the EFI, and then reverts the CPU back to the legacy 16-bit real mode before loading the real operating system. Once the operating system has made it into its true 64-bit operating mode, all of the legacy runtime services which would have been provided by the 16-bit BIOS have been replaced by OS-specific 64-bit implementations.
Windows supports booting directly from EFI only if you're using UEFI 2.0 or above, and only if it's a 64-bit UEFI.
Linux usually does not directly boot from either EFI or from BIOS; instead, a second-stage bootloader (like GRUB) is booted directly, and then Linux is loaded from there. GRUB supports booting from either 32-bit EFI or 64-bit EFI, but the specific version of GRUB you boot from must be compiled to match the version of EFI: a 32-bit version of GRUB for a 32-bit EFI, and a 64-bit version of GRUB for 64-bit EFI. If you then boot into a 64-bit Linux, then that operating system will not be able to interface with any of the runtime services (http://wiki.phoenix.com/wiki/index.php/EFI_RUNTIME_SERVICES) provided by a 32-bit EFI. (There is work on bypassing the second-stage bootloader to boot directly from EFI to Linux, but it is probably best identified as "experimental" at present.)
Absolutely nothing to do with that at all. Upgraded Mac Pros don't work when they have GPUs that support OpenGL 4.
It's an entirely artificial limitation, as per usual with Apple, trying to force people to upgrade. Only thing is, there's so little in ML that people really need,
Oh, good. So if there's nothing that users of older systems need, there's no harm in the fact that they can't upgrade. I'm glad you established right from the start that you're whining about something that isn't a big deal.
they're not gonna plonk down $2000+ to upgrade a perfectly usable (and fast) 2006/7 Mac Pro to some "new" Mac Pro that's not been updated in years, which may well end up being unsupported three years down the line. Back in the classic OS period, Macs were supported for 7 years or more, now you're lucky to get 4. Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
There's no reason Apple couldn't either fix the firmware on the Mac Pros they claimed back in 2006/7 to be fully 64 bit, to really be fully 64 bit, or include a 32 bit kernel with ML. It's possible to run 64 bit Windows and Linux on the 32 bit EFI systems, so why can't Apple get OS X to run?
Of course there's a reason. It costs money, diverts resources from other projects, and adds complexity. Supporting 2 kernels is time consuming, expensive, and error prone.
I don't doubt that Apple considered that and weighed the advantages against the disadvantages - and concluded that continuing to upgrade the older hardware isn't worth the effort. Part of that is undoubtedly the fact that people with older hardware tend not to be as quick to upgrade as people with newer hardware. If they haven't upgraded to Lion, why would you expect them to upgrade to ML?
Cost to Apple to update integrated graphics drivers to 64-bit: $50,000
Cost to 1000 customers forced to upgrade their still useful hardware: $1,000,000
Benefit of this policy to Apple executives and shareholders: $1,050,000
Apple to customers: "Screw you."
Customers to Apple: ?????
Yes, you can look at it that way. The other way to look at it is that part of the reason OS X is a better choice than Windows is that they don't make an effort to support every POS hardware that has ever been created. At some point, the benefits are too small to outweigh the disadvantages. Supporting older Macs costs money that could better be spent on developing new stuff. It creates problems that affect everyone - not just those who use the older kernel. It adds complexity which slows everything down.
Besides, it's pretty much a moot point. Systems that don't have a 64 bit EFI (like my 2006 MBP) didn't run Lion, either. So if you managed without upgrading to Lion, inability to upgrade to SL probably isn't a big deal - at least for people who don't make a career out of whining about Apple's every move.
Oh, and if you want to talk about costs, let's talk about the people who actually DO upgrade. OSX - $19.99 which you can install on every Mac you own (for personal use). Windows - could be up to 10 times that amount or more, depending on which version - and that's PER computer. So instead of whining about the potential cost for someone who probably wasn't going to upgrade, anyway, why not talk about the costs for the people who actually will do so?
By distributing new versions of OS X solely on the Mac App Store, Apple has also drawn a line in the sand, since Macs not capable of installing at least OS X Snow Leopard 10.6.8 won't be able to access the App Store.
Which eliminates PPC Macs - but they were eliminated a long time ago. If your system can't run SL, then it's hopelessly ancient and you probably weren't going to upgrade, anyway. How many people with systems too old to run SL would even be considering ML?
To quote from an Ars Technica article concerning Windows 8 minimum requirements, "there’s a wide gap between a system that can run Windows 8 and a system that can run it well." From their perspective, the run it well machines would be in the neighborhood of 5 years old and earlier. I've been running Windows 8 preview on a Dell Inspiron e1705, circa 2007 and I'd classify it as run it mediocre. As such, I'd be reticent to tout Microsoft's support for old machines.
I've seen quite a few people saying how well it runs on their old machines, actually. People've been running it on P4s and it's pretty speedy.
The longer they continue to distribute both a 32-bit kernel and a 64-bit kernel, the longer they'll need to spend money developing for and testing both configurations. By limiting themeslves to only the 64-bit code base, they can be more agile responding to future maintenance of the product, while at the same time needing to devote fewer development resources to the task.
Of course Apple's so strapped for cash they can't hire a couple of devs to fix/compile/test the 64 bit kernel on 32-bit EFI machines. The kernel doesnt really change much between releases anyway, so there wouldn't be that much to test. It's mainly the frameworks above the kernel that are modified.
Why was Apple advertising the Mac Pros in 2006 as full 64-bit machines when they weren't? I smell a class action lawsuit ahead. As others have said, if a couple of script kiddies can get ML working without source code on a 1,1/1,2 Mac Pro, why can't Apple do it officially? I am aware of how the BIOS emulation works, but I'm sure Apple could get the 64 bit kernel loaded from a 32 bit EFI if they put their minds to it. They've done some pretty impressive feats in the past, on much less capable hw/sw.
Apple needs to be careful, people pay the "Apple tax" because they expect their machine to be reliable and have a long life; if after a couple of years they starts ditching customers that've spent thousands on a Mac, it's not going to go down too well. It does seem the Mac is getting more and more neglected (400 days without an iMac update?) in favour of iPad and iPhone. Apple's Mac market is small, they can't go about slapping loyal customers in the face lest they lose what share they have. Windows is really starting to look mighty good to many a Mac owner.
Oh, good. So if there's nothing that users of older systems need, there's no harm in the fact that they can't upgrade. I'm glad you established right from the start that you're whining about something that isn't a big deal.
You obviously care enough about it to "whine" in the other direction. What about devs who want to write iOS apps? If Apple's previous actions are anything to go by, the version of Xcode released after ML won't support Lion, so devs're going to need a new Mac to submit apps to Apple. Another artificial limitation to try to force people to fork out more for new hardware.
Apple needs to be careful, people pay the "Apple tax" because they expect their machine to be reliable and have a long life; if after a couple of years they starts ditching customers that've spent thousands on a Mac, it's not going to go down too well. It does seem the Mac is getting more and more neglected (400 days without an iMac update?) in favour of iPad and iPhone. Apple's Mac market is small, they can't go about slapping loyal customers in the face lest they lose what share they have. Windows is really starting to look mighty good to many a Mac owner.
That's silly. They're supporting machines 4 years old and newer.
Since very few people upgrade older computers, anyway, it's really a non-issue.
You obviously care enough about it to "whine" in the other direction. What about devs who want to write iOS apps? If Apple's previous actions are anything to go by, the version of Xcode released after ML won't support Lion, so devs're going to need a new Mac to submit apps to Apple. Another artificial limitation to try to force people to fork out more for new hardware.
I'm not whining about anything - but rather pointing out the flaws in your logic.
As a developer, the cost is minimal. A Mac Mini is $599 and you can sell the old one for $400. So a couple hundred dollars every couple of years. And that even assumes that your negative assumptions are true.
In return for minor inconvenience (inability to upgrade hardware that I never intended to upgrade, anyway and a slight cost for developers), we get the best, most stable, most efficient, most usable consumer OS on the planet. Most Mac users are happy with that trade-off.
That's silly. They're supporting machines 4 years old and newer.
Since very few people upgrade older computers, anyway, it's really a non-issue.
I think you'll find many people with a $5000 Mac Pro 1,1 are on Lion. Even the oldest Mac Pros are fast, faster than some of Apple's latest machines. My Mac Pro 1,1 runs Rage at 40fps no problem, but it needs Lion. What happens when apps are updated to require ML, and autoupdate and break like Apple's botched iPhoto update few weeks back? As I said before and you ignored, why could they support machines for 7 years in the classic era, but not now on a modern OS?
Oh dear! A friend running ML GM tells me a Mac MBP 2010 running Lion with Final Cut Studio and Aperture 3 running, when updated to Mountain Lion GM continues to run both fine. However a fresh installation of ML on the same MBP refuses to install either.
Update. I suggested turning off auto graphic switching ... Waiting to hear if that helped.
If they haven't upgraded to Lion, why would you expect them to upgrade to ML?
Personally, I've held on to Snow Leopard on my 64-bit Intel Mac because I have been reluctant to jump on the bandwagon with newer technology - I've been content to stick with well-supported proven technology. As soon as ML comes out, Snow Leopard will lose all security support, so I plan to upgrade my 64-bit Intel Mac to Lion very soon just so that I can maintain current technical support.
As for my 32-bit Intel Macs... Well, once ML comes out I suppose I will be left with the choice of either relegating them to the trash heap, or else installing an alternate OS which still receives security support such as Windows (I still have a license for XP lying around, and it has more than a year of security support left) or Linux.
Comments
Quote:
Originally Posted by macinthe408
I am going to have one splintered OS family in my household.
My 2006 MacPro 1,1 will end its journey at Lion. My MacBook Air currently runs Mountain Lion (DP). However, I need to keep my company MacBook Pro at Snow Leopard.
I'm sure all those cats will get along.
I wonder what the limitations are that prevent the older Macs from running ML?? Does ML require THAT much horsepower just to haul it around?
Too bad, my old late 2006 MBP is still running like it was new. However I never did upgrade it from Leopard since it only has 2Gb of RAM. I wasn't too sure it would be very spunky on the newer OSX versions.
Is my MBP Retina covered?
Quote:
By distributing new versions of OS X solely on the Mac App Store, Apple has also drawn a line in the sand, since Macs not capable of installing at least OS X Snow Leopard 10.6.8 won't be able to access the App Store.
Did this make anyone else besides me scratch their heads?
All intel Macs can run Snow Leopard. I do not understand the point they are trying to make with this paragraph.
By the way this new forum totally sucks. I can't edit my posts, it took me 10 minutes to find where the sig editor is. It does all this crazy inline editing bullshit. Like OS spell check is over written by the forums built in copy and paste functions. Why would you even need copy and pasted built into the web app when every OS natively supports copy and paste. This sucks. FYI.
Quote:
Originally Posted by Extrema
Cost to Apple to update integrated graphics drivers to 64-bit: $50,000
Cost to 1000 customers forced to upgrade their still useful hardware: $1,000,000
Benefit of this policy to Apple executives and shareholders: $1,050,000
Apple to customers: "Screw you."
Customers to Apple: ?????
Mathematical Wall updating Chipsets that aren't OpenGL 3.x, PRICELESS.
Absolutely nothing to do with that at all. Upgraded Mac Pros don't work when they have GPUs that support OpenGL 4.
It's an entirely artificial limitation, as per usual with Apple, trying to force people to upgrade. Only thing is, there's so little in ML that people really need, they're not gonna plonk down $2000+ to upgrade a perfectly usable (and fast) 2006/7 Mac Pro to some "new" Mac Pro that's not been updated in years, which may well end up being unsupported three years down the line. Back in the classic OS period, Macs were supported for 7 years or more, now you're lucky to get 4. Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
There's no reason Apple couldn't either fix the firmware on the Mac Pros they claimed back in 2006/7 to be fully 64 bit, to really be fully 64 bit, or include a 32 bit kernel with ML. It's possible to run 64 bit Windows and Linux on the 32 bit EFI systems, so why can't Apple get OS X to run?
Quote:
Originally Posted by RichL
There's only one logical choice for OS 10.9:
Aren't pumas and mountain lions the same animal? I think we're just getting a reworked version of OS X 10.1 this month!
Forced to upgrade? You mean Apple is holding a gun to your head or your 5+ year old Mac will suffer a seizure and stop working on the day ML comes out?
To quote from an Ars Technica article concerning Windows 8 minimum requirements, "there’s a wide gap between a system that can run Windows 8 and a system that can run it well." From their perspective, the run it well machines would be in the neighborhood of 5 years old and earlier. I've been running Windows 8 preview on a Dell Inspiron e1705, circa 2007 and I'd classify it as run it mediocre. As such, I'd be reticent to tout Microsoft's support for old machines.
It is horrible to use on an iPad!
Quote:
Originally Posted by Elijahg
Absolutely nothing to do with that at all. Upgraded Mac Pros don't work when they have GPUs that support OpenGL 4.
It's an entirely artificial limitation, as per usual with Apple, trying to force people to upgrade. Only thing is, there's so little in ML that people really need, they're not gonna plonk down $2000+ to upgrade a perfectly usable (and fast) 2006/7 Mac Pro to some "new" Mac Pro that's not been updated in years, which may well end up being unsupported three years down the line. Back in the classic OS period, Macs were supported for 7 years or more, now you're lucky to get 4. Windows 8 can run on 10 year old Machines, because Microsoft doesn't add in artificial limitations.
There's no reason Apple couldn't either fix the firmware on the Mac Pros they claimed back in 2006/7 to be fully 64 bit, to really be fully 64 bit, or include a 32 bit kernel with ML. It's possible to run 64 bit Windows and Linux on the 32 bit EFI systems, so why can't Apple get OS X to run?
The longer they continue to distribute both a 32-bit kernel and a 64-bit kernel, the longer they'll need to spend money developing for and testing both configurations. By limiting themeslves to only the 64-bit code base, they can be more agile responding to future maintenance of the product, while at the same time needing to devote fewer development resources to the task.
Apple supports booting 64-bit Windows on a 64-bit-CPU/32-bit-EFI Mac via Boot Camp because the 32-bit EFI first boots into a BIOS emulation layer, and then the BIOS emulator boots 64-bit Windows. The same technique can be used to install 64-bit Linux on a 64-bit-CPU/32-bit-EFI Mac. In this case, a second-stage bootloader (aka the BIOS emulation layer) interfaces directly with the EFI, and then reverts the CPU back to the legacy 16-bit real mode before loading the real operating system. Once the operating system has made it into its true 64-bit operating mode, all of the legacy runtime services which would have been provided by the 16-bit BIOS have been replaced by OS-specific 64-bit implementations.
Windows supports booting directly from EFI only if you're using UEFI 2.0 or above, and only if it's a 64-bit UEFI.
Linux usually does not directly boot from either EFI or from BIOS; instead, a second-stage bootloader (like GRUB) is booted directly, and then Linux is loaded from there. GRUB supports booting from either 32-bit EFI or 64-bit EFI, but the specific version of GRUB you boot from must be compiled to match the version of EFI: a 32-bit version of GRUB for a 32-bit EFI, and a 64-bit version of GRUB for 64-bit EFI. If you then boot into a 64-bit Linux, then that operating system will not be able to interface with any of the runtime services (http://wiki.phoenix.com/wiki/index.php/EFI_RUNTIME_SERVICES) provided by a 32-bit EFI. (There is work on bypassing the second-stage bootloader to boot directly from EFI to Linux, but it is probably best identified as "experimental" at present.)
Oh, good. So if there's nothing that users of older systems need, there's no harm in the fact that they can't upgrade. I'm glad you established right from the start that you're whining about something that isn't a big deal.
Of course there's a reason. It costs money, diverts resources from other projects, and adds complexity. Supporting 2 kernels is time consuming, expensive, and error prone.
I don't doubt that Apple considered that and weighed the advantages against the disadvantages - and concluded that continuing to upgrade the older hardware isn't worth the effort. Part of that is undoubtedly the fact that people with older hardware tend not to be as quick to upgrade as people with newer hardware. If they haven't upgraded to Lion, why would you expect them to upgrade to ML?
Yes, you can look at it that way. The other way to look at it is that part of the reason OS X is a better choice than Windows is that they don't make an effort to support every POS hardware that has ever been created. At some point, the benefits are too small to outweigh the disadvantages. Supporting older Macs costs money that could better be spent on developing new stuff. It creates problems that affect everyone - not just those who use the older kernel. It adds complexity which slows everything down.
Besides, it's pretty much a moot point. Systems that don't have a 64 bit EFI (like my 2006 MBP) didn't run Lion, either. So if you managed without upgrading to Lion, inability to upgrade to SL probably isn't a big deal - at least for people who don't make a career out of whining about Apple's every move.
Oh, and if you want to talk about costs, let's talk about the people who actually DO upgrade. OSX - $19.99 which you can install on every Mac you own (for personal use). Windows - could be up to 10 times that amount or more, depending on which version - and that's PER computer. So instead of whining about the potential cost for someone who probably wasn't going to upgrade, anyway, why not talk about the costs for the people who actually will do so?
Which eliminates PPC Macs - but they were eliminated a long time ago. If your system can't run SL, then it's hopelessly ancient and you probably weren't going to upgrade, anyway. How many people with systems too old to run SL would even be considering ML?
I've seen quite a few people saying how well it runs on their old machines, actually. People've been running it on P4s and it's pretty speedy.
Of course Apple's so strapped for cash they can't hire a couple of devs to fix/compile/test the 64 bit kernel on 32-bit EFI machines. The kernel doesnt really change much between releases anyway, so there wouldn't be that much to test. It's mainly the frameworks above the kernel that are modified.
Why was Apple advertising the Mac Pros in 2006 as full 64-bit machines when they weren't? I smell a class action lawsuit ahead. As others have said, if a couple of script kiddies can get ML working without source code on a 1,1/1,2 Mac Pro, why can't Apple do it officially? I am aware of how the BIOS emulation works, but I'm sure Apple could get the 64 bit kernel loaded from a 32 bit EFI if they put their minds to it. They've done some pretty impressive feats in the past, on much less capable hw/sw.
Apple needs to be careful, people pay the "Apple tax" because they expect their machine to be reliable and have a long life; if after a couple of years they starts ditching customers that've spent thousands on a Mac, it's not going to go down too well. It does seem the Mac is getting more and more neglected (400 days without an iMac update?) in favour of iPad and iPhone. Apple's Mac market is small, they can't go about slapping loyal customers in the face lest they lose what share they have. Windows is really starting to look mighty good to many a Mac owner.
You obviously care enough about it to "whine" in the other direction. What about devs who want to write iOS apps? If Apple's previous actions are anything to go by, the version of Xcode released after ML won't support Lion, so devs're going to need a new Mac to submit apps to Apple. Another artificial limitation to try to force people to fork out more for new hardware.
That's silly. They're supporting machines 4 years old and newer.
Since very few people upgrade older computers, anyway, it's really a non-issue.
I'm not whining about anything - but rather pointing out the flaws in your logic.
As a developer, the cost is minimal. A Mac Mini is $599 and you can sell the old one for $400. So a couple hundred dollars every couple of years. And that even assumes that your negative assumptions are true.
In return for minor inconvenience (inability to upgrade hardware that I never intended to upgrade, anyway and a slight cost for developers), we get the best, most stable, most efficient, most usable consumer OS on the planet. Most Mac users are happy with that trade-off.
I think you'll find many people with a $5000 Mac Pro 1,1 are on Lion. Even the oldest Mac Pros are fast, faster than some of Apple's latest machines. My Mac Pro 1,1 runs Rage at 40fps no problem, but it needs Lion. What happens when apps are updated to require ML, and autoupdate and break like Apple's botched iPhoto update few weeks back? As I said before and you ignored, why could they support machines for 7 years in the classic era, but not now on a modern OS?
Update. I suggested turning off auto graphic switching ... Waiting to hear if that helped.
Quote:
Originally Posted by jragosta
If they haven't upgraded to Lion, why would you expect them to upgrade to ML?
Personally, I've held on to Snow Leopard on my 64-bit Intel Mac because I have been reluctant to jump on the bandwagon with newer technology - I've been content to stick with well-supported proven technology. As soon as ML comes out, Snow Leopard will lose all security support, so I plan to upgrade my 64-bit Intel Mac to Lion very soon just so that I can maintain current technical support.
As for my 32-bit Intel Macs... Well, once ML comes out I suppose I will be left with the choice of either relegating them to the trash heap, or else installing an alternate OS which still receives security support such as Windows (I still have a license for XP lying around, and it has more than a year of security support left) or Linux.