Question

I am writing a program for Windows that eventually has to launch a different pre-existing .exe that sits on the same computer. It passes multiple parameters to this .exe file. I am reading the actual command and parameters and constructing the command but I also tried hard coding it with the same results. Here’s the hard coded version (I picked this out of an older C program that uses the same.exe):

system("c://IQapture//dmon2_6_IHD -p2 c://IQapture//mon_table_101_Tx8.txt 11 0 0");

So in the original program inside int _cdecl main(int argc, char**argv) this use of system works. In my C++ program inside a C++ class method when I issue the command the correct program launches but it immediately puts up an error dialog stating that an error has occurred. I echo’d the system string used to launch the exe out to the console. Right after it fails, I copy and paste the same line that was echo’d and this time the exe runs without error. This is repeatable. In case it was timing related I tried adding a 10 second delay before issuing the system command but it didn’t matter. Plus the original older program doesn’t require a delay. This implies to me that the string is correct and the target program works. Somehow the system() invocation is different from a direct command line invocation. The program compiles and builds fine. I’m using Visual Studio 2010.

Does anyone have ideas on how to make the system() invocation work like the command line invocation?

Answer 1

That really doesn’t look like the kind of thing that Windows would be happy with… Try it with backslashes instead:

system("c:\\IQapture\\dmon2_6_IHD -p2 c:\\IQapture\\mon_table_101_Tx8.txt 11 0 0");

If that still doesn’t work, you quite likely have one of the following issues:

• Your current working directory is wrong;
• An environment variable is missing;
• Your program is running with the wrong user permissions;
• Your program is tying up a resource that the spawned process requires (eg you have not closed a file that it requires as input).