Posts: 10,628
Threads: 91
Joined: Aug 2006
Reputation:
181
I tried with Win10 - set file name to "C:\Windows\SysWOW64\cmd.exe" and working folder to "C:\Windows\SysWOW64" - and when I run it I can see in TaskManager that it runs as 32bit application
Regards/Gruss
Oliver
Posts: 5
Threads: 2
Joined: Jan 2016
Reputation:
1
Hi Oliver,
Yes, that makes sense, but I need the 64-bit command prompt to run, not the 32-bit. I've found a work-around. %systemroot%\sysnative\cmd.exe will invoke a 64-bit cmd on a 64-bit Windows, and a 32-bit cmd on a 32-bit windows. If ARD was a native 64-bit application, this would not be needed.
I discovered the "fix" only after typing a full explanation of the problem. If you want to see it, read on ...
If you run a 32-bit cmd.exe and do a directory on the %windir%\system32 folder, you will get a very different listing than if you run a 64-bit cmd.exe. Try it sometime. Windows works its magic behind the scenes, substituting the appropriate folder (system32 vs syswow64) depending on whether the program is 64-bit or not. In my case, I'm running a 64-bit OS, and qwinsta.exe is a 64-bit executable. Here's some output to help demonstrate:
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
U:\>dir c:\windows\system32\qw*.*
Volume in drive C has no label.
Volume Serial Number is 1484-8F1F
Directory of c:\windows\system32
07/13/2009 07:41 PM 242,688 qwave.dll
07/13/2009 07:39 PM 28,672 qwinsta.exe
2 File(s) 271,360 bytes
0 Dir(s) 168,462,430,208 bytes free
U:\>c:\windows\syswow64\cmd
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
U:\>dir c:\windows\system32\qw*.*
Volume in drive C has no label.
Volume Serial Number is 1484-8F1F
Directory of c:\windows\system32
07/13/2009 07:16 PM 210,944 qwave.dll
1 File(s) 210,944 bytes
0 Dir(s) 168,462,430,208 bytes free
U:\>
The command window is initially a 64-bit application, so the directory listing of c:\windows\system32 shows all the 64-bit versions of the files. When I run the c:\windows\syswow64\cmd command, the command windows runs a 32-bit command prompt, so the directory listing of c:\windows\system32 shows only 32-bit versions of the files. Notice how qwave.dll is a different size, and there is no qwinsta.exe since it only exists as a 64-bit application.
I came up with a kludge of copying the 64-bit cmd.exe into an alternate folder and calling that, but then discovered the "sysnative" folder.
Posts: 24
Threads: 4
Joined: Nov 2012
Reputation:
0
I can confirm this issue. I just wanted to create a thread for this, but a search found this one. ;-)
ASG RD is 32-bit and hence it launches a 32-bit cmd.exe, even if the path is set to C:\Windows\System32\cmd.exe.
However, @Bulldogian's workaround using %systemroot%\sysnative\cmd.exe is working for me on a Windows 10 64-bit box.
IMHO, every application should be available as a native 64 bit application nowadays.
Posts: 10,628
Threads: 91
Joined: Aug 2006
Reputation:
181
There are still a lot of apps that do not run in native 64bit mode - we would like to offer this, but we still are using components that are not available for 64bit :-(
Regards/Gruss
Oliver
Posts: 24
Threads: 4
Joined: Nov 2012
Reputation:
0
PuTTY was just released as version 0.68 with a x64 build. One app less that is just available as a 32bit version.