Thank you in advance,
Tan

I got this problem since Kix 2001 Beta 1 and it continues on Beta 2, and it's only happen with the console-less version of kix on OS Windows 9x, most on docking station users (it proves, not only me!).

This is the scenario: during log on, username and password entered, the "Please wait while logon script..." dialog appears, dos console box appears with title "Z:\KIX32", then it closes, the "Please wait..." dialog also closes, windows taksbar loaded and an error message appear: "Kix32.exe has perform an illegal operation... bla...bla...".

The kix script that I used work perfectly on Kix 3.63, it's only a small script and I have tested also with a very small, basic, error free of kix script, and it's still with the same error.

Is there somebody notice about this?

Thank you for any comments,
Tan

Note that the consoleless version isn't very useful on Windows 9x unless you use LMSCRIPT emulation, because otherwise you will always have a console anyway. This is caused by the way logonscripts are handled on Windows 9x.

Also note that you may need to launch the batch/executable using START /w, otherwise the calling batch may terminate prematurely, and the connection to the NETLOGON drive may be lost before the script completes.

Kind regards,

Ruud

Look at this one ? It seems the same. Exept I can't test NT4 and 2K.
http://kixtart.org/board/Forum3/HTML/000018.html

------------------
Jos.

--------- Happyness is a working Kix script. ------- :D

i Can confirm this to be a problem.

I also notice the GP-fault using kix32 Beta2 on Win95 systems. Replacing it with kix32c solve's the problem.

I use a fairly large set of scripts. So I haven't been able to locate the offending code.

Eelco

Although it doesn't make a lot of sense, you can also use it from a batchfile, but you must run it using "START /w KIX32.EXE".

The reason for this is that KIX32 is a true Windows application, and as such runs asynchronously. So unless you use LMSCRIPT emulation, or tell the batchfile to wait until KIX32 completes, the logon API will prematurely think KiXtart is finished and rip out the network connection to the NETLOGON share (which in turn will of course cause an exception in KiXtart).

Regards,

Ruud