New command line file option: <executable>.clx e.g. ashell.clx or ashw32.clx

Similar to the .cl file, the .clx file may be optionally placed along side the ashell executable in order to supply an alternate command line. But unlike the .cl file, which is only used if the original command line does not contain any switches, the .clx is used regardless of the original command line. This is useful in situations where you want to modify the ashell command line for all the users, without having to track down and modify all the individual user startup command or shortcut files.

Also unlike the .cl files whose contents always augment the original command line arguments, the .clx command line may either replace the original command line, or be inserted prior to the original. To get the latter effect, add a " +" to the end of the .clx command line.

For example, if the original command line is:

ashell -i /vm/miame/miame.ini log bas:

and there is an ashell.clx in the same directory as the ashell executable, containing:

-mntsys asr63:=/vm/miame63/dsk0 +

then the new effective command line will be:

ashell -mntsys asr63:=/vm/miame63/dsk0 -i /vm/miame/miame.ini log bas:

If the "+" was removed from the end of the .clx file, then the new effective command line would simply be the executable followed by the contents of the .clx file, i.e.

ashell -mntsys asr63:=/vm/miame63/dsk0