|
|
|||||||
Hi, My script is running fine, the box 'please wait while you logon script excecutes' will not go away after the DOS type box has finished, i've added the QUIT command to the bottom of the script but that doesnt work either, any ideas? Thanks! |
||||||||
|
|
|||||||
Dear, Welcome to the board. Which kixtart version you are running? ------------------ |
||||||||
|
|
|||||||
Add a Cookie1 before the exit command, and i'll guess that the problem is gone ! Cheers, rogier |
||||||||
|
|
|||||||
I'm using kix95.363, i have the same problem on both Win95 & 98 (inc. SE). I tried adding the COOKIE1 line at the end of the script and it actually stops the script from exiting at all, so I'm left with the DOS type box up, which i think if a step back? Would it be an idea for me to post my script up here? break off ;SOME USER INFORMATION ;run "\\aglnt01\auditing\Agent32.exe -P \\aglnt01\auditing\auditor.prf" CLS ? "PLEASE WAIT, DO NOT TOUCH THE KEYBOARD OR MOUSE!" use u: \\Droicon1\USERS\@userid ? BIG CLS ;USER SPECIFIC COMMANDS IF @USERID = "TEMPUSER" IF @USERID = "RW" IF @USERID = "pjk" IF @USERID = "DJB" IF @USERID = "JC" IF @USERID = "GL" ;GROUP SPECIFIC COMMANDS IF INGROUP ("DOMAIN ADMINS") IF INGROUP ("DOMAIN USERS") ;DROICON IF INGROUP ("DROICON") IF INGROUP ("DCCPURCASING") ;DIAL-A-UNIT IF INGROUP ("Dial-A-Unit") IF INGROUP ("PRODUCTION") ;GAMMA IF INGROUP ("GAMMA") ;ADROIT IF INGROUP ("ADROIT") IF INGROUP ("ACCOUNTS") ? |
||||||||
|
|
|||||||
I have a suggestion... Instead of putting COOKIE1 at the end of your code, put the word EXIT. Yes, it's simple... but it should work for you. ------------------ |
||||||||
|
|
|||||||
Dear, We look at your code and we have some suggestions:
Please put the result of c:\kixtart.log on the board, when you have still problems. Greetings.
[This message has been edited by MCA (edited 21 June 2001).] |
||||||||
|
|
|||||||
I dont think the debugging will tell you much because the script box disapears after the script is finished, i'm left with a "Windows NT Logon Script" dialog box with the message: "Please wait while your logon script excecutes." and a cancel button. - 1-10:26:12- - 16-10:26:12- - 21-10:26:12- - 23-10:26:13- - 26-10:26:13- - 28-10:26:13- - 30-10:26:13- - 35-10:26:13- - 149-10:26:14- - 150-10:26:14-
Any ideas, your help so far has really been appreciated. Kind Regards, |
||||||||
|
|
|||||||
Try to put Exit at the bottom of the script. |
||||||||
|
|
|||||||
That's what i also was telling: script bla bla and then add Cookie1 That should do it ! Greets, |
||||||||
|
|
|||||||
Dear, Another possibility is the way you are calling the script in your usermanager. code: But possible you need another file (= LOGON.PIF), which will close that box. Why? During some tracing of "what activities of registry are there" and "which code:
What was the differences between both: the DOS box was started by a PIF file with the option Close on exit active. What did we do: we try to change the properties of the file CLEANUP.BAT After running the BAT file by our windows explorer the commands were Our advise is: try to create also a PIF file from your BAT file with Greetings.
[This message has been edited by MCA (edited 22 June 2001).] |
||||||||
|
|
|||||||
I'm having what may be a similar problem. I've got a script that runs flawlessly in most cases. The script won't exit on some machines some of the time. I have narrowed it down to the following consistencies: slow machines (hardware or software-induced) login AS SOON AS POSSIBLE Under these conditions, it is more than common that the script will not exit properlly after execution. In my case, the script has finished completely. There are no errors because the script completed. It's as if the console called forgot that it was going to be exiting after KIX32 was run. If a user experiencing the problem logs off and back on again, they will not experience the problem. BREAK ON will not allow the user to close the window either. I think this could be a login script execution process thing. NT may be blocking the ability to do this. As a result, you have to END TASK on the script to lose the window. I've also seen that the desktop loads prematurely in most (if not all) instances where the script hangs. Generally, I expect the script to have to run prior to being given a desktop. This may not be applicable in Win9x environments. There is a registry setting that can be changed on clients that this is happening, but I haven't seen 100% success from this either. If I find that KiX 4.11 fixes the issue, I'll post a follow-up. |
||||||||
|
|
|||||||
I've seen this behavior only under Windows 9x and my solution is to put an EXIT 0 at the end of my script and a CLS EXIT at the end of my batch file. |
||||||||
|
|
|||||||
I seem to remember this issue being brought up in the Savill FAQ & the NT Reghack FAQ. I thought they suggested it was related to what directory the script started up in. |
||||||||
|
|
|||||||
Dear Olaf, Welcome to the board. Is your problem solved? greetings. |