Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
 
HaHA! Microsoft has done a rather good job of Windows obsolescence without any intentional planning.
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.
 
  • Like
Reactions: crjackson2134
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?)

Planned obsolence is a jab at MS's repeated failed attempts to innovate, that at every step, negatively affects windows market share. Whether it was the most recent win10 upgrade that needlessly deleted any local content not stored in one drive, countless users lost years of data for no good reason, the indecision of windows 8, or how about being vista-ed in the past. Where are the full touch friendly versions of office? Historically, Tablet PC's have been around since.. windows tablet 98. that's 20 years. Supporting their own initiatives more than they historically have? There is an attempt to innovate at ms. but come on, it's ms. you can only expect so much.
 
  • Like
Reactions: crjackson2134
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.

Microsoft like any company are have good and bad parts. Being a log time apple fan boy I've given up the hate for Microsoft long ago. One thing they are good at is legacy support. If fact it's their obsession with legacy support that has held them back. I've only started using windows as an experiment because of Apple's lack of mac pro support. I installed windows in my older mac hardware just to see if I like it. I have a mac mini 2007 and a macbook 2009 running windows 10. It seems Microsoft support old mac hardware better then apple. I find this ironic. While I don't like windows 10 as much as macos, I think it's safe to say Microsoft support of older hardware is much better then apple.
 
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?

SSE3 was introduced 14 years ago - and AMD bungled their version of it.

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.

You're comparing Apples and Orangutans .
 
...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.

Apple benefits greatly planned obsolescence. MS care if you want to pay $100 for windows. They don't care if you install it on 10+ year old computers like I did.
 
The Mac Pro 4,1 / 5,1 was initially introduced in 2009, over 8 years ago. Based on the number of firmware updates we have blessed with on the MacPro... I fail to see any level of planned obsolescence with the MacPro.

Honestly, I’ve experienced a level of hardware platform support that exceeds ANY PC macufacturer to date. Period.

How many x58 motherboard manufacturers are updating the bios of their motherboards today? I think Apple is the only one.

Is this planned? Most of apples obsolesence is a result of hardware design. Where they can push the envelope.. they deliver.

I’ve been using windows since 1.0 shipped. Today I trust my televisions to the OS, that’s about it.
 
  • Like
Reactions: crjackson2134
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.

Read what you wrote. So no Spectre/Meltdown microcodes needed?

All motherboard manufacturers obsoleted X58 mobos years ago and no one is updating microcodes. Not even Intel is updating his own motherboards earlier than DH67.
 
  • Like
Reactions: crjackson2134
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.
 
  • Like
Reactions: crjackson2134
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, unless you were referring to something else he said.

Also, while it's nice to have continued support for a 9-year old Mac, that was never Apple's intention. The 2009 was dropped two years ago, remember? Without the hack that flashes it to 5,1 firmware you'd be officially limited to El Capitan, which I think is no longer receiving security updates now that Mojave is released (don't they only release updates for their last three OSes?), and is therefore unsafe to be running on any machine connected to the internet.

I don't have a dog in this fight, but let's be honest here. Apple officially left 2009 cMP owners high and dry three years ago.
 
All OEM's do planned obsolescence one way or the other. I work for a big OEM distributor and what the OEM does is raise the price on a planned product for obsolescence above the new product's price just because the demand for the old product is still high. No matter what you do as an end user you can't win this game.
 
I don't really think calling a person's statement naive is considered name-calling

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.
 
  • Like
Reactions: handheldgames
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.
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...
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.

My lost Magic Mouse connection came alive after the 3rd reboot into Win 10 without doing anything else. There was never an indication of a driver problem in Device Manager, other than the mouse was missing there, but for some reason it took 3 reboots to reappear. As far as I can tell everything is working fine now.

I'm glad to have the Win 10 Bootcamp Manager functional again when I know I want to stay in Windows for reboots. But I still like using a script to boot from MacOS to Win10 so I don't have to type a password when using the Startup Disk preference pane.

Thanks MisterAndrew for letting us (me) know that BC6.1 brought this functionality back to the Mac Pro.

(Also I'm on BootROM 138- so upgrading to 140- wasn't necessary to make this work on the Mac Pro. No one said it was, but I wanted to confirm that for anyone, like me, that might wonder.)
 
  • Like
Reactions: crjackson2134
You went directly from BootCamp 5 drivers to BC6.1 without uninstalling BC5?

Exactly... I’ve done it a couple of times now, the syntax on how you run the CLI options matter AFAIK. I used the -h option (help, it lists all available options) and modified my execution for the driver download/install. Try it out and find what works best for you.

Anyway, I’m greatful for the ability to use the BC Control Panel again.
 
  • Like
Reactions: handheldgames
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.

I guess the mods can decide if that's considered a personal attack in terms of the rules here. But IMHO that's really a stretch. If I say someone is making a specious argument does that mean I'm calling them a specious person? :rolleyes:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.