• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why didn't MS add native AHCI support to XP starting with SP3?

VirtualLarry

VirtualLarry

No Lifer
I mean, after all, they added 48-bit LBA support with SP1, so they do add new disk technologies in SPs. Why didn't they continue to do so with SP3?

If they ever release a SP4 edition of XP (unlikely), then I hope they add AHCI support. There are some laptops that lack an IDE mode switch in the BIOS for the disk controller chipset, that I would like to put XP on without going though crazy hoops.
 
XP SP4 would not have AHCI support. Mainstream ("we add stuff") support for XP is over as of last year.

As for why they didn't add it, my best guess is that it's not a small change. Even though MS adds things during the Mainstream support phase, such additions tend to be small things to solve immediate problems. AHCI support isn't an immediate problem.
 
Did Microsoft EVER add any disk controller drivers with any XP Service Pack? I never noticed any additions when watching the initial XP Install routines (where it lists the drivers being transferred to the hard drive).
 
Last edited:
Well, Microsoft forced us to install controller drivers using a floppy disc. Now, I don't know about you, but I stopped using a floppy before 2000 rolled around. It still irks me I had to go out and buy a floppy drive and cable just to do Windows installs.
 
RebateMonger said:
Did Microsoft EVER add any disk controller drivers with any XP Service Pack? I never noticed any additions when watching the initial XP Install routines (where it lists the drivers being transferred to the hard drive).
Click to expand...

XP RTM won't detect many of the sata controllers in use today. It wasn't a driver issue, it was a kernel issue. Kernel revisions through service packs remedied alot of that. Basic controller drivers are included with the install and cover a wide range of controllers, but the full features ones usually come packaged in the chipset drivers for your specific motherboard.
 
I like threads it sound like this.

"Stupid" human being. They had to built the Pyramids by hand. What the matter "Stupid" Caterpillar could bulilt for them Bulldozers and Cranes .

.
 
Microsoft doesn't make these decisions in a vacuum. IHVs and device chip vendors have a say over what vendor/hardware specific drivers get into Windows.

e.g. I'm pretty sure Microsoft's decision to neuter 36-bit PAE support on 32-bit client SKUs was because it gave hardware vendors a choice: spend the money and resources to regression test all your current in-box drivers for compatibility (including those for end-of-life or legacy hardware) with 36-bit PAE and fix the bugs, or don't and we'll just pull support for 36-bit PAE.

Perhaps there was a similar choice given to hardware vendors WRT in-box AHCI support.
 
Last edited:
tcsenter said:
Perhaps there was a similar choice given to hardware vendors WRT in-box AHCI support.
Click to expand...
But AHCI is a standard, like IDE and EHCI (USB2.0). The one MS AHCI driver should work with any SATA chipset that is truely AHCI (some NV and early chipsets claim to be AHCI, but really aren't).
 
WhoBeDaPlaya said:
That's kinda ignorant. There's still some stuff that will only run properly on XP.
<-- Not a hater. Running Win7 x64 ultimate on main rig, XP for other systems.
Click to expand...

And that only way that will change is if people start moving on. If people hadn't been so stupid with regards to Vista that wouldn't be an issue now.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top