Hi Joel. Thanks for the quick reply.
Of course: I'm using an ASUS N61-VNA2 laptop with the following specs:
- Intel Core2Quad Q9000 CPU @ 2.0GHz
- 4GB DDR3 RAM
- Windows 7 Professional, Build 7600, fully updated
This is how I finally figured out what the situation was:
I found two different versions of the windows command prompt (CMD.exe) on the computer; a 32-bit and a 64-bit version. The 32-bit version is located at C:\Windows\SysWOW64, and the 64-bit version is located at C:\Windows\System32. If I open the CMD.exe from SysWOW64 and check Task Manager, it appears in the process list as "cmd.exe *32" whereas if I open the one from System32, it shows as simply "cmd.exe," supporting this fact.
Now, if I open a 64-bit prompt and navigate to C:\Program Files\Eraser and run eraserl.exe, it works like a charm. I have batch files that use it, no problem. But if I open a 32-bit prompt, navigate to C:\Program Files\Eraser, and try running eraserl.exe, I get the error:
Code:
'eraserl.exe' is not recognized as an internal or external command,
operable program or batch file.
Specifically, what I'm trying to do involves several concurrent batch files. They do various things, and each one opens the next one, then closes. At one step in this process, a program is launched that takes over for a while. When it's finished, it launches the next batch file. It's all fine and well up to that point, because it's a 32-bit program, and therefore launches a 32-bit CMD prompt for the batch file to run in.
I've tried a couple of things, like having that batch file navigate straight to C:\WINDOWS\System32 and running CMD from there, and running it from there using the "start" function, but no matter what I try, the "child" CMD environment is always 32-bit when launched from another 32-bit environment.
Hah that was pretty detailed... let me know if you need any more info. Thank you
