I'm surprised that not using a one-line bacth file to launch the KiXtart script is actually worth a couple of hours of writing/testing/debugging another script.

You could always try passing an empty var as a "command-line switch", e.g.
Code:

kix32 script.kix $a $b

However, how would you differentiate between command-line switches intended for the KiXtart executable and command-line swithces intended for the script (which is also passed as a parameter)?
E.g.
Code:

kix32 script.kix /f

kix32 /f script.kix

Does the /f switch apply to the KiXtart executable or the script.kix script? There are ways around this, however, I don't think it's that important as you have ways to provide information from the command-line to the script.

Edited by sealeopard (2004-02-07 04:09 PM)
_________________________
There are two types of vessels, submarines and targets.