Comments on: How to Open and Run 32-bit Command Prompt in 64-bit (x64) Windows http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/ Tips and Tricks on Computing, Technology and Gadgets. Sat, 22 Nov 2008 18:03:41 +0000 http://wordpress.org/?v=2.6.3 By: ian sebryk http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/#comment-4558 ian sebryk Thu, 21 Aug 2008 09:42:39 +0000 http://www.tipandtrick.net/?p=1176#comment-4558 i thought that might be a solution, but before i tried it, i tried just running it from a normal shell, instead of through the batchfile that launched the app in question, and it worked fine. so much weirdness. the batchfile no longer works, but direct command line does. how weird is that?! i'll also try a different path without brackets to see if that re-enables my batchfile's ability to launch. reaaaly need the batchfile to work again... :) thank Nicholas. i'll keep you posted. WR! i thought that might be a solution, but before i tried it, i tried just running it from a normal shell, instead of through the batchfile that launched the app in question, and it worked fine. so much weirdness.

the batchfile no longer works, but direct command line does. how weird is that?!

i’ll also try a different path without brackets to see if that re-enables my batchfile’s ability to launch. reaaaly need the batchfile to work again… :)

thank Nicholas. i’ll keep you posted.

WR!

]]> By: Nicholas Dille http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/#comment-4556 Nicholas Dille Thu, 21 Aug 2008 06:34:39 +0000 http://www.tipandtrick.net/?p=1176#comment-4556 I may be dipping the raft but I reckon the TCL interpreter does not allow brackets in the path to a file which it is about to source. Does it help to move the installation directory to a location outside of "c:\Program Files (x86)", e.g. "c:\progs"? Hope that helps, Nicholas. I may be dipping the raft but I reckon the TCL interpreter does not allow brackets in the path to a file which it is about to source.

Does it help to move the installation directory to a location outside of “c:\Program Files (x86)”, e.g. “c:\progs”?

Hope that helps,
Nicholas.

]]> By: ian sebryk http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/#comment-4553 ian sebryk Thu, 21 Aug 2008 03:37:49 +0000 http://www.tipandtrick.net/?p=1176#comment-4553 i tried using your advice to try and get some 32bit apps to run a bit better on my 64bit box. problem is, now i get weird errors from some key software. i don't know how to undo the change... which may serve me right for swimming in deep waters... throw me a raft, ya? here's a sample error that showed up mid-execution after i'd run the %windir%\SysWoW64\cmd.exe command: Error: can't define "ProgramFiles(x86)": name refers to an element in an array while evaluating script: namespace eval :: {source {C:/Program Files (x86)/[directory tree]/RMSExpression.tcl}} i tried using your advice to try and get some 32bit apps to run a bit better on my 64bit box. problem is, now i get weird errors from some key software. i don’t know how to undo the change… which may serve me right for swimming in deep waters…

throw me a raft, ya?

here’s a sample error that showed up mid-execution after i’d run the %windir%\SysWoW64\cmd.exe command:

Error: can’t define “ProgramFiles(x86)”: name refers to an element in an array
while evaluating script: namespace eval :: {source {C:/Program Files (x86)/[directory tree]/RMSExpression.tcl}}

]]> By: Nicholas Dille http://www.tipandtrick.net/2008/how-to-open-and-run-32-bit-command-prompt-in-64-bit-x64-windows/#comment-2963 Nicholas Dille Fri, 23 May 2008 06:29:53 +0000 http://www.tipandtrick.net/?p=1176#comment-2963 As you described in the article, the original %SystemRoot%\System32 is not accessible to 32-bit processes. Unfortunately, there are several tools existing uniquely as 64-bit binaries (e.g. logogg.exe and tsshutdn.exe). In one of my articles, I describe two techniques circumventing the limitation of launching 64-bit system tools from 32-bit processes: http://blogs.sepago.de/nicholas/2008/03/13/jailed-32-bit-processes-on-windows-x64/ Enjoy, Nicholas. As you described in the article, the original %SystemRoot%\System32 is not accessible to 32-bit processes. Unfortunately, there are several tools existing uniquely as 64-bit binaries (e.g. logogg.exe and tsshutdn.exe). In one of my articles, I describe two techniques circumventing the limitation of launching 64-bit system tools from 32-bit processes: http://blogs.sepago.de/nicholas/2008/03/13/jailed-32-bit-processes-on-windows-x64/

Enjoy,
Nicholas.

]]>