Ok Bootcamp without APFS drivers was a dealbreaker for me until now. Now I have Mojave and HS on separate disks and I can successfully go back and forth from EFI Windows to Mojave or HS through blessing. So 6.1 drivers fixed the issue.
Can you provide any examples? I'm not even sure what you mean.HaHA! Microsoft has done a rather good job of Windows obsolescence without any intentional planning.
Lots of GPUs don’t work anymore with Windows 10. Most ATI before TERASCALE don’t work anymore, not even with old drivers. All AMD processors without SSE3 got the axe too.Can you provide any examples? I'm not even sure what you mean.
Other than obvious things like a system that was nicely configured for Windows XP struggles with Windows 7 and Windows 10. The same hardware, however, with more RAM, VRAM and disk space can run Win10 just fine. Not "planned obsolescence", but simply the fact that minimum hardware requirements increase over time. (The Mac Pro initially came out with 1 GiB of RAM. Would that be feasible with High Sierra?)
Can you provide any examples? I'm not even sure what you mean.
Other than obvious things like a system that was nicely configured for Windows XP struggles with Windows 7 and Windows 10. The same hardware, however, with more RAM, VRAM and disk space can run Win10 just fine. Not "planned obsolescence", but simply the fact that minimum hardware requirements increase over time. (The Mac Pro initially came out with 1 GiB of RAM. Would that be feasible with High Sierra?)
Lots of GPUs don’t work anymore with Windows 10. Most ATI before TERASCALE don’t work anymore, not even with old drivers. All AMD processors without SSE3 got the axe too.
Since Windows only provides basic, generic video drivers - why is this MS's fault and not ATI/Nvidia?Lots of GPUs don’t work anymore with Windows 10. Most ATI before TERASCALE don’t work anymore, not even with old drivers. All AMD processors without SSE3 got the axe too.
...But the biggest thing is that Microsoft's "obsolescence" benefits Intel and AMD by selling new hardware - it doesn't benefit Microsoft. Apple's planned obsolescence directly benefits Apple, since Apple OSX is only supported on Apple systems.
This is one of the most naïve statements that I've ever seen here.How many x58 motherboard manufacturers are updating the bios of their motherboards today? I think Apple is the only one.
This is one of the most naïve statements that I've ever seen here.
The other X58 mobos aren't being updated because Windows and Linux releases aren't being made incompatible with the legacy BIOS. Apple is releasing OS versions that are incompatible - so Apple needs to either update the BIOS or drop support for the systems (or get Phil and his ass to release a new Mac Pro).
Since the MP7,1 is terribly late, it would be embarrassing to drop support for the MP5,1 - so Apple does a BIOS update.
This is one of the most naïve statements that I've ever seen here.
The other X58 mobos aren't being updated because Windows and Linux releases aren't being made incompatible with the legacy BIOS. Apple is releasing OS versions that are incompatible - so Apple needs to either update the BIOS or drop support for the systems (or get Phil and his ass to release a new Mac Pro).
Since the MP7,1 is terribly late, it would be embarrassing to drop support for the MP5,1 - so Apple does a BIOS update.
Name calling is never appropriate @AidenShaw. Read the forum rules.
If you are tied to a Microsoft operating system, you have an option not to upgrade to the latest version of MacOS. Granted, ongoing compatibility would be a nice to have. While it’s not the greatest option, it’s not like Apple stopped providing security updates to High Sierra and legacy firmware revisions.
On the other hand, as a MacOS, iOS and React.JS developer, I’m happy as hell to have continued support for a 9 year old Mac.
I don't really think calling a person's statement naive is considered name-calling
You went directly from BootCamp 5 drivers to BC6.1 without uninstalling BC5? Cool. Didn't work for me. I tried it a couple of times. I had to uninstall BC5 first to get the Boot Manager to appear in the task bar or run from the Program directory.I didn't have to do that. It just worked. Then on next reboot, it reinstalled the proper BT/MM driver. Just go to your device manager and let it find the proper driver. That SHOULD work. It did for me...So bottom line, I guess you have to uninstall version 5 BootCamp Services before installing version 6, even though there was no message that was necessary as there was when people went from v6 to v6.1.
You went directly from BootCamp 5 drivers to BC6.1 without uninstalling BC5?
Disagree.
Calling the statement naïve, is tantamount to calling the writer naïve. He could have said he disagreed without a personalized attack to the author.
That said, regardless of the reason, the cMP is getting a lot support from Apple and negative attention from the PC crew. I for one appreciate the continued support.