Thanks for your input, everyone.

I started working on it a little bit, and it appears that the hardest part would be supporting ALL the functions that can be handled in batch. There are a lot of functions that either have no direct support in KIX, or are stripped down with only the most COMMON features.

Theoretically (and maybe not too hard to code, either), you can read in each line and parse it, then figure out inputs, operations, outputs, and branch instructions then save this to a file. After all the lines have been processed, an algorithm can be written that matches all the inputs, outputs, and branches of each line in such a way to make tighter code.. BUT... how do you deal with functions that have no direct support in KIXtart?

Things like net user, or net time (to parse for the time on a remote server, not set it), or subst are not supported in KIXtart.

Converting the lines that can be converted directly may be useful, but each line that cannot be converted directly would have to be hand coded anyway, and may not be doable by kix internally.

I'm not totally ready to abandon the idea, but working on it and watching this bulletin board has given me another idea to work on that may be both easier to implement and more useful in the long run -- a script debugging engine.

(I'll start a new thread.. thanks again for the input.)

Brian