Slashdot Mirror
Boot Camp Might Damage Speakers on 2016 MacBook Pro (digitaltrends.com)
An anonymous reader writes:One of the things an Apple Mac can do that Windows 10 machines can't do -- at least easily and completely legally -- is run both Windows and MacOS. Interestingly, it's Apple's Boot Camp utility that makes this feat possible, which essentially enables Macs of all flavors to boot directly to Windows 10 and use the Mac as if it were a Windows machine. Usually, this is a fairly straightforward process that works well, with the resulting Boot Camp configuration doing fairly well at mimicking a Windows 10 machine with a few hardware limitations. As of the 2016 MacBook Pro machines, however, it appears that Boot Camp might be causing some serious and uncharacteristic audio issues. It appears that the new speakers running on the refreshed MacBook Pro line aren't working so well with the obsolete drivers provided in the current version of MacOS Sierra Boot Camp. Users are reporting the issue on all models of the 2016 MacBook Pro, and they are not experiencing the issue in MacOS. Virtual machines using Parallels or other software are also not experiencing the issue, providing more support of a bad audio driver causing the problem in Boot Camp.
Really feeling that Apple quality right now.
I'm sure steve jobs would be fine with this.
I'll take "Stuff that shouldn't even be possible" for $1000 Alex.
Speakers joining RAM, SSD, and batteries on Apple's growing list of components that can never be swapped out?
One of the things an Apple Mac can do that Windows 10 machines can't do -- at least easily and completely legally -- is run both Windows and MacOS.
1) So Apple Macs are Windows 10 machines.
2) "Legally" is not really a very interesting distinction.
3) Except that clearly it can't run Windows nearly as well as every other PC compatible.
'It just works.'
I don't hear that as much as I used to. Why is that?
Except I'm coming from Mac.
If the anonymous reader or the msmash had done more than copy-pasting the first three paragraphs of the article, adding a link -- if they'd even read what they copy-pasted -- they might have realized this. If they lived in this fairy-tale land where editors edited, they might have gone so far as to summarize the bit about "pops" which appear to damage the speakers over time.
It's bootcamp that allows Macs to run Windows and not the fact that Macs and PCs use virtually identical hardware? Who knew.
It's neither a "feat" that an Intel notebook can run Windows, nor is it interesting. What's with all the Apple cocksucking, submitter?
Is this the guilty command in the boot loader?
POKE 59458,62
bold.
You're not listening to it right.
Price, Quality, Time. Pick none. What, you thought you had a choice?
So the way I understand this is that the potentially damaging issues happens within BootCamp itself which Apple makes and provides the audio driver and this is before you boot into Windows and therefore Linux also? I am going to sum up the paragraph I could otherwise write: how do you fuck that up?
Brought to you by Carl's Junior.
Did you just spend half a summary defining "boot loader" on slashdot? Editor please.
When did Slashdot start accepting submissions from people who don't know the difference between a bootloader and a driver?
XML is a known as a key material required to create SMD: Software of Mass Destruction
Obviously Apple has put a limited effort into bootcamp. I'm running Windows 7 (natively booted) on late 2013 model. Gripes:
- I've remapped some keys using Windows built-in functionality, and the reaction time on these remapped keys is slower. It misses normal duration keystrokes, so I have to be extra slow for these keypresses to register.
- After waking up from sleep it clings onto the last active wifi network for tens of seconds, sometimes minutes, before realising the machine has just woken up in a different location and it's time to connect to another wifi. (Manually disconnecting from network helps but why the hell won't it do this pronto authomatically like my last Asus?)
- After connecting to different wifi networks a few times, it stops recognising any and requires a reboot.
- After disabling the wifi device (e.g., in an airplane), 30% chance it won't reenable and will require a reboot.
- I could never get Windows to recognise the built-in SD reader.
- It does not remember the keyboard backlight setting on reboot. Resets it to default.
17779 eligible voters in a district, 17779 'vote' as one. This is Russia.
So, contrary to your statement, yes, Apple managed to hit the bar set by their competitors.
At the prices Apple charge for their laptops I expect them to far exceed the bar set by their far cheaper competitors. If they only meet it then there is nothing to justify the far higher prices...which is a big part of the problem with the new MBPs: they are average laptops with an insanely high price.
how do you fuck that up?
Well I suppose one way would be to spend all your engineering time shaving 2mm off the thickness, designing keys which hardly move, removing other keys and replacing then with a piece of the screen and finally attempting to remove all the ports. After that you probably don't have much time to spend on less important stuff like making sure you can't overdrive your speakers.
To get more power from compact speakers, I believe Apple has an algorithm that detects and removes clipping before it can saturate/damage the speaker. Perhaps this isn't available in the windows side. This might be a consequence of hardware-sw algorithm co-design.
They'll blame the user for it and make you pay for it.
BeauHD. Worst editor since kdawson.
Give it a couple of years of Apple pretending the issue doesn't exist, a class action lawsuit, eventually they'll be forced to acknowledge it and refund repair costs. But none of it is without a fight and without paying for the repair in the short term.
Seen it over and over and over again now. Thanks but no thanks.
With virtual machines, why not run Windows in a VM. The last time I dual-booted was way back with Windows 2000 and 98 or some shit.
Clever click-bait advertising:
One of the things an Apple Mac can do that Windows 10 machines can't do -- at least easily and completely legally -- is run both Windows and MacOS. Interestingly, it's Apple's Boot Camp utility that makes this feat possible, which essentially enables Macs of all flavors to boot directly to Windows 10 and use the Mac as if it were a Windows machine. Usually, this is a fairly straightforward process that works well, with the resulting Boot Camp configuration doing fairly well at mimicking a Windows 10 machine with a few hardware limitations. As of the 2016 MacBook Pro machines,
And the Bait after the Advert
it appears that Boot Camp might be causing some serious and uncharacteristic audio issues. It appears that the new speakers running on the refreshed MacBook Pro line aren't working so well with the obsolete drivers provided in the current version of MacOS Sierra Boot Camp. Users are reporting the issue on all models of the 2016 MacBook Pro, and they are not experiencing the issue in MacOS. Virtual machines using Parallels or other software are also not experiencing the issue, providing more support of a bad audio driver causing the problem in Boot Camp.
I understand /. needs to 'keep the lights on' but can it be done without completely selling out?
~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
Thank you for not starting your paragraph off by saying "apple mac can do that a PC can't". Because a mac IS a ****ing PC. Thank you so much.
Must be those drill sergeants at Mac Boot Camp yelling up close and personal at the equipment. You'd get damaged also.
Tracy Johnson
Old fashioned text games hosted below:
http://empire.openmpe.com/
BT
until Windows won't run.
Sounds vaguely familiar.