View Single Post
Old 08-23-2016, 05:25 PM   #8
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,786
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
You do not need the junction utility to create symbolic links in Vista or later versions of Windows, better by far to use the built-in MKLink command.

The only reason MS keeps junction 'on the books' is for legacy reasons, which is primarily a concern for corporate LOB systems.

And if you put 'foreign objects' into Windows/System32 then should you ever need to reinstall Windows you will lose them. Far better to put such things into something like a C:\Utilities folder, and add that folder to the Path environment variable.

If you want a GUI tool to create symlinks, Symlink Helper adds an option to Windows/File Explorer right click menu (n.b. first time it's run you need to run it as admin). I use Link Shell Extension, which also handles hard-links, junctions, and mount points, includes a drag/drop create feature, a repair function for symlinks, mount points and junctions, hard-link lists and counts, and icon overlays etc.

BR

Last edited by BetterRed; 08-24-2016 at 04:14 AM.
BetterRed is online now   Reply With Quote