- Nov 2, 2011
- 8
- 0
- 66
I have a MacBook Pro (early 2011), which I almost exclusively use as a Windows machine. Seeing how SSDs are reaching sort of affordable prices, I have been considering getting one, but I have put the idea on hold after learning that I wouldn't be able to use TRIM under Bootcamp and would get nowhere close to 6Gbps link rate.
Why is Apple forcing the SATA controller into legacy IDE mode when using BIOS emulation with Bootcamp? While doing so sort of made sense at first, as Windows XP couldn't support AHCI natively and wouldn't work without a driver, Bootcamp has dropped XP support quite a while ago. There are at least two or three generations of Macs that have never supported XP but are still crippled this way.
Is there any valid technical reason for disabling AHCI under Bootcamp or is Apple yet again nudging users towards its own closed sandbox?
P.S. I know you can hack the bootloader to sort of fix this, but doing so has its own drawbacks and I'm more interested in learning the rationale behind the decision.
Why is Apple forcing the SATA controller into legacy IDE mode when using BIOS emulation with Bootcamp? While doing so sort of made sense at first, as Windows XP couldn't support AHCI natively and wouldn't work without a driver, Bootcamp has dropped XP support quite a while ago. There are at least two or three generations of Macs that have never supported XP but are still crippled this way.
Is there any valid technical reason for disabling AHCI under Bootcamp or is Apple yet again nudging users towards its own closed sandbox?
P.S. I know you can hack the bootloader to sort of fix this, but doing so has its own drawbacks and I'm more interested in learning the rationale behind the decision.