From my experience, the default behavior of Kixtart 4.02 is that one can not interrupt the script with Ctrl-Break or Ctrl-C. On some OS's like NT and higher one can terminate a process. when this happens, KiXtart forces a logoff on NT, W2K, and XP. Not sure about Win9x.
From the manual:
quote:
By default, to prevent users from inadvertently interrupting a script, KiXtart automatically disables the CTRL+C/BREAK keys, removes the Close command in the System menu of the current command-prompt window, and hides the Please wait while your logon script executes message box on Windows 9x.
In a multi-tasking environment such as Windows NT, users cannot be fully prevented from interrupting a program. (Programs can be stopped by using the Task List, for example.) As an additional protection, on computers running Windows NT Workstation only, when BREAK is OFF (the default) KiXtart also installs a special event handler for the current console. The effect of this handler is that whenever a user forcibly terminates KiXtart, the user is automatically logged off. This also means that you must be careful when testing scripts.
