Need help with custom command (mklink)

[geo909]

Dear all,

New TC user here, I'm having trouble creating new command buttons, any help would be appreciated. The one that I'm currently having trouble with has to do with making junction links. If I open a cmd terminal and run "mklink testlink /J C:\myfolder", then this will create a junction link of "C:\myfolder" on the current path, named "testlink". However, if I create a button like this:

Image: https://i.imgur.com/2Nw4BAG.png

which I would assume that it creates a link of the target path onto the current one, I get instead the error:

Image: https://i.imgur.com/jX1dQ1o.png

Could somebody explain to me how to create a button that does what I want?

Thank you in advance.

[Stefan2]

Hi and welcome geo909

Please take a right click on your button, chose COPY and paste the button code in here.


Additionally you can take a search on the forum to find f.ex:
viewtopic.php?f=28&t=51775&p=357299&hilit=mklink#p357299
and some other examples.




c u later
 

[Usher]

2geo909
Do you use 32-bit TC in 64-bit Windows?

[Dalai]

mklink is an internal CMD command, so there is no EXE which TC could launch. You must specify cmd.exe as application and mklink as the command to run by CMD. Example:

Code: Select all

TOTALCMD#BAR#DATA
cmd.exe
/c "mklink /J testlink %T"
C:\Windows\System32\cmd.exe
mklink


-1

To copy the button, mark the code above and paste it onto a free space on your button bar.

[EDIT] Typo [/EDIT]

Regards
Dalai

[Horst.Epp]

From Petermad's extended Menus for TC:

Code: Select all

[em_ext_junction]
cmd=%COMSPEC% /K
param=if exist %P%N\* (mklink /J %T%N %P%N) else (echo The cursor must be on a FOLDER)
path=%SYSTEMDRIVE%\
menu=Make Junction in Opposite Panel to FOLDER Under Cursor (Not on Network)
button=%COMMANDER_EXE%,12

[em_ext_symlinkd]
cmd=*%COMSPEC% /K
param=if exist %P%N\* (mklink /D %T%N %P%N) else (echo The cursor must be on a FOLDER)
path=%SYSTEMDRIVE%\
menu=Make Symlink in Opposite Panel to FOLDER Under Cursor
button=%COMMANDER_EXE%,12

[em_ext_symlink]
cmd=*%COMSPEC% /K
param=if not exist %P%N\* (mklink %T%N %P%N) else (echo The cursor must be on a FILE)
path=%SYSTEMDRIVE%\
menu=Make Symlink in Opposite Panel to FILE Under Cursor
button=%COMMANDER_EXE%,12

[em_ext_hardlink]
cmd=%COMSPEC% /K
param=if not exist %P%N\* (mklink /H %T%N %P%N) else (echo The cursor must be on a FILE)
path=%SYSTEMDRIVE%\
menu=MAke Hardlink in Opposite Panel to FILE Under Cursor (Only on Same Drive)
button=%COMMANDER_EXE%,12

Fore full absolute fantastic menus see:
https://www.ghisler.ch/board/viewtopic.php?t=33740

[geo909]

Thanks a lot guys! Dalai's suggestion works, I'll look into Horst.Epp's a bit more to understand what it does.

@usher: I'm using 64 bit windows
@Stefan2: Thanks for the suggestions, I'll have them in mind.

[Horst.Epp]

Thanks a lot guys! Dalai's suggestion works, I'll look into Horst.Epp's a bit more to understand what it does.

@usher: I'm using 64 bit windows
@Stefan2: Thanks for the suggestions, I'll have them in mind.

Add the em_commands into your usercmd.ini and you can use them in menus, buttons or assig Hotkeys to it.

[MVV]

geo909,
1. You can't use %-parameters in Command field, only in Parameters.
2. mklink is not a separate program, it is an internal command within cmd.exe.
That's why Dalai's button is correct.

BTW, you can use my NTLinks Maker tool if you need to create links often.

[Usher]

@usher: I'm using 64 bit windows

My question was about both TC and Windows bitness. In 64-bit Windows you should use 64-bit TC, otherwise some features (system commands, paths on disk, etc.) may be unavailable.

[petermad]

2geo909

I'll look into Horst.Epp's a bit more to understand what it does

These are external commands that are meant to be used together with my Extended Menus (see signature), but they can of course alo be used for your own buttons and shortcuts. See: http://madsenworld.dk/tcmd/symlinkmenu.png

[3axarko]

I read comments above and wrote command for selected files.

Code: Select all

[em_ext_hardlink]
cmd=cmd /C
param=(for /d %%a in (%P%S) do mklink /H "%T%%~na%%~xa" %%a)
path=%SYSTEMDRIVE%\
menu=Make Hardlink in Opposite Panel to all selected files (Only on Same Drive)
button=%COMMANDER_EXE%,12

you can pause operation if something goes wrong

Code: Select all

param=(for /d %%a in (%P%S) do mklink /H "%T%%~na%%~xa" %%a||if not [%errorlevel%]==[0] pause)

Than I added it to %appdata%\GHISLER\usercmd.ini
Than Start -> Change Start Menu -> Add Item
Search in command field "em_ext_hardlink"
Shortcut Key = Ctrl+Alt+Shift+F5
And "Voila". I can create links without any side program or plugin.

[Dalai]

23axarko
There's one important thing I don't understand. As far as I see the command iterates over directories and tries to create hardlinks to them. But hardlinks cannot point to directories (only to files).

PS: You can shorten

Code: Select all

%%~na%%~xa

to

Code: Select all

%%~nxa

One other thing: I strongly recommend to quote loop variables within a command, i.e. it's better to use

Code: Select all

mklink ... "%%~a"

instead of

Code: Select all

mklink ... %%a

.

[3axarko]

2Dalai
Thanks for the advice.
Variable "%%a" will create two quotes for each side. Like ""audio_file.mka""
I tried to do the same using for /r, but it didn't work. I wasn't able to replace the quotation marks in the file names using a single line of code. However, even though /d is supposed to iterate through directories, it worked on files as well.

[Dalai]

Variable "%%a" will create two quotes for each side. Like ""audio_file.mka""

Look more closely. I used "%%~a" instead of "%%a".

However, even though /d is supposed to iterate through directories, it worked on files as well.

That's not what I'm seeing. Check out this code directly on a CMD:

Code: Select all

cd /D "%SystemRoot%\"
for /D %T IN (*.*) DO echo %T

I don't get any files in my output because the /D switch limits the loop to directories.

But I think I know why it works for you. If you select only files in TC the parameter %P%S will be replaced with their names. But as soon as you select directories, the mklink command will throw an error. Not sure if it's intentional that the for loop behaves the same way with and without the /D switch in such cases. I still suggest to remove the /D switch as it is irritating to read such code which doesn't really make sense.

One more thing: Be aware that the command line has a length limit that is reached rather quickly if you use %P%S. It's much better to use a list file via %L or %WL instead. The for loop must be told to work with a file in that case, something like this:

Code: Select all

for /F "delims=" %%F IN ('type "%WL"') DO mklink ...

[white]

It's much better to use a list file via %L or %WL instead. The for loop must be told to work with a file in that case, something like this:

Code: Select all

for /F "delims=" %%F IN ('type "%WL"') DO mklink ...

I'm not sure I agree with that. AFAIK "For /F" has limited Unicode support, so if you don't change the codepage to UTF-8 first, you might run into trouble.