Since launcher is only a 32bit application, if I execute a remote command, it does it in a 32bit session. This is not usually what I want for the 64bit machines, especially if I need to deal with program files, system files, or the registry.
It also won't help me with my existing scripts that check to see which environment I'm running.
please help.
Thanks,
Ben Lipman.
Hey Ben,
We have a synchronization installation script looks something like this:
REM Have to test both of these variables depending on whether the .bat
file is under Wow64 or not.
REM Run it under C:\Windows\System32\Cmd.exe and
C;\Windows\SysWOW64\Cmd.exe to see the difference.
if “%PROCESSOR_ARCHITECTURE%” == “AMD64” goto x64Windows
if “%PROCESSOR_ARCHITEW6432%” == “AMD64” goto x64Windows
============== DO 32 BIT STUFF HERE ==============
goto end
:x64Windows
============== DO 64 BIT STUFF HERE ==============
:end
Not sure if this is something you can use as a template in your case. On
a side note, Deadline 3.0 applications (including the launcher) will be
universal binaries that will run as a 32 bit process or a 64 bit process
depending on the .NET runtime that is detected, which might be of some
help in yoru situation.
Cheers,
I understand how to make a dos script. What I don’t understand is how to make deadline launch a dos script or any process in the 64bit environment. Its important that it be a 64bit environment so the registry, and redirected folders are correct as well as the ability to launch 64bit processes.
Hmm, I’m not sure what can be done in this case, since running both
c:\WINDOWS\system32\cmd.exe and c:\WINDOWS\SysWOW64\cmd.exe through the
launcher runs a 32 bit copy cmd.exe.
However, I just tested this with the Deadline 3.0 launcher (which runs
as a native 64 bit app on 64 bit machines). Running cmd.exe or
c:\WINDOWS\system32\cmd.exe started a 64 bit copy of cmd.exe, and
running c:\WINDOWS\SysWOW64\cmd.exe started a 32 bit copy of cmd.exe. So
at least this process will be straight-forward in the next release of
Deadline.
Cheers,