I'm running Windows 7 64-bit.
I have a .m1s script that uses a 32-bit .ocx to perform serial communications. I have an issue where I get an ActiveX error now that I've upgraded to 64-bit.
Based on the link at bottom, I think Mach is using Windows\system32\wscript.exe (or cscript.exe) to execute macros, but in 64-bit Windows, system32 holds only the 64-bit script interpreters,
which can't use existing 32-bit .ocx or .dll libraries. In other words, my existing scripts might actually work if Mach called the 32-bit script interpreters now located in Windows\WoW64\
Is there a way I can select which interpreter is called to run scripts? If not, could one be added? Has anyone else run into this yet?
This is what I think is happening:
http://stackoverflow.com/questions/2429477/cannot-use-createobject-from-vb-scripts-on-windows-7