MKLINK – Create and Use Links in Windows

I'm using makelink with a Classic Shell toolbar. I'd like to make it so that when I click an item it makes a link to it, but if there's nothing selected, have it make a link to the current folder. I was told I'd need a .bat file with the if argument. What exact commands would I use to make the file?

Hi Kari et al,

Thanks for starting a thread and hosting great contributions! Alas, I still need help getting across the goal line with network drives.

Using examples here and on MS's site, I created a test symbolic folder link called "Lighting" here:

"F:\junk\TESTING Standard Project Folder TESTING\Documents\17-Specifications"

It points to the "Lighting" folder here:

"N:\junk\TESTING Standard Project Folder TESTING\Drawings\04-Design Development\01 Finishes Lighting & Specifications\Lighting"

The link has these issues:

• Right-clicking, selecting Properties and Open Folder Location leads to the Lighting folder (without opening it).
• Double-clicking on the link in Windows doesn't throw an error, but does produce an "Open With" window with (irrelevant) choices.
• Efforts to copy the link fail, claiming that "The filename, directory name, or volume label syntax is incorrect."

I really appreciate hearing of Skol's success. Does anyone have any ideas about what I'm doing wrong?

Thanks for all comments!

Thanks! It was created within admin-enabled command prompt while within the following directory:

"F:\junk\TESTING Standard Project Folder TESTING\Documents\17-Specifications"

mklink /d "Lighting" "N:\junk\TESTING Standard Project Folder TESTING\Drawings\04-Design Development\01 Finishes Lighting & Specifications\Lighting"

FYIs: F and N are the same location. The Properties browse confirms that Windows properly identifies it. I can't copy it in a window or in command prompt.

Oops; thanks, that makes the shortcut work as expected in the original location. Now, the shortcut/link works as expected there, and running the DIR command there describes the entity as a <SYMLINKD>.

The final hurdle is making the relative reference work on the live volume. This means copying it (or, in live use, the folder set in which it lives) to the production drive.

Here is where it appears to fail: When copied to the target location, the link becomes a directory there. In fact, it becomes a directory even when copied into a different folder in its own folder set.

I had thought that the symbolic reference would enable me to create a portable link whose reference would always be relative to the specification regardless of location as long as the relevant folder structure remained intact.

Might I be trying to use the entity in a way that is different from its intended use, or might it not work on Windows 2008 virtual servers running over xenserver?

Then I'm trying to use the symbolic link for something it's not intended to do. I'm looking for a way to build portable shortcuts (with relative references to their targets) into a template of folders so that, when users physically copy the template to a live destination, the copied shortcuts would point to the new destinations.

Autodesk uses "xrefs" - external references - in this way, with either absolute or relative references to files that support a main file being edited. Using relative references enables the entire file set to be moved to other drives or systems while preserving the external references.

Thanks for helping to clarify mklink and symbolic linking for me. I'll keep searching for my answer!

I have a post-it notes type app on my system where I keep all sorts of computer related info, including one titled "Junction Point Creation" which I'll replicate here. This is how I had to word it to myself for it to be completely clear. Since a certain measure of uncertainty usually accompanies this issue for many, hopefully it'll help clear any confusion, Kari's excellent article notwithstanding. Then again it may make things worse    :


Step 1.
 Move the folder in question from its current location ( OLDLOC ) to the new location where you'd like it to reside from now on ( NEWLOC )

Step 2.
 Execute : mklink /j "OLDLOC" "NEWLOC"

Step 3. ( optional )
 Set the 'h' ( hide ) attribute to the folder in question in OLDLOC ( not NEWLOC—the preceding command will have made it "reappear" in OLDLOC, i.e. in its original location… hence, the 'h' attribute if desired )