1.

Solve : REG ADD Batch?

Answer»

Quote from: nothlit on October 27, 2010, 06:37:17 PM

If left as CMD it goes to what I would consider the normal global run without the Wow6432Node.

Would anyone know why?

Is it because the converter is 32bit and the OS is 64bit? Just trying to make sense of it. Thanks.

You do know there are two cmd.exe versions PRESENT in 64 BIT Windows? One 64 bit and one 32 bit?

64 bit... %windir%\system32\cmd.exe
32 bit... %windir%\SysWoW64\cmd.exe

Below you can see I go from 64 to 32 bit cmd and back again. You can see how to check the version...

Code: [Select]C:\Users\Mike>%windir%\system32\cmd.exe
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mike>echo %programfiles%
C:\Program Files

C:\Users\Mike>%windir%\syswow64\cmd.exe
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mike>echo %programfiles%
C:\Program Files (x86)

C:\Users\Mike>exit

C:\Users\Mike>echo %programfiles%
C:\Program Files
http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/

Thanks for that Salmon TROUT. Good information, I had run across the separation before that windows had the two environments but during this whole THING I really didn't think about it. Live and learn I suppose.


Discussion

No Comment Found