Please forgive me if you already know this, but Windows XP on SSD is not an easy thing to do correctly since the OS was never designed with SSD in mind. Some issues to consider:
- AHCI mode versus IDE/legacy mode for SATA controller. AHCI will give you support for NCQ and hotswap, but you won't be able to install Windows XP with AHCI drivers for your mobo SATA controller since the WinXP setup files lack a generic AHCI driver. There are, however, 2 possible workarounds for this issue (if you want AHCI), which are:
(1) you perform an F6 installation to first set up your disk controller with the appropriate AHCI driver prior to running Windows XP setup, or
(2) you re-create your Windows XP setup CD to include the AHCI driver for your mobo via slipstreaming.
- Proper sector alignment for 4K (a.k.a. Advanced Format) -- and special note... once your XP installation is properly aligned on the SSD, make sure that, if you do backups, your backup tool (i.e. Norton Ghost or Acronis) will respect the 4K Advanced Partition alignment when doing a restore from a backup of your properly aligned partition.
- No TRIM support on XP (but most SSDs today have garbage collection feature natively built in, so TRIM not necessarily needed).
- Some HDD maintenance features/tools should not be used on SSD, i.e. Windows Disk Defragmenter.
In short, getting Windows XP onto SSD is do-able, but it is (at best), a kluge. Just this week, I replaced my last desktop which ran XP Pro SP3 x86 on a 64GB Crucial M4 SSD (in AHCI mode on SATA3 controller) with a newly built system running Windows 7 Professional SP1 x64 on a 128GB Samsung 830 SSD. The user experience is much better on the Windows 7 system which supports SSD natively, versus XP on SSD which had to be kluged to get it working. (And by "better", I mean much faster system performance).
But if you want to stick with XP, it does run faster on SSD than on HDD obviously