I'm glad you managed to resolve the problem yourself, I've added this reply as an explanation in case some one else has a similar problem and locates this thread.

The problem is most likely caused by having different versions of KiXtart installed.

When you execute the encrypted code it will find the version of kix32.exe in one of two ways. If you are using the secure features and have the "\" character specified in the KiXtart executable path then only that executable path will be used to run the script. This is to avoid a trojan exploit where somone renames their local "notepad" as kix32.exe.

If you don't use the secure features then the PATH environment variable is used to locate the kix32.exe executable, and the first one found is used.

It is likely then that there was an old version of KiXtart in a directory near the start of your PATH which didn't support the @SCRIPTx macros. You didn't have a problem when you tested your script because you called the newer version explicitly.

[ 31. October 2002, 10:42: Message edited by: Richard Howarth ]