New
#1
Installing boot SSD: AppData? Win7 libraries vs. special folders?
Hello everyone,
I'm planning how to make use of my spiffy new 80GB SSD. My current system came preinstalled with a 1TB drive containing a single C partition storing everything (plus a couple of hidden partitions for Dell Restore etc.), which died and was replaced with a 2TB drive, and the former drive image restored to the new HDD. (This leaves me with 1TB currently unallocated.) My plan is to:
- Create a D partition from the free 1TB
- Move my data to D (e.g. from C:\Users\Charles\My Videos to D:\Charles\My Real Videos)
- Add each new D folder to the appropriate library (e.g. Add D:\Charles\My Real Videos to the Videos library, and set it as the default save location)
- Defrag and image my C drive (now only containing OS + programs + app data + remnants of my old, empty user folders) to the SSD
- Delete the C partition from my HDD
- Expand the D partition to the full 2TB on my HDD
- Install the SSD as the new C boot drive
Notes:
- I'm using Win7 libraries instead of the old technique of moving user folders' location. Is this the preferred method nowadays?
- I'm leaving AppData on the system drive — too many users have had serious trouble, even when making no mistake in the process. (e.g. can't update from Win8 to 8.1) Do you agree that it's an acceptable compromise to leave AppData alone? I really wanted complete separation between static OS/programs and dynamic data/settings, but the problems seem like a dealbreaker. Is there anything wrong with leaving AppData on the C drive? (It just means I have to back it up daily and, if I ever reimage the system drive, to remember to take one last current backup of AppData.)
Thanks for your guidance!