After installing the latest version of WebPICmd.exe from the chocolatey gallery (https://chocolatey.org/packages/webpicommandline, 7.1.1374) on windows 8 I am not able to use the problem. For some reason the command output is going to a new console window, which immediately closes. I am running the command from PowerShell.
On Windows 7, it behaves nicely and the output of webpicmd.exe goes to my current window. I cannot imagine why it would work otherwise for windows 8.
Can you try launching your CMD (One you run WebPICmd in) as Administrator.
Related
I am on Windows running Intellij and Git for Windows SDK for a feature rich terminal on Windows (pacman, oh my zsh, etc...)
I looked up previously on which command to use to make it the default Intellij Terminal and SO delivered:
How can I launch git-for-windows SDK's git-bash in Windows Terminal?
I am using the cmd from above's 2nd post:
C:\git-sdk-64\msys2_shell.cmd -defterm -here -no-start -mingw64
Everything works fine except for a stubborn resizing issue :
Every time I resize the Intellij Terminal, the MSYS terminal stops receiving key strokes and I have to reopen a new one:
( can't type after the resize under the echo hello )
Trying to avoid WSL for now as I noticed maven builds through wsl were noticeably slower than directly on powershell or via git terminal.
Workaround
Not exactly a solution but if you run with MinGW32, the resize no longer causes the problem
To be seen if I will suffer from other 32/64 bit incompatibilities
using for now:
C:\git-sdk-64\msys2_shell.cmd -defterm -here -no-start -mingw32
I have installed Node Js on Windows 10 64 bit to learn Node JS. When i type
node -v a cmd window flashes and goes away. When i run the node.exe from the program files, i can run the node commands there such as "console.log". Am I missing something?
Moving the Node JS Path variable to the top/ahead, worked.
I had the same problem. I tried uninstalling/reinstalling different versions, but ultimately reinstalling Windows did the trick.
I just had this problem yesterday with windows 8 64 bit version.
On a whim, I checked if the node.exe [right click on the icon] properties have "run as administrator" checked in the compatibility tab. It did. But my command window wasn't in an elevated [administrator] prompt.
I just needed to check the version, node --version.
Unchecking run as administrator stopped the window from disappearing.
What helped me was to change the cmd.exe settings to TrustedInstaller. Right click on cmd.exe -> properties -> security -> change the setting there.
On Windows 10, when I run Node.js commands (e.g. node -v) from a PowerShell console, they always spawn a new Windows Command console. When I run the same commands from a Windows Command prompt, they run in that same console session. Interestingly, whatever this is appears to cause the same behavior when running Node commands via the Task runner in Visual Studio Code and when Visual Studio 2017 build steps contain Node commands - each Node command run spawns a new console. This only started about a week or so ago. I don't recall any updates to my PC that could be related. Other developers on my team that use the same tools don't experience this same behavior. I have another PC that this doesn't occur on. What could be causing this?
Windows 10
Node.js v7.8
I have two Windows 7 machines. On one machine I can run python scripts by double clicking on the .py file, however on the other machine the script does not execute, the command prompt will flash quickly and the script does not execute. I can execute scripts on both machines using the command line. I have the same version of python installed on both machines.
How do I ensure that a python script can be executed by double clicking the script on Windows 7?
Step 1. Check if your .py files are associated with "python launcher" (Not just "python"). You can check that by right clicking the .py file and see:
In my case, I have two machines of Windows 10. The one with Python 3.6 installed by choosing "Install Now" works perfectly. The another one which having the same version of python installed in a customized location has problems. It seems nothing to do with the environment path setting, as I could run python in the console mode correctly. So at the end, I was forced to uninstall the python, (then removing all the related paths manually if needed), and install it again with default setting "Install Now".
I have done my homework, honest, and tried everything I can think of but it seems that every time I open CMD I get the 32bit version, regardless of where I open it from. I have tried:
Windows start orb -> CMD -> enter
Typing 'C:\Windows\System32\cmd.exe'
Typing 'C:\Windows\SysWOW64\cmd.exe'
In each case I am running it with Admin rights and I have UAC turned off. I can tell it's always 32 bit as I am unable in any case to run nbstat.exe (which I would expect from a 32 bit command line).
I have been into Process Explorer and both version are nodes under the same instance of csrss.exe which doesn't feel right to me.
Any thoughts?
The easiest way to see if a process launches 64- or 32-bit is to go to the process tab of the task manager, a 32 bit CMD will show as cmd.exe *32.
One way to launch a 64-bit CMD is to just use "My Computer" and double click C:\Windows\System32\cmd.exe.
One way to launch a 32-bit CMD is to do the same but double click C:\Windows\SysWOW64\cmd.exe.
Slightly odd observation; it seems that if you launch the 64-bit CMD from a 32-bit one, it will also launch as 32-bit. That may be why you're seeing the 32-bit version show up all the time. Explorer is a 64-bit process and can launch CMD in 64-bit mode.
The version of command prompt that windows spawns matches the bit-ness of the launching process, via the magic of windows path redirection. Therefore, a command prompt started from a 32-bit program will be a 32-bit command prompt, and one started from a 64-bit application a 64-bit command prompt - Microsoft Technet.
The technet article suggests creating a symlink to the 64-bit version of the command prompt executable to defeat the redirect.
Reading the comments reveals that an easier method exists (not Win XP), you can use the virtual folder C:\Windows\Sysnative to get the native versions of the system tools.
Therefore, to always get a 64-bit command prompt on 64-bit windows, execute:
C:\Windows\sysnative\cmd.exe