MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Search the Community
Showing results for tags 'program files'.
Found 1 result
I'm setting up a new computer that will have a 250 GB Samsung EVO 850 SSD and two 1 TB Seagate Barracuda hard drives. I want the SSD to be the boot drive and have the Windows folder with the operating system (Windows 7 Professional 64 bit). I also want to have a few programs on the SSD: browsers, email, and VLC Player. I prefer to have a lot of software programs. (That's just me. I have my reasons; don't waste your time trying to talk me out of it.) I don't want to overcrowd the SSD. I want to keep the great majority of programs and of the application data folders on one of the Seagate drives. I guess you could say I basically want a big Program Files folder on a Seagate drive and a mini-Program Files folder on the SSD. What's the proper way to proceed? Install the whole system drive package, with Program Files and user profiles/accounts as well as the actual OS (which I assume is synonymous with or subsumed in the Windows folder) on one of the HDDs, and then migrate just the Windows folder to the heretofore blank SSD and set the SSD as boot drive in the BIOS? Or should I install Windows 7 to the SSD and then create parallel Program Files and application data folders on the Seagate hard drive? Or maybe move Program Files to the Seagate if possible, and just have my small number of programs on the SSD in their own folders there?