First, I would like to thank all of you for your enthusiastic help.
Second, I can add more info on the problem.

I took the whole thing home and tried it on MY domain that does not have a LOGON share. -- It still fails when LOGON is used and works when LOGN is used, neither of which exist on my domain.

Third, I do not believe that shares or rights have any thing at all to do with the encryption phase of the program. As I surmise, this program is just embedding a call to \\PATH\KIX32.EXE with a passed parameter of the name of the .KIX script and then encrypting the whole thing into one .EXE. None of this packaging should need to validate any paths, only the .KIX script existence.

So, the question that remains is what is special about the word LOGON.

Richard wrote KixCrypt and is probably the only one that can answer why LOGON is triggering it.

BTW, have any of you tried to reproduce the exact same error with a dummy script using the same calls?

That would confirm the problem as I have done at home.

Thanks
Stephen

[ 07. December 2002, 02:23: Message edited by: ElegantSol ]
_________________________
Stephen If the solution to the problem be concise and artfully or ingeniously contrived yet simple and handsome in effect, then the solution merits the adjective elegant. -- K.G. Wilson