SATA mode versus Legacy Mode

_Niroth_

Distinguished
Aug 1, 2006
18
0
18,510
Hey All-

I have a new SATA drive that I want to install Windows XP fresh on but I don't have a floppy drive that works anymore and don't feel like going through the slipstream hassle. I was wondering what (if any) performance hit I would be taking by setting the drive to Legacy IDE mode in BIOS and just install it with windows thinking it is IDE?

Thanks
 
Wait.. I'm a noob here.. Why do you need a floppy drive? I installed XP on my SATA drive clean a couple years ago w/o a floppy drive.. I had XP install CDs. Slipstream refers to network deployment right? Thx
 
No, slipstream refers to the process of integrating service packs and hotfixes on to the XP cd. Once they are slipstreamed, the user no longer has to install them seperately, because they have already been applied. With SP2 slipstreamed, you shouldn't require a floppy to load the proper drivers (or a SATA to IDE adapter), they should already be on the disk.
 
Nope I get it through the school or whatnot. But, in any event, if the SP2 Disk will have SATA drivers on it then I guess that is all I need to do . Thanks a lot.
 
Nope I get it through the school or whatnot. But, in any event, if the SP2 Disk will have SATA drivers on it then I guess that is all I need to do . Thanks a lot.

Depends on what kind of SATA controller you have as to whether the Windows XP (with or without SP2) will have drivers for it or not.

If your SATA controller is in legacy mode, Windows will use generic IDE drivers for setup. Once Windows is running, if you install chipset drivers for your motherboard, you'll get a manufacturer-optimized IDE driver, but it will still communicate with the SATA controller via the legacy IDE/ATA protocols.

If you put the SATA controller in native mode/AHCI mode, Windows will usually report that it can't find a storage controller on your computer. In this case, you need a floppy drive and a floppy with the native SATA drivers on it, and you'll press F6 during the Windows setup to have it load the drivers from the floppy. This is the same way you set up a machine that has a SCSI controller or RAID controller as the boot device.

If you use legacy mode, you give up two things that the native SATA driver can do: Native Command Queueing (NCQ), and Hot-Swap capabilities.

There have been other discussions on the forum about NCQ, and tests on current SATA drives that support NCQ seem to indicate that NCQ can actually slightly slow performance when used on a single-user workstation, although it can speed up performance when used on a server. I personally feel this is the result of immature development of NCQ capabilities in current SATA drives and controllers, and I feel that those results will reverse themselves in future SATA implementations, but that's only my speculation.

Hot-Swap can be useful in very specific circumstances. At work here we have some video editing workstations that use a removeable caddy hard drive system, where each video project is stored on it's own removeable caddy. Moving to native SATA drivers in these systems enabled us to hot-swap the caddies, rather than previously where we would have to shut the systems down to swap.

I personally would recommend the native SATA/AHCI mode and it's associated drivers, even though it's more of a pain to set up. The controller manufacturers will be concentrating their performance efforts there, and future drives, controllers, and drivers that improve performance will be built around native mode, not legacy mode.
 
If you use legacy mode, you give up two things that the native SATA driver can do: Native Command Queueing (NCQ), and Hot-Swap capabilities.
true, but in both cases the disk AND the controller must support ncq and hot swap. if one of them does not support, then he can use in legacy mode with no loss of performance at all.
 

TRENDING THREADS