Process Termination of BC2.exe?

[Guest]

I am using scheduler in combination with scripting to launch BC2.exe at certain times each day. While Windows Scheduler has an option to kill the job after X hours, this only kills the .bat file that started the BC2.exe process. Is there a way to tell the BC2.exe process to not run more than 24 hours and 'overlap' itself on multiple instances of the same job?

Alternatively, can you specify in the script what the BC process should be called? Right now I will have up to 8 BC2.exe processes running at once, so I have no way of knowing which one to kill. If they were uniquely named it would be very easy to just use kill.exe or something to kill the process. (Suppose I could always copy BC2.exe to BC3.exe, BC4.exe, etc)

[Chris]

Re: Process Termination of BC2.exe?

You can set only one instance of BC in the Startup section of Tools|Options. Just uncheck "Allow multiple instances of program".

There isn't a way to set a timeout inside of a BC script. It also isn't possible to name the process inside the script.

I'm not sure if it is possible to set the name of the process from a batch file.

Renaming BC2.exe should work though.

Have you tried running the script directly instead of using a batch file to see if the task scheduler timeout can kill it that way?

It might also help to have the script output a verbose log to see what is taking so long for it to run.

[Zoë]

Re: Process Termination of BC2.exe?

The "Allow multiple instances of program" checkbox does not affect scripting.