The following is the response to a private email I received asking about running a KiXcrypt'ed executable from a NETLOGON share and using the Kix32.exe which is also resident on the share.

As the solution may apply to others I've posted it here.

It might be useful to append it to the KiXcrypt topic in the FAQ forum.

quote:
Hi Gary,

Nice to hear from someone using KiXcrypt in the real world.

"I am trying to use a KiXcrypted KiXtart script in a login script, without KIX32 being installed locally (just located in the Windows NT Servers NETLOGON share)."

Hmm. Tricky one.

Ok, the KiXcrypt program uses the "%" character as a metacharacter. In fact the string is passed to a "C" printf to generate the command string.
You can see the results if you use the "-d" debug option to make the encrypted file and then run crypted.exe.

The simplest solution is to double up the "%" - you will then have to double up again to defeat the printf proccessing. Your encryption line will now look like this:
kixcrypt.exe script.kix "%%%%0\..\kix32.exe %s"

When I run this through with the debug option the command line it displays is:
DEBUG: Executing C:\WINDOWS\COMMAND.COM /C %0\..\kix32.exe VJYMKHUW.kix

Which I think is what you are looking for.