We are seeing some random issues with Windows 95 clients where the kix32 command does not even run and it aborts our login script prematurely. Looking at the Task List, kix32 and winoldap are usually all that are listed. If you end kix32 and then select Cancel on the Running your login script box, the machine will boot fine.

Our process is as follows:
Each user runs LOGIN.BAT for their login script
LOGIN.BAT among other things does the following:
1. puts the latest version of the kix files on the PC
2. calls kix32 from the local PC and calls our kixtart script (which right now is about 19kb, we have two others that are 25 and 52kb respectively)
The call is %windir%\kix32.exe %0\..\GROUPS.SCR

The next executable line after this call is a pause statement. In about 50% of the time when I login, I do not get to this pause statement. I also have a messagebox statement as the first line of the GROUPS.SCR script and that does not get executed.

Your thoughts would be most appreciated.

Thanks,

Tom Gibson, MCSE
Senior Systems Engineer
Federal Way, WA

Continuing further debugging...

Thanks

Tom Gibson

Bryce

------------------
kix.isorg.net

I think I may have narrowed it down to the use of EXIT in the script. It would appear the functionality under 3.63 on Win95 PCs has changed.

Thanks,
Tom

Your goal is to run groups.scr in a correct way. For this purposal we
advice you to do the following things.
1. download kix363update.exe from our site http://home.wanadoo.nl/scripting
this program will install kixtart at your local workstation and creates information
about the update process in file c:\kix363.ok
2. change your login.bat to:

code:

---

     %0\..\kix363update.exe /q
     if c:\winnt\kix32.exe   c:\winnt\kix32.exe   %0\..\group.scr
     if c:\windows\kix32.exe c:\windows\kix32.exe %0\..\group.scr
   

---

Greetings.

btw: see also kixtart topic http://kixtart.org/board/Forum1/HTML/001920.html
for more information of usage of kix363update.exe