SLEEP 30

Quote:

---

By default, to prevent users from inadvertently interrupting a script, KiXtart automatically disables the ctrl+c/break keys, disables 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, you cannot fully prevent users from interrupting a program. (They can end programs by using the Task List, for example.) As an additional protection, on computers running Windows NT or Windows 2000 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 means that you must be careful when testing scripts.

Tip> On Windows 9X, the Please wait while your logon script executes message box contains a Cancel button, which you can hide by opening a copy of Msnet32.dll in Visual C 4.00 WorkBench, selecting the LMWINSCRIPTDLG resource, and making the Cancel button invisible.

---

Quote:

---

As an additional protection, on computers running Windows NT or Windows 2000 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.

---

I figured it might be something like that, but I do not have the manual memorized. Thanks for the quote!

Is there a way to turn this off globally (i.e. disable this feature for all scripts) - perhaps with an entry in the registry or in an .INI file - or must one put the BREAK ON statement in every single script in order to prevent this (to me, highly undesirable) behaviour?

-- Jeff
-- aka The Eternal Newbie

Quote:

---

I do not understand why this is undesirable?

---

I thought I had already explained that.

I don't care if users close the window manually. Even if they get to a command prompt, there's nothing they can do there that concerns me.

I don't need this "security" feature. To me, all it does is cause problems by logging users off when I don't want it to do so. I don't ever want a user logged off except under my direct control, which is something I don't have in this situation.

I would like some way to disable it globally, as it has no redeeming quality for me in any situation I can imagine.

-- Jeff
-- aka The Eternal Newbie

Quote:

---

You still have not explained why you are unable to use BREAK ON in a script. Also, you've been told that using WKIX32 would also solve the problem as you then don't even have a console window (with a properly written script).

---

I never said I was unable to do so, merely that I find it to be an inconvenience to have to remember to do so every time I write a new script.

Plus, I have said that I would try wkix32 as an alternative.

What else do you want from me?

-- Jeff
-- aka The Eternal Newbie