Ok, well after a week of brain-racking and a few megs worth of KiXtart trace files send back and forth, we have some positive results:

No, it had nothing to do with funky quotes, scripts size, quantity of UDFs, etc.

The problem, as weird as it still remains, can be attributed to one line of code -- a line which has been in my script since 1998.

Try this for yourself (from a machine you don't mind hanging):

code:
$rc=box(0,0,10,10,GRID)
$rc=box(6,9,20,71,Å) ; the special char is produced by ALT+143
$rc=messagebox('Hello World','Testing',4112,0)
exit 0
Mind you: This works without problem with KiX 4.02, and will work with 4.10 if you create a shortcut such as "e:\test\wkix32.exe" "\temp\testscript.kix" and then use it to launch the 4 lines of code above.

What Ruud and I have been working on, is that the failure is caused by changing the script argument to include a drive letter such as "e:\test\wkix32.exe" "e:\temp\testscript.kix"

I don't know exactly why, and Ruud is leaving town for a few days, so we'll have to wait for his explanation upon his return...

But the interim solution is to wrap the special character used to generate the box in quotes. This, (according to the manual) is the way it should have been done, but since I never ran into a problem before, it was never looked at...

$rc=box(6,9,20,71,"Å")
; Wrapped in quotes, the script filespec with a drive letter now works.

So, while there is still a mystery as to why a change in the command line argument triggers the failure, at least I have a solution.

Of course, this may be the tip of the iceberg and other things may be effected, so hopefully finding this one problem will prevent others [Smile]

-Brian