Thanks for your comments, Mark. I have already acknowledged the extreme difficulty of parsing and recoding batch. [Smile] What I'm wondering is how the CMD.EXE is only 236KB and is able to parse so many variations of code. The trick would be to parse the code identically to CMD.EXE and find functions in KIX that mirrored the CMD functionality.... although I doubt I would have the patience to do such a thing. Obviously, the problem is that many CMD functions have no KIXtart equivalent. These particular lines could not be included, however a utility that parsed all lines EXCEPT these may still be useful in some situations.

NET USE --> USE
COPY --> COPY
Mkdir/MD --> MD
NET TIME --> SETTIME
%username% --> @USERID
REGEDIT /S *.REG -->WRITEVALUE, etc ** parsing a .reg file and creating the equivalent script would be easy.. might be a nice UDF..
ATTRIB --> SETFILEATTR
.....

These are just a few of the many conversions that could take place automatically. For the basic logon script that only maps drives and displays a message, this could be very useful, especially for people that are new to KIXtart.

On the other hand, perhaps it would be more worthwhile to simply create a reference chart of CMD functions/commands that map directly to KIXtart functions along with suggested syntax. This could be posted as a FAQ?

The command line you posted creates a file cacls.txt that lists the permissions of all the folders on the current drive.

Brian