Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

node.exe from node.js conflicts node.exe from Microsoft HPC Pack #7773

Closed
fyears opened this issue Jun 12, 2014 · 7 comments
Closed

node.exe from node.js conflicts node.exe from Microsoft HPC Pack #7773

fyears opened this issue Jun 12, 2014 · 7 comments
Labels

Comments

@fyears
Copy link

fyears commented Jun 12, 2014

node.exe is kind of not-so-usual name. But sadly I installed Microsoft HPC Pack that added its path into PATH in Windows environment and had a node.exe in the path before I installed node.js with official Windows installer.

To avoid any conflicts besides the one caused by Microsoft HPC Pack, I created a nodejs.cmd in C:\Program Files\nodejs, since nodejs is likely to be well known and unique.

:: nodejs.cmd
:: Created by fyears, modified from npm.cmd
@IF EXIST "%~dp0\node.exe" (
  "%~dp0\node.exe" %*
) ELSE (
  node %*
)

Maybe joyent could consider adding this nodejs.cmd in the official Windows installer.

@Mithgol
Copy link

Mithgol commented Jun 12, 2014

You could also reorder paths in the PATH (giving the Node's path a higher priority) unless Microsoft HPC Pack relies on being able to call its node.exe without the exact path.

@fyears
Copy link
Author

fyears commented Jun 12, 2014

@Mithgol yes of course. But...

Firstly, I have no idea why Microsoft HPC Pack was installed in my computer. Well, you know, many unknown dependencies when you are installing things in Windows.

Secondly, the PATH of Microsoft HPC Pack and node.js are both added automatically, while Microsoft HPC Pack automatically adds its path in the beginning and node.js automatically adds its path in the end. To keep this automatic process unchanged, I think adding nodejs.cmd in (official installer of) node.js folder is a good idea.

@Mithgol
Copy link

Mithgol commented Jun 12, 2014

Why bother keeping this automatic process unchanged? Let's change it. It's quite possible (I hope) to make the installer of Node.js adding the target path to the beginning of PATH instead of its end. (Though I may be wrong actually; I am not familiar with the installer used by Node.)

@trevnorris
Copy link

This is an unfortunate circumstance, but I'm not quite sure what we're able to do about it. Or even what the node related issue actually is.

@matsilva
Copy link

matsilva commented Dec 2, 2014

Similar issue here #6856

@jasnell
Copy link
Member

jasnell commented Aug 29, 2015

Nothing to do here.

@jasnell jasnell closed this as completed Aug 29, 2015
@theoutlander
Copy link

I usually end up renaming HPC's node.exe to HPCNode.exe. Microsoft needs to be smart about this. They can very easily prefix everything with HPC....given that half the exe's in that folder are HPC*.exe!

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

No branches or pull requests

6 participants