Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOSKEY not working on Windows 10 with clink #451

Open
ghost opened this issue May 15, 2017 · 8 comments
Open

DOSKEY not working on Windows 10 with clink #451

ghost opened this issue May 15, 2017 · 8 comments

Comments

@ghost
Copy link

ghost commented May 15, 2017

On a clean install of up-to-date Windows 10 x64 DOSKEY does not work inside clink attached prompt. I can run e.g. DOSKEY c=cls giving no errors but that mapping is not found after pressing c. Show stopper for me and I'm sure many others. Thanks.

@yongxiu
Copy link

yongxiu commented May 16, 2017

+1, this used to work until I upgraded to Windows 10 Creators update.

@kyeongsoo
Copy link

Same here. My Win10 is "Version 1703 (OS Build 15063.296)".
I can still list all the macros already loaded through autorun by "doskey /macros", but none of them work.

@tx46
Copy link

tx46 commented Jun 1, 2017

This needs to be fixed urgently for clink to be usable at all. What can be done about it?

@Stanzilla
Copy link

@philiparvidsson you wait for @mridgers to come back or you fork.

@vvs
Copy link

vvs commented Jun 13, 2017

This is affecting me as well, I've been struggling without my aliases for quite a while, and finally today spent an hour trying to figure out why they don't work anymore, and it turned out that clink on Windows 10 can't handle doskey.

Anyone has any idea what's wrong and how/where to fix it?

@ghost
Copy link
Author

ghost commented Jun 13, 2017

As @Stanzilla says this project looks dead so might as well drop clink

@vvs
Copy link

vvs commented Jul 16, 2017

Just FYI, the PR #464 fixes this problem for me.

@DanyGee
Copy link

DanyGee commented Jan 8, 2019

Here is what I did to enable DOSKEY aliases on WINDOWS 10 (Build 17134) with clink enabled.

  1. Created doskey.cmd file with my aliases in it:
@echo off
doskey np="C:\Program Files (x86)\Notepad++\notepad++.exe" $*
doskey ls=dir $*
doskey ns=nslookup $*
doskey ip=ipconfig $*
doskey hosts="C:\Program Files (x86)\Notepad++\notepad++.exe" C:\Windows\System32\drivers\etc\hosts
doskey aliases="C:\Program Files (x86)\Notepad++\notepad++.exe" C:\Windows\System32\doskey.cmd
doskey youtube-dl=D: $T cd Dropbox\Windows\Programs\Portable\ $T echo Now launch: youtube-dl.exe YOURLINK --format best
  1. Put the doskey.cmd file in C:\Windows\System32 folder - this is crucial ❗️ It tends not to work from other locations 🤔
  2. Last step is to launch cmd with additional parameter, our doskey.cmd file that is...
    2019-01-08_08-36-24

This way every time you launch cmd, it will inject doskey.cmd file to it, even with clink enabled.
There is also an option to inject doskey.cmd through registry, but once clink is enabled, this trick is already used by clink itself, thus, cannot be used by doskey, and the /K parameter trick is the best workaround I've found so far.
2019-01-08_08-56-00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants