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

Can't run cmder.exe #389

Closed
Limro opened this issue Feb 12, 2015 · 8 comments
Closed

Can't run cmder.exe #389

Limro opened this issue Feb 12, 2015 · 8 comments

Comments

@Limro
Copy link

Limro commented Feb 12, 2015

http://www.reddit.com/r/programmingTools said this was the shit and I wouldn't be sad to walk away from PowerShell.
But when it doesn't run at all, I get a bit sad.

The process:

  • Download .7z-file (24.7 MB) version
  • Extract to C:\Programming Filez (x86)\CMDer\
  • Move CMDer.exe, msvcp120.dll, msvcr120.dll and Version v1.1.4.1 to \bin\ folder
  • Open PowerShell
  • cd to folder
  • Run Cmder.exe /REGISTER ALL, which yells error
  • Open PowerShell as admin
  • Run the same command - no output
  • Double click the Cmder.exe - nothing happens
  • ./Cmder.exe - nothing happens
  • Check Path variables - no changes (Cmder.exe not added)

Got a fix?

@Stanzilla
Copy link
Member

Leave out that part

Move CMDer.exe, msvcp120.dll, msvcr120.dll and Version v1.1.4.1 to \bin\ folder

@MartiUK
Copy link
Member

MartiUK commented Feb 12, 2015

Who told you to move the binary files into a bin folder?

@Limro
Copy link
Author

Limro commented Feb 12, 2015

Who told you to move the binary files into a bin folder?

From the installation manual in the README.md:

Step 3: Place files into bin folder, it will be injected into your PATH.

@MartiUK
Copy link
Member

MartiUK commented Feb 12, 2015

@Limro That's for other binaries or programs you want to use, why would we ask you to move the cmder launcher binaries yourself?

@Limro
Copy link
Author

Limro commented Feb 12, 2015

@MartiUK It's odd, right. But the manual didn't say which files to move, and I wanted the cmder to be in my PATH :)

@MartiUK
Copy link
Member

MartiUK commented Feb 12, 2015

@Limro The normal usecase is for you to have it anywhere you like but launching it using the launcher executable (cmder.exe), from what it sounds like you are opening up a powershell instance and then using that to run cmder. cmder is your terminal emulator/console/'dos prompt' as it runs cmd, powershell or whatever for you.

@Limro
Copy link
Author

Limro commented Feb 12, 2015

Yup - I think I got it now 👍 Thanks a lot.

@MartiUK
Copy link
Member

MartiUK commented Feb 12, 2015

@Limro No problem 👍

Jackbennett added a commit to Jackbennett/cmder that referenced this issue Feb 26, 2015
In reference to cmderdev#389 I thought I'd just clear up this instruction even more.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants