Quote:

Does kix32.exe have to be in the same directory as the encrypted script in order for it to run



No, but if you don't specify where it is then it needs to be on the clients PATH somewhere.

When I said execute it in a command console, I meant the encrypted script (kixtest2.scr in your case) - not the encryption process.

If it is beeping at you then there definately errors. The only time that KiXcrypt will beep is when attempting to install a Control-C handler at run time. If this fails it will beep, but continue to execute.

Leave the "-o" option out for the moment. Just create the executable with "kixcrypt -d myscript.scr". This will automatically create a "myscript.exe" and display some debugging information.

When you run the exe, it will display more debugging information - this can be very useful in determining what the problem is.