Overclock.net › Forums › Components › Hard Drives & Storage › SSD › Make SSD inaccessible to user but able to be windows primary and boot?
New Posts  All Forums:Forum Nav:

Make SSD inaccessible to user but able to be windows primary and boot?

post #1 of 9
Thread Starter 
Did some searching and found some similar threads but nothing really answering the question I have.

Basically I'm building a PC for my parents and want to add in an SSD for windows boot and load times. However, I only want to buy a 64 or 128GB and don't want them able to put stuff on it. I obviously want to make it primary and boot drive for windows operating system.

I only want my parents to be able to save files, install programs and see HDD . Is this possible?
post #2 of 9
I would just install it along with the HDD and copy the "Users" directory over to the HDD. Then delete the original folder and create a symbolic link to the "Users" directory on the HDD. The command for creating the link would be the following, assuming E: is the HDD (You must run the command prompt as an administrator).
Code:
mklink /d "C:\Users" "E:\Users"
Anything saved to My Docs, pics, etc. will go straight to the HDD transparently. All installed programs will stay on the SSD.
post #3 of 9
Thread Starter 
Thanks for the info. That's the best solution so far. However, I was also trying to keep the garbage programs they tend to download/install off the SSD as well. Just want windows on it and programs that I can install as admin or something.
post #4 of 9
Repeat the above process for the Program Files directories. The only downside is that all programs will have to run from the HDD unless you install them to a non-standard location. You could always create a new directory for programs you want to run from the SSD. i.e. C:\SSD\Program Files
post #5 of 9
Thread Starter 
Awesome! Thanks for all the help. Will be giving it a shot this weekend.
post #6 of 9
You won't be able to do this while in the OS... You can't just move folders that are in use. You can copy them, but you won't be able to create the mklink files because of a name conflict. It's likely that you would have to throw the drives in another PC to do it.
post #7 of 9
Thread Starter 
Quote:
Originally Posted by Powermonkey500 View Post

You won't be able to do this while in the OS... You can't just move folders that are in use. You can copy them, but you won't be able to create the mklink files because of a name conflict. It's likely that you would have to throw the drives in another PC to do it.

So those steps will work in another pc? I feel like there should be an easier solution for this since SSDs came out and are still expensive for large drives.
post #8 of 9
Quote:
Originally Posted by AMD_King View Post

So those steps will work in another pc? I feel like there should be an easier solution for this since SSDs came out and are still expensive for large drives.

It's possible, but a bit more convoluted and obnoxious.
You would have to create the mklink files using the original PC, but in another directory to avoid the name conflict. I believe Windows prevents you from making mklinks if the target directory is not currently valid. Assuming drive letters will change, this would avoid possible headaches.
Then you would have to switch both drives to another PC (or load a bootable disk with an OS. Linux has flaky NTFS support in most cases though) and move the directories over to the hard drive, and copy the mklink files to their proper locations.
post #9 of 9
Quote:
Originally Posted by Powermonkey500 View Post

You won't be able to do this while in the OS... You can't just move folders that are in use. You can copy them, but you won't be able to create the mklink files because of a name conflict. It's likely that you would have to throw the drives in another PC to do it.
I hadn't considered that. I've never tried to link the program files folders before. It may work in safe mode, assuming nothing from the directories in question is loaded.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: SSD
Overclock.net › Forums › Components › Hard Drives & Storage › SSD › Make SSD inaccessible to user but able to be windows primary and boot?