Please provide example of how script called from User profile and the line in the batch file calling the KiX script.

Finally, also recommend moving to V3.63 from 3.54 - more stable, more useful, and most posts on this board are users using this version.

Bill

@echo off
%0\..\kix32.exe

Here is a portion of the kixtart.kix file:

cls

IF INGROUP("Illinois") = 1
use f: "\\troyer2\@userid$"
use i: "\\troyer2\programs"
; use j: "\\troyer2\msj"
use k: "\\troyer2\data"
use l: "\\troyer2\ustatj"
use n: "\\troyer1\netapps"
use p: "\\troyer1\standard"
use q: "\\troyer1\projects"
use r: "\\troyer2\projects"
use s: "\\troyer1\sec"
use t: "\\troyer2\QTemp"
use u: "\\troyer2\users"
use w: "\\troyer4\archives"

In WXP, user profile, the entry in logon script is: logon.bat
Should there also be an entry for the profile path, and if so, what?
I will also install the newer version.

I understand you are currently using: %0\..\kix32.exe <script name>
which is proper for Win9x/NT/2K.

However, XP apparently can not properly evaluate this '%0\..\' naming process, which is a method to tell the Windows O/S to use the current directory.

A check of MS Tech site yields no specific solution on proper syntax for calling a login script for WinXP. So, you will need to perform some tests to find proper syntax.

This snippet of script, when used in your BATCH file calling the KiX script, can determine systems that are Windows XP. I understand when running 'ver' at a command prompt XP returns '...5.10.xxxx' (Win2K returns '...5.00.xxxx', and NT 4 returns '...4.0').

code:

---

FOR /f "delims=0,n skip=1 tokens=4" %%i in ('ver') do (  IF "%%i" == " 5.1" (
  <run XP-specific start command here>
  ) ELSE (
  %0\..\kix32.exe <script name>
  ))

---

As for proper syntax to start the script - I recommend a few tests to find proper result:
1. In batch file, try variations for calling the KiX script such as:
a. kix32 <script name>
b. start kix32.exe <script name>
2. In Users profile, try: kix32 <script name>

Likely you will need to try others to get the solution, but hopefully this gets you started in the right direction.

These two MS Tech docs may help you -
Q258286
(http://support.microsoft.com/support/ kb/articles/Q258/2/86.ASP?LN=EN-US&SD=tech&FR=0&qry=logon&rnk=21&src=DHCS_MSPSS_tech_SRCH&SPR=WINXP)
and Q265016 (http://support.microsoft.com/support/ kb/articles/Q265/0/16.ASP?LN=EN-US&SD=tech&FR=0&qry=logon&rnk=24&src=DHCS_MSPSS_tech_SRCH&SPR=WINXP)

Lastly - when you do find the proper solution - please post back for all on this board to share.

Bill

[ 05 November 2001: Message edited by: bleonard ]

But i don't have a XP system to test on

NTDOC - any light you can shed on this problem?

Bill

Welcome to the board.

We see in this topic and also in other topics about kixtart and Windows XP
that the logon procedure contains something like

%0\..\kix32

without the specification of filename of your kixtart script.
Very general call can be

%0\..\kix32 %0\..\your_script.kix

The benefits of specifying your script filename is:

• you are executing the wanted script.
  
• the kix32 program doesn't need to search for a script with the possible
  names
  @userid.kix,
  @userid.scr,
  kixtart.kix
  and
  kixtart.scr
  which means kix32 starts much faster the execution of your script.
  
• it is much clear what script will be executed.
  

%0\..\KIX32.EXE KICK.SCR
EXIT

Kick.scr calls something.kix depending on group membership.
It works ok, even on dialup. We only have 2 machines running the new OS. One is a Celeron 766 with 64MB and the other is a 1.4GHz Pentium with 128MB.
I've not had to do anything different to make it the scripts work for XP. I can enclose more scripts if necessary. I'd like to get to the bottom of this. Sounds a bit flaky to me, so we might have problems soon.

Clients:
Windows 95/95a/95b/95c/98/98se/ME/NT (SP 1- 7 Rollup)/2000 (SP 0-2)/XP Beta/XP

We use the following:

%0\..\kix32.exe logon.kix

This works on all clients including XP

There appears to be only a few variants.

%0\..\kix32.exe logon.kix
or
%0\..\kix32.exe %0\..\logon.kix
or
%0\..\kix32.exe \\myserver\myshare\logon.kix
or
%windir%\Kix32.exe %0\..\logon.kix
or
C:\KIX\Kix32.exe %0\..\logon.kix

However, since there are many ways to alter default settings or impose other security roadblocks I would think it is fair to say that no single answer on this method is guaranteed to work for everyone.

If you are having problems please try launching via one of the above methods and it should work for you.

XP is not the problem as far as I can tell, it is a path issue.

The following code can be used to find the current release version of Windows XP from a batch file. This may need to be altered for other non English languages and/or when XP is updated.

NOTE:
The line to check for Windows 9x must be first otherwise you'll get an error because Windows 9x does not understand the FOR command as used here.

code:

---

@ECHO OFF
IF NOT "%OS%" == "Windows_NT"  GOTO WIN9X
for /f "Tokens=*" %%i in ('ver') do (  IF "%%i" == "Microsoft Windows XP [Version 5.1.2600]" GOTO XP)
IF not "%ALLUSERSPROFILE%" == "" GOTO WIN2K
IF "%OS%" == "Windows_NT"      GOTO NT4
GOTO END
:XP
ECHO Found Windows XP
REM Or what ever command you want to run.
GOTO END
:WIN2K
ECHO Found Windows 2000
REM Or what ever command you want to run.
GOTO END
:NT4
ECHO Found Windows NT 4
REM Or what ever command you want to run.
GOTO END
:WIN9X
ECHO Found Windows 9x
REM Or what ever command you want to run.
GOTO END
:END

---

Hope This Helps -

We did a short analyze what is going on with a kix32.exe call.

• kix32.exe
  means
  - first try to find a script kixtart.scr in your working directory,
  which doesn't mean "it is your NETLOGON directory".
  - secondly it will try to find a script kixtart.kix also in your
  working directory.

  conclusion: it only search for a script in your working directory. first with the
  .scr extension and later with the .kix extension.

• kix32 x:\scripts\your_script

  it will search first for the script your_script.scr and secondly for
  the script your_script.kix in the directory x:\scripts.

• kix32 x:\scripts\our_secure_script.txt

  it will not search for a file, but try to execute specified file. the extension
  of it isn't important. the contents must only be kixtart code.
  

please change your logon.bat file to

code:

---

@echo off
 dir /b >>c:\kix-info.log
 %0\..\kix32
@echo off

---

greetings.

we've made it work.
THANK YOU ALL for your excellent help and tips.