0.12.3 on Windows XP give not valid win32 application error

[deliverymanager]

I tested on a Windows XP platform.
a) 0.10.33 works fine.
b) 0.12.2 works fine
c) 0.12.3 after installing without a problem, I try to open the Node.exe and it gives me an error "node.exe is not a valid win32 application"

I have also tested the same win32 x86 0.12.3 version on a windows 7 platform and it works fine.
So, probably, this is related to a windows XP problem.

[jasnell]

duplicate of #25347

[misterdjules]

@orangemocha Do you have some time to investigate?

[orangemocha]

Not a dupe of #25347, as that one was reported on Windows 7, and this issue is specific to Windows XP.

Most likely would need to backport nodejs/node@e8d0850

[jasnell]

@orangemocha ah... ok.. missed that distinction entirely.

[JimHolloman]

I have the same issue on XP, 32-bit. Both the installation (.msi) package and the stand-alone node.exe file (I downloaded both) provide the message "node.exe is not a valid win32 application". The npm provides the same error with the program name changed to npm.exe.

I wonder if someone packaged the 64-bit code as a 32-bit install (.msi) and stand-alone program (node.exe).

Looking forward to getting a copy that will run on Windows XP, 32-bit. I can provide testing once an update is available.

[orangemocha]

Ok, the problem is the gyp/project files don't explicitly specify a subsystem version, which results in the default being used. The default changed from VS 2010 to VS 2012 and later. So this means that one of the release machines still has VS 2010. (@misterdjules we should probably fix that or at least try to document it in an asset sheet). nodejs/node@e8d0850 fixes the issue. Opening a PR shortly.

[orangemocha]

Had a chat with @misterdjules and he told me that the release machines have both VS 2010 and 2013. So the change that probably introduced the regression is a58b174, where we select a different toolset version.
Since that change is not in v0.10, the v0.10 release still works on XP. I will cherry pick #25367 into v0.10 later.

[misterdjules]

Fixed by 3122052. This fix will be included in the upcoming v0.12.4 release. Thank you!

[misterdjules]

@orangemocha @deliverymanager @JimHolloman There's a new candidate release with the fix for this issue here: http://nodejs.org/dist/v0.12.4/. Could you please try to install this version on Windows XP and let us know if it solves your problem? Thank you!

[deliverymanager]

Yes I can confirm that in 0.12.4 the bug is resolved.
It is working fine.

[misterdjules]

@deliverymanager Thank you! In the meantime I was also able to setup a Windows XP VM, and I also verified that the new binaries/installers work on XP.

[ghost]

Gentlemen, Though I do run Win 7 for fat apps sing VS 2013, my web work is done in Win XP. Thank you so much for resolving this Win XP issue; it allows many of us to continue using more modern versions of node.

[misterdjules]

@appopen Thank you for the support! 👍

[Dineshkumar2401]

windowsXP32bit install to odoo9 lessc cmd problem to soluction to install lessc plugins using cmd panel ref to url:http://lesscss.org/usage/#developing-less problem all solved.....