C#@> I had tried a few times and found it workable, though a few
 C#@> changes in the BAT were perhaps needed to accomodate the program which
 C#@> seemed to consider certain calls as errors. With the speed of most
 C#@> systems today, and the desire to go and meddle with the file contents
 C#@> often, I happened to find no reason to go on using it.

I see only one good use for it. If a computer has to be shared with
family or co-workers, compiling batch files should help reduce the
likelihood of unwonted batch file changes. :-)

I use XED which integrates up to 64K of COM files into one unit to
reduce the number of disk clusters they take up on a disk. I though
I could use XED with batch files also by compiling them to com files.
No dice. A couple of them did strange things. It appeared that lines
in one compiled batch would interact with lines in compiled batches
of other batch files!





___ Blue Wave/QWK v2.12