I'm going to drastically simplify everything I have tried. For exact details, please review the CMD screenshot.
I want to create a RELATIVE PATH symbolic link named [ RESOURCES ]
at the following path:
C:\Users\crack\Documents\[ GLOBAL ]\[ SOURCE ]\[ INITIATIVES ]\Audio\Music
That should point to:
C:\Users\crack\Documents\[ GLOBAL ]\[ SOURCE ]\{[ LONGCHAR REDIRECT ]}
I have been trying mklink /D
in cmd as admin, with the following steps.
Navigate to the directory the symbolic link should be created in.
cd "C:\Users\crack\Documents\[ GLOBAL ]\[ SOURCE ]\[ INITIATIVES ]\Audio\Music"
Create the symbolic link.
mklink /d "[ RESOURCES ]" "../../../{[ LONGCHAR REDIRECT ]}" symbolic link created for [ RESOURCES ] <<===>> ../../../{[ LONGCHAR REDIRECT ]}
To the BEST of my understanding, this syntax SHOULD set the link to {[ LONGCHAR REDIRECT ]}
in [ SOURCE ]
relative to Music
but it doesn't!
The confirmation indicates that the link was created successfully but when I try access the symbolic link I get the following error:
cd "C:\Users\crack\Documents\[ GLOBAL ]\[ SOURCE ]\[ INITIATIVES ]\Audio\Music\[ RESOURCES ]"
C:\Users\crack\Documents\[ GLOBAL ]\[ SOURCE ]\[ INITIATIVES ]\Audio\Music\[ RESOURCES ] is not accessible.
The filename, directory name, or volume label syntax is incorrect.
Am I misunderstanding the use of ..
to indicate a parent directory? Again, please feel free to review my multiple experiments via the CMD screenshot. I've tried multiple variations on the relative file path theme, using ..
, .
, and changing around the current directory.
If mklink
will not implement the desired association, please also feel free to recommend a relative file path alternative. I copy the [ GLOBAL ]
directory to various drives and backup services, so I need the file-paths truncated to beneath the 260 MAX_PATH
limitation via their actual location in the {[ LONGCHAR REDIRECT ]}
folder to be reflected across each duplicate location, but I need my working directory to include their virtual locations in the [ RESOURCES ]
folder.