> First, a START does not seem to be necessary here for some reason if the
> program is GUI, but it is necessary if it's CONSOLE. It is not clear to me
> why this is. For example, coding this same BC2.EXE program in the F9-menu
> equires a START to open another task, but in CO-1F it does not.

> Kim, can you shed some light on this?
F9 causes a .BAT to be built and run for the current sript, which is why a START is required to spawn a new process.
For CO-1A/F, a listed .EXE is executed directly with the CreateProcess() API, which returns immediately when running a GUI app.

> Second, coding the (unnecessary) START in CO-1F also starts BC2.EXE in
> it's own task, but the parameters, (whether coded on the line or left
> blank), are not passed to the program. This is either a bug, or needs
> better clarification in Help. (Or both). ;-)
It's a bug, just fixed.

> Note, Matthias, that you do not need to specify %4 %5, since these will be
> the defaults if left blank. (See last paragraph of section 3.9).
Or the three lines above the CO-1E/F input field:
---------------------------------------------------------------------------
Enter full path\file name of compare program (Blank = TFC.BAT).
For an .EXE, TFC parameters %4 %5 passed by default, (add [SFN] for %2 %3).
For a .BAT or .CMD, use none. (Use them inside the .BAT or .CMD file).
----------------------------------------------------------------------------

Kim