Dear,
(earlier published information. thanks NTDOC pointing to that)
Another possibility is the way you are calling the script in your usermanager.
Put f.e. logon.bat in your logonscript field.
The batch file can have the contents:
code:
@echo off
%0\..\kix32.exe %0\..\your_script.kix
exit
@echo off
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
file handling things are going on" we saw that the system is trying to
locate PIF files.
In our case we run the CLEANUP.BAT file without an existing PIF file.
The code is something like this:
code:
@echo off
deltree /y c:\temp\.
exit
@echo off
- we start the BAT file by our windows explorer
Result:
commands were executed normally and the exit statement
in that BAT file wasn't executed. The box remains open. - we start the BAT file from a DOS box by entering CLEANUP.BAT
Result:
commands were executed normally and the exit statement
in that BAT file seems to be executed. The box was closed.
What was the differences between both: the DOS box was started by a PIFfile with the option Close on exit active.
What did we do: we try to change the properties of the file CLEANUP.BAT
and it was possible to set the option Close on exit active. After Apply
and OK a new file was created with the name CLEANUP.PIF.
After running the BAT file by our windows explorer the commands were
executed properly and the box was closed also. File tracing shows us
that the system tries to find the cleanup.pif file after
starting the cleanup.bat file. The PIF file just contains
the Close on exit setting.
Our advise is: try to create also a PIF file from your BAT file with
Close on exit set to active
and
place it in the same directory where your LOGON.BAT is
located.
Greetings.
[ 20 May 2002, 17:07: Message edited by: MCA ]
