-
Notifications
You must be signed in to change notification settings - Fork 7.3k
node.exe from node.js conflicts node.exe from Microsoft HPC Pack #7773
Comments
You could also reorder paths in the |
@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 |
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 |
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. |
Similar issue here #6856 |
Nothing to do here. |
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! |
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
inC:\Program Files\nodejs
, since nodejs is likely to be well known and unique.Maybe joyent could consider adding this
nodejs.cmd
in the official Windows installer.The text was updated successfully, but these errors were encountered: