![]() ![]() So as already recognized, the / itself is the problem with the symlinks.įirstly, we should look at the syntax of options and required parameters generated by entering the mklink command help request, mklink /?: MKLINK | | ] Link Target ![]() Looks like Link Shell Extension is interpreting / itself and might provide \ to the underlying Windows API? Something which Windows itself isn't doing, but simply using / as are stated in the link itself, which is wrong for paths. Clicking "Ziel öffnen" opens a new Windows Explorer folder showing the link target. Have a look at the following screenshot, which is showing the relative path. ![]() Some additional interesting thing I just recognized: Opening the created symlink with the above syntax in cmd.exe and Windows Explorer directly fails, but it succeeds in Link Shell Extension. So I suggest repeating your test using Junctions yourself. D in my test, but I might be missing something of course. That should point to: C:\Users\crack\Documents\\\Ĭ:\Users\tschoening\Documents\test\target>cd ""ĭie Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.Ĭ:\Users\tschoening\Documents\test\target>Īt least I don't see any other difference than /J vs. I want to create a RELATIVE PATH symbolic link named at the following path: C:\Users\crack\Documents\\\\Audio\Music For exact details, please review the CMD screenshot. I'm going to drastically simplify everything I have tried. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |