I used to run AaS 2.0 to activate a Dual-Program running (Call-on-Duty). For instance, I specified the executable file, e.g., pro1.exe written in C language, in AaS. The activated pro1.exe will then call the other executable file, e.g., pro2.exe through the calling of "system("pro2 parameters.dat")" compiled in pro1.exe. Usually, pro2.exe will be displayed in the Task Manager in WinXP.
Now I am having problem in doing the DualProgram running. When I start pro1.exe in AaS, I only see pro1.exe running displayed in the Task Manager in WinXp(SP3) instead. And one of the output files from pro2.exe seems outrageous.
When I activate pro1.exe by clicking the file in the folder manually, pro1 calls pro2 correctly. And the Task Manager diaplays pro2.exe is running. This means pro1 can still call pro2 outside AaS.
So something must be goofy in AaS running under WinXP(SP3). I tried AaS 3.0 and got the same problem.
Any suggestion is appreciated.