It has been asked what other little things can be done to squeeze a litle more performance from Windows 7 on our SSD drives... One thing that helps maintain performance on an SSD is the percentage of free space available to the SSD controller to execute 'wear leveling'. Basically, spreading out the load to the least used empty memory cells.
In order to do this, we need to fool Windows and other programs into looking elsewhere for stuff that is necessary, but rarely used and taking up a lot of disk space.
This part is only useful IF you have your operating system on your SSD AND it is formatted as NTFS and have a second drive available (NTFS) with space free to use.
What we are going to do is move certain directories to the other drive, then make Windows (and the programs) think it is still on the boot drive. We do this by using an NTFS 'junction'. Think of a junction as a pointer to a location. To the operating system, the files look like they are in location A, but they are really physically in location B.
For the tutorial, we are going to assume that the SSD is C: and the second drive is E:. Substitute your drive letters as needed. As always, MAKE A BACKUP FIRST!
If you are still with me, here is how to do it (the easy way):
Go to http://schinagl.priv.at/nt/hardlinks...kshellext.html and download (and INSTALL) the link shell extension software (and VC runtime, follow the instructions on the site) for your flavor of Windows 7
(or barf Vista).
Make sure explorer is set to SHOW hidden and system files (Tools/Folder Options/View tab, Show hidden, uncheck Hide protected operating system and hide extensions)
Create the following directories:
Boot into safe mode. Open explorer and navigate to C:\Windows.
Right click on the Installer directory and select CUT
Navigate to E:\WinSystem\Windows right click and select paste. It should have created the directory E:\WinSystem\Windows\Installer with files in it.
Right click the directory E:\WinSystem\Windows\Installer and select Pick Link Source.
Navigate to C:\Windows and right click in the directory and select Drop As and select Junction.
You should now see C:\Windows\Installer is back (with a wierd link on the folder icon)... The OS now will put installer files on the other drive and look for them there, but think it is still on c:!
Other directories I do this with are the HP install directory (C:\SwSetup) and MS Office setup directory (C:\MSOCache).
In the previous tutorials, yo learned how to move the TEMP and internet Temporary files... This is a good place for them too. Here is the directory structure on my E:\WinSystem directory:
E:\WinSystem\Temporary Internet Files
Just make sure to drop the junction in the same place as the original directory and the OS will be none the wiser and you will have moved GIGABYTES of seldom used stuff of your SSD (and redirected some more writes)!
The only down side that I have found is as follows: If your backup strategy is like mine WAS, then you would only be making a backup image of the SSD. The problem is, that image backup software does not see that you moved the files, so they cannot copy the files in the E:\WinSystem directory with the image. The fix is quite simple if U are using Windows 7 backup: Along with the system image, have it back up the directory E:\WinSystem. Then it will keep them together and in sync (you restore the image AND the directory that went with the image).
Undoing the junction is easy too, if you want to. Simply delete the junction from the C drive and move the directory back where it was (hence the reasoning I had you create WinSystem\Windows\Installer instead of WinSystem\Installer as a reminder of where the directory was when U started (thinking of WinSystem as the root)!
Alphabetical Article List
Currently, there are 1596 Active Users (257 Members and 1339 Guests)
- › [Various] RX Vega 64 & 56 Reviews 1 minute ago
- › Ultrawide Curved monitors for Graphic Designers? 1 minute ago
- › [Official] Corsair Carbide Air 540 Owner's Club +Gallery 3 minutes ago
- › [ST] Bitcoin Price Update: OVER $2,200! 3 minutes ago
- › [Official] Screenshot of Your Games Thread 4 minutes ago
- › Official- Heatkiller Club 9 minutes ago
- › [Intel] Ice Lake to be the successor to 8th gen Intel Core processors 10 minutes ago
- › [eTeknix] Intel Core i9-7960X 16 cores, 32 threads Geekbench Scores... 13 minutes ago
- › [WCCFTech] AMD’s RX Vega 56 and 64’s $399 and $499 Price Tag Was A... 14 minutes ago
- › Vega Frontier / RX Vega Owners/Info thread. 16 minutes ago
- › HDPLEX H5 Fanless Computer Chassis by michelme67
- › Nuance Power PDF Standard by Lady Fitzgerald
- › ID-COOLING SE214L Snow Edition CPU Heatsink by DaveLT
- › Team Dark 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200)... by ADmodz
- › Logitech Wireless Keyboard K360 (Dark Silver) (920-003366) by enes13mes
- › PDF Studio 12 - Advanced PDF Editor for Windows - Pro Edition... by Lady Fitzgerald
- › Brand New Fujitsu ScanSnap ix500 Portable Document Scanner... by Lady Fitzgerald
- › Tecware Phantom Backlit Mechanical Keyboard (Red / White Backlit... by DaveLT
- › Allsop XL Mouse Pad- Raindrop Blue by neilyo
- › Manjaro Linux XFCE 64bit (Latest Version) Arch based linux by AlphaC
- › (OPINION) AMD shot themselves in the foot by...
- › The Best CPUs of 1H 2017 (DRAFT)
- › AM4 Motherboard manufacturers , make...
- › AsRock, you dissapointed me on Ryzen launch...
- › Why 240GB, 250GB , 256GB, and 275GB SATA3 SSD...
- › The Orion Spectrum: Everything You Need from...
- › Windows 10 Tweaks
- › Analyzing the Source Code of UEFI for Intel...
- › Overclock.net Counter Strike: Global...
- › DIY: How to do a fiber optic mechanical...