Cloning WinXP Pro 32-bit SP3 partition from HDD to SSD

[PartingShot]

Recently got my hands on an Intel 80GB SATA300 SSD and want to try to migrate my existing desktop system from HDD to SSD. But the OS is WinXP Pro 32-bit SP3, so it's not exactly ready for SSD without some configuration and tweaks.

Looking for guidance from anyone who has done this. Here's what I've been considering after lots of google-researching.

- Proper sector alignment for SSD: do-able with 3rd party partitioning/cloning tools
- Garbage Collection: manually do-able in XP using Intel's SSD Toolbox application.
- Defrag: disable
- Page file: disable, or move to RAM drive
- Internet cache and temp files: move to RAM drive
- Disk indexing: disable

Does this sound about right, for starters at least? Please give any corrections and/or additional pointers. Thanks a bunch everybody

[fritzi93]

To elaborate:

1) You can use a free version of Acronis to clone to the SSD, if you have either a WD or Seagate drive, available at their websites. Macrium free can do it if you have, say, a Hitachi.

2) After cloning and bootup to the SSD, check alignment with AS_SSD (google for it). I would guess your chances of being out of alignment are 50/50 or perhaps more, to go by personal experience.

3) Fix alignment with a Parted_Magic live CD. Boot it up, start Partition Editor, shift alignment a block to the right, okay, close window, then apply changes (on the toolbar).

You should be okay with the rest of it. You did some homework.

[EDIT] Windows might not boot up and you may need an XP install disc to repair the boot manager after re-aligning the partition. Or do it from recovery console (do a search on it).

[jman98]

- Page file: disable, or move to RAM drive
- Internet cache and temp files: move to RAM drive

I wouldn't use a precious RAM drive for either of these tasks.

[PartingShot]

Thanks for the responses. I did perform the OS transfer from HDD -> SSD this weekend. The story has a bittersweet ending.

BTW, a very special thanks to fritzi93 for his response, which got me through the alignment problem, which I did have after the cloning process.

Fix alignment with a Parted_Magic live CD. Boot it up, start Partition Editor, shift alignment a block to the right, okay, close window, then apply changes (on the toolbar).

Parted_Magic Live was awesome, thanks for that tip.

Anyway, the system came up fine after cloning/re-aligning, and it was significantly faster than before. Unfortunately, though, the Intel SSD Toolbox software could not communicate with the Intel 320 80GB SSD because the SATA controller in my PC (part of an AMD chipset, you can see my current system specs under my VH profile) is not compatible with the Intel SSD Toolbox. Apparently, Intel would rather you use the SSD Toolbox on Intel-based systems. So two critical features of the Toolbox are lost to me because of having an AMD system: Secure Erase and SSD Optimization (garbage collection). Those options are greyed out in the Toolbox GUI.

So I decided to revert back to the HDD, and save the SSD for a future build with Intel-based hardware. Thanks again for the feedback, fritzi93

[fritzi93]

I may be wrong, but I should think you'd still be okay to use the Intel SSD in your system.

It's my understanding that the firmware of an SSD is the most important thing. If it's working as intended, no real worries, even if you're using XP and can't enable TRIM. Garbage collection will be carried out regardless (although the SSD will not work as efficiently in IDE mode, nor will GC). But it will still work, and work much better than a mechanical hard drive.

Does your Intel SSD use an Indilinx controller? (At one time I know they did, maybe still do). If so, you could use wiper.exe, used by several makers of Indilinx-based SSDs (some models of Patriot, G-Skill, Crucial, Intel...). That would give you manual garbage collection. I can use that on my OCZ Indilinx Vertex, or use what OCZ calls gc.exe, essentially the same thing, dunno what the difference is, maybe none.

Tell you what, I can use gc.exe daily or monthly, doesn't make any difference in how the drive benches, although I do that sparingly. So I'm not sure if that concern is not overstated in the threads about the subject you can find on the web. Nearly all of which are written by *performance* enthusiasts, take note.

Then there's the OCZ Agility3 (Sandforce controller) I got on special at Newegg for my older HTPC (now transferred to office duty). Turned out I couldn't enable AHCI on that board, nor will the damn OCZ toolbox work. The drive seems to be fine though regardless, and benches consistently the same. Again, apparently the firmware is carrying out GC all by itself.

If I'm wrong, someone please correct me. I look forward to any further replies.

[jagabo]

- Page file: disable, or move to RAM drive
- Internet cache and temp files: move to RAM drive

I wouldn't use a precious RAM drive for either of these tasks.

If you have more than 4 GB of RAM use a ram drive that can use the memory 32 bit XP can't access.

[PartingShot]

Does your Intel SSD use an Indilinx controller? (At one time I know they did, maybe still do). If so, you could use wiper.exe, used by several makers of Indilinx-based SSDs...

Looks like in the case of the 320 series SSDs, Intel has its own controller.
*Source (AnandTech)*

So to sum up, Intel 320 SSD with Intel SSD controller + Intel SSD Toolbox + AMD SATA mobo controller = FAIL... at least with respect to having the full functionality of the Toolbox. The SSD drive itself performs very well in the system. I just want to be able to secure erase, then restore my system partition (from backup image) from time to time, in order to avoid the performance degradation that happens over time.

Can anyone here recommend a good tool for secure erasing the Intel 320 SSDs, since I can't use the Intel SSD Toolbox with my AMD motherboard? Thanks.