There are times when one may want to execute an external program from the logon script. The desire being that the previously mentioned external program RUNs independently from the KiXtart logon script process. Well we know that SHELL is not the what we want, but RUN seems like the ticket. So...RUN is used to launch SMSLS.BAT.
What I have experienced with 4.02 on W2K is:
Shell work great but the logon script can be delayed during the execution of the SMSLS.BAT and related code as expected.
When RUN is used the KiXtart logon script console, sometimes remains after the logon script finishes. The logfile records that the KiXtart script code ends and the last line of the batch file used to call the Kix code executes. When this happens the window can not be closed of course.
So I added some additional code that I expected would better isolate the executing external program: Run | Shell '%comspec% /c Start ... SMSLS.BAT'. In both cases, the START command will leave a new console window open after SMSLS finishes. No big deal I thought. We can add an EXIT to the SMSLS.BAT file. But what really concerned me was that when SMSLS took a while to execute the LOGON script window remained until the DOS prompt appeared in the SMSLS window thus holding up the loading of the desktop.
That would seem to indicate that any program executed from the logon script has to complete before KiXtart or the "LOGON" session can terminate.
If that is the case, is there any REAL value to using RUN?
Does anyone know a way to truly spawn an independent process from the logon script other than using the RUNONCE key?
Is this KiXtart or the RunLogonScriptSync value that is the true culprit?
