I have installed www.deployd.com on my Windows-XP PC for learning purposes. The book am studying ask me to execute the following command at the prompt ::
> dpd create sportsstore
but i get the following error message
Node.exe is not a valid Win32 Application
What must i do to rectify this error?
Thanks.
UPDATE
The node.exe it is complaining about is inside the the tools folder of Deployd. It is like this
C:\program files\Deployd\tools\Node.exe is not a valid Win32 Application
That error is usually an indicator of trying to run a 64bit application in a 32bit OS.
The solution is to change the version of node to the 32bit version. Be careful to choose the same version as your tutorial to avoid any conflicts.
Related
I am a complete newbie to all this.
I tried to install node.js 4 times and then again uninstalled it every time trying different things, thinking one of them would work.
The link to the question is-Cannot find runtime 'node' on PATH - Visual Studio Code and Node.js
After I typed $node --version in powershell terminal in VSCode (after installing node.js in C drive, defaulting to all recommended options in the setup) I get an error. I have uploaded the image of the error.
the error
Please tell me how to get node.js working with VSCode.
To get the version of Node, just type node --version in the terminal without the "$".
msvcrt.lib(chkstk.obj) : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
I found the problem. trying to run rust from developer powershell was causing the problem. In regular Windows PowerShell without path tweaks for Visual Studio, link.exe is not found in the command path, so cargo appears to magically discover the absolute path name in the x64 tools directory, which is the correct one. The host architecture of the shell does not affect this behavior.
Unfortunately, the launchers named Developer PowerShell and Developer Command Prompt for VS 2019 set up the command path for x86 tools. Perhaps it would be better for cargo to ignore the PATH-located executable on Windows if the registry-resolved tools directory appropriate for the target platform contains the executable file.
I have a nodejs project in Vs2013
I built it on a w7, 64 bit machine, and it's working, on my main box, check it into TFS and it builds and runs test in Team city. Also runs from a batch file that calls protractor.cmd directly.
I pulled it down on a second box, windows 7, 64 bit
installed Java jdk, VS Node tools, node.js, protractor, VS2013 update 4.
If I run it from the batch file it runs fine. If a debug the project in vs2013 it crashes with the error above
The specified executable is not a valid application for this OS platform.
There are some SO questions that says node.exe is the problem but I searched my drive (with agent ransack) and can't find node.exe anywhere.
I uninstalled the 64 JDK and installed the 32 bit JDK and no joy..
I'm assuming I've installed the wrong version of something.. but I don't know what
Any Ideas? Any Help Is appreciated.
Make sure you added Node.exe to the path.
You said you installed nodejs, so look for Node.exe in something like C:\Program Files\nodejs\
If you can't find Node.exe, then uninstall nodejs and reinstall it and pay attention to where it installs.
Now that you have Node.exe, add it to the path by
right click on My Computer
select Properties
activate the Advanced tab
click the Environment Variables button
edit the Path system variable
I want to use Node.js under Windows XP. I've downloaded the node-v0.10.15-x86.msi installer but when I try to install Node.js I always get this error at the middle of the process:
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2908.
Here is a screenshot:
Is it possible to install Node.js on Windows? I cannot find any installation instructions on their site. I have AMD Athlon XP 1833 MHz processor. It is quite old processor. May this be the reason?
So, I figured out how to install it :)
I did a double click on node-v0.10.15-x86.msi file in order to install Node. And that caused an error.
.msi files shouldn't be installed that way. I found a solution on this page http://thebackroomtech.com/2007/08/23/howto-extract-files-from-a-msi-file-using-the-windows-command-line/
So my steps in Windows command line. I pointed a directory where to unpack node-v0.10.15-x86.msi to:
C:\>msiexec /a "C:\Downloads\Programs\Node.js\node-v0.10.15-x86.msi" /qb TARGETDIR="C:\Program Files\nodejs"
And now it works. It unpacked Node.js and all its dependencies to C:\Program Files\nodejs. I just added the directory to PATH.
I'm glad I can use Node on Windows. Working under Ubuntu is a pain.
I had the same problem. For resolve this problem you need to remove this key from registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-21-1123561945-1935655697-1060284298-1003\
Components\AD95649F068525549B26938D7D18FEA7
Founded here
For me the S-1-5-21 was different, I renamed it to _del
HKEY_LOCAL_MACHINE
\SOFTWARE
\Microsoft
\Windows
\CurrentVersion
\Installer
\UserData
\S-1-5-21-1292428093-1606980848-1188629396-500_del
I am getting this error on a node native addon I created. It works fine on my development machine, but breaks on the test machine.
module.js:485 process.dlopen(filename, module.exports);
Error: The specified module could not be found.
j:\node_modules\mhl-dispatcher\node_modules\node-odp\libs\build\Release\odpnode.node
In the c++ code, I'm using some dlls:
System.dll
System.Data.dll
Oracle.DataAccess.dll
I am using the /clr option.
Any ideas to what the issue might be?
Thanks.
I've figured out the problem, There are two dlls required to run c++ natives on a machine msvcp100d.dll and msvcr100d.dll. The are added by installing the Ms visual c++ 2010 redistributable package. Also for those running 64 bits you would the the 64 bit versions of the dlls or you would get an error.
Error : %1 is not a valid Win32 Application
Hope this helps others.
Cheers
Node either couldn't find the file in any location that it tried, or the Object file does not export a NODE_MODULE symbol.