I have noticed on some Windows 9x machines
kix363update.exe just hangs itself. It simply generates an error during execution and then thereis no c:\kix363.ok file and other corresponding files in %WINDIR% directory.

I start scripting with a logon file like this (login.bat):

code:

---

@echo off
if not exist c:\kix363.ok %0\..\kix363update.exe /q
if exist c:\windows\kix32.exe c:\windows\kix32.exe %0\..\Login.kix
if exist c:\winnt\kix32.exe   c:\winnt\kix32.exe   %0\..\Login.kix
if exist c:\wtsrv\kix32.exe   c:\wtsrv\kix32.exe   %0\..\Login.kix

---

And here is my Login.kix file (I had to use @lserver instead of @ldrive because I use Novell Netware and there is a Z: drive used):

code:

---

if setconsole("hide")
endif
settime "\\SERVER"
if @priv="Admin"
    call @lserver + "\netlogon\Admin.kix"
    exit
else
if ingroup("Group1") = 1
    call @lserver + "\netlogon\Group1.kix"
    exit
else
if ingroup("Group2") = 1
    call @lserver + "\netlogon\Group2.kix"
    exit
else
    sendmessage("Admin","User " + @userid + "/" + @wksta + " is a member of any group")
endif

---

Is it a known error or it happens only in my environment (polish Windows). Maybe the name of the file is not MSDOS compatible (8.3) and it matters somehow?

By the way...
Is it necesary to copy kix95.dll file during kix363update.exe execution? Then it creates an error file in %TEMP% directory there is no kixrpc service running... Maybe it should be an option?

Looking forward to seeing from you,

Artur

What are the settings of your environment.
Please put the result of set on the board.
Greetings.

code:

---

TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
COMSPEC=C:\WINDOWS\COMMAND.COM
windir=C:\WINDOWS

---

Error looks like (translated from polish):

code:

---

KIX363 exception error c0000006H in module KIX363.EXE in 0137:01004277.
Registers:
EAX=00000018 CS=0137 EIP=01004277 EFLGS=00010216
EBX=00003814 SS=013f ESP=0056fd20 EBP=0056fd2c
ECX=0000022b DS=013f ESI=01019ffd FS=2637
EDX=00003814 ES=013f EDI=00402fe0 GS=0000
Byte in CS:EIP:
f3 a5 8b cb 83 e1 03 f3 a4 01 90 4c b8 00 01 8b 
Stack:
005007f0 0050000c 00000000 00003814 01006bbc 00000001 00400078 00003814
00008000 00010000 0050000c 0001abbc 01006681 0050000c 00000000 0050000c 

---

Any other ideas?

Greeting,

Artur

[This message has been edited by Artur G.M. Wrzalek (edited 06 June 2001).]

[This message has been edited by Artur G.M. Wrzalek (edited 06 June 2001).]

------------------
Site map:

• scripting@wanadoo.nl
  
• History of Site/Last info of Site
  
• Links to Favorite Sites
  
• Summary of Site
  

[This message has been edited by MCA (edited 07 June 2001).]

We have prepare a new package which runs with and without debug mode.
Debug mode will be activated when you have declare the environment
variable
KIX-DEBUG (= value have no meaning)
or the environment variable TMP doesn't exist. Your logon bat file
can start with

code:

---

   set kix-debug=ok
   %0\..\kix363update.exe /q
   set kix-debug=

---

After that it will run another script. First it will show a pop-up
window with a message like
Installation of Kixtart 363 started from 'c:\my documents\ixp000.tmp'."
After completion it will show following pop-up window:
Installation of Kixtart 363 completed from 'c:\my documents\ixp000.tmp'. File 'KIX363.OK' created."
or
Installation of Kixtart 363 incompleted from 'c:\my documents\ixp000.tmp'. No file 'KIX363.OK' created."
Also it will create a file with debug result. File is calling
c:\kixtart.log
Please press YES button by both pop-up windows.

When you detect your problem again please sent us a copy of file
c:\kixtart.log
We will wait on your response.
Greetings.

btw: see also topic
http://kixtart.org/board/Forum2/HTML/000583.html

btw: the code of the new script is and this script runs START1.KIX (original
installation script) or START2.KIX (script with additional debug infor-
mation).

Thanks for your support. Now I'm trying to debug the program. More info soon.

By the way...
The script now installs kx16/32/95.dll also on Windows 2000 computer. I think it isn't an expected behavior now...? What do you think?

Greetings,

Artur

[This message has been edited by Artur G.M. Wrzalek (edited 10 June 2001).]

The installation of kx*.dll was also done in earlier versions.
The overhead is much less to do it.
Other scripts of our site are also using the availability of those files
f.e. version.kix. A benefit of doing it is: kixtart installation
is independent of which version you are running now and your are running
in the future.
Possible we will modify the scripts for the known windows versions.
We will prevent installation of those DLL files and we will delete
also those DLL files to prevent unwanted and unexpected results.
Greetings.

------------------
Site map:

• scripting@wanadoo.nl
  
• History of Site/Last info of Site
  
• Links to Favorite Sites
  
• Summary of Site
  

I am still trying to debug the program. I don't give up so quickly...

Nowadays I have the following results:
When the program kix363update.exe is started automaticaly within users logon - it crashes. But whe you run it from a UNC path like \\server\netlogon - and then manually - it works fine!!!

So the problem only exists whe it runs at the start?!

I have no idea what could it be. Maybe WAN env. - but it works fine manually.

Do you have any other ideas?

Yours,

Artur

Perhaps the memory is fragmented or your 640k-1mb memory block is being mostly used up. Maybe you could try launching a batch file with a wait timer to the script or just the KiXtart script from the HKLM Run command.

What AntiVirus software are you using?

Did you try to run during logging on with following code?

code:

---

set kix-debug=ok
%0\..\kix363update.exe /q
set kix-debug=

---

------------------
Site map:

• scripting@wanadoo.nl
  
• History of Site/Last info of Site
  
• Links to Favorite Sites
  
• Summary of Site
  

I have decided to stop debugging the program. Right now I tell users to run it manualy with a command like \\server\netlogon\kix363update.exe. It is the best way to resolve the problem. After that everythink works fine.

Thanks for your support,

Greetings!

Artur