I've captured a few utilities than can be called from the command line and a couple of batch files that call them.
When the utilities are not ThinApp'd the batch file launces the utility and waits, while the user interacts with the utility and then exits, at which point the batch file continues.
eg. batch file launches notepad++ with a file, user enters some info, saves file, exits and script continues....
When the utilities are Thinapp'd the batch file launches the utility and the utlity launches as expected but the batch file continues immediately and does not wait for the process to exit.
eg. batch file launches thinapp'd notepad++ with a file, but continues running without the user's input...
I am assuming this is because the entry point process which is called is exiting once the process within the thinapp is loaded.
So my question is, is there a way for the initial process to remain active while the thinapp is running?