- Joined
- May 18, 2012
- Messages
- 48 (0.01/day)
Processor | i5-4690K @ 3.7ghz |
---|---|
Motherboard | Asus Z97-A |
Cooling | Corsair H100 |
Memory | 16GB G.Skill DDR3 12800 |
Video Card(s) | MSI GTX 660 TI 2GB PE/OC |
Storage | 125gb SSD, 256gb SSD, 500gb HDD, 1tb HDD, 2tb HDD |
Display(s) | Acer G235HAbd 23" |
Case | Corsair C70 Vengeance |
Audio Device(s) | SteelSeries Arctis 1 Wireless |
Power Supply | Antec Earthwatts 650w |
Mouse | SteelSeries Rival 3 |
Keyboard | MS Sidewinder X4 |
Software | Windows 10x64 Pro |
Okay, so ive got a 25gb WD Blue HDD, with win7x64 on it as an 80gb NTFS (C:\) partition. the rest of the drive is programs (D:\), everything that i could keep from being installed to C:\program files basically.
like so.
once the rest of my new hardware arrives, i want to copy that 80gb os partition to one of these fellas:
,crucial MX100 256gb SSD.
then, (once everything is running and stable) expand the data partition back to fill the entire drive, so that C:\ is the 256gb ssd, and D:\ is the 250gb hdd.
does that make sense?
Im familiar with using gparted to fiddle with partitions, but i want to be sure that windows isnt going to flip a table when it suddenly finds itself on a new drive, attached to a new motherboard and new CPU.
ive tried this trick once before, some years back, with winxp (moving the os to a new mobo/cpu setup, which didnt work at all, the disk was eventually formatted and win7 installed on it.
is win7 any better about being relocated like that? do i need to "seed" my win7 install with drivers for the new motherboard's chipset and widgets before i do the teardown? any mandatory prep-work to make this happen smoothly? (backing up files is a given, of course). recommendations for imaging software? i think i was looking at clonezilla last time.
if i have to re-activate windows, no big deal (totes legit OEM copy), but id rather not have to reinstall if i can reasonably avoid it.

like so.
once the rest of my new hardware arrives, i want to copy that 80gb os partition to one of these fellas:
then, (once everything is running and stable) expand the data partition back to fill the entire drive, so that C:\ is the 256gb ssd, and D:\ is the 250gb hdd.
does that make sense?
Im familiar with using gparted to fiddle with partitions, but i want to be sure that windows isnt going to flip a table when it suddenly finds itself on a new drive, attached to a new motherboard and new CPU.
ive tried this trick once before, some years back, with winxp (moving the os to a new mobo/cpu setup, which didnt work at all, the disk was eventually formatted and win7 installed on it.
is win7 any better about being relocated like that? do i need to "seed" my win7 install with drivers for the new motherboard's chipset and widgets before i do the teardown? any mandatory prep-work to make this happen smoothly? (backing up files is a given, of course). recommendations for imaging software? i think i was looking at clonezilla last time.
if i have to re-activate windows, no big deal (totes legit OEM copy), but id rather not have to reinstall if i can reasonably avoid it.