I have just instituted the KXRPC service on my BDC and PDC, and tried a login script that will get the home directory for each Win95/98 user from User manager for domains.

ON some Win95/98 machines this works flawlessly,

Others I get a Kix32 exception in Kix32. It happened on a Win95 and a Win98 system, and then 2 others I tried it worked flawlessly.

My question is:

After you install the KXRPC service on the PDC/BDC's, do you have to put the KX16.dll and KX32.dll files in the C:\Windows\System directory for this to work.

I have seen it work without but the 3.6.1 documentation claims it needs kx16.dll and kx95.dll

Anyone?

Please email me if you know....

Sincerely,
Ed Ziots
eziots@lifespan.org

What is the problem for placing all kixtart files at your local workstation. It doesn't cost enormous amount of diskspace.
The most important thing is: your script works.

By using the kix362update.exe from the site http://home.wanadoo.nl/scripting automatically the package will check of all kixtart files are correct installed. when not it will replace them.
After that your problems must be over.
Greetings.

Next problem is, I have 500 users that need to have home directories mapped correctly.

Therefore do I have to run this update locally on each system, and if so, where do I need to add the files to? ( I guess C:\windows\system?) Is there any registry hacks? etc etc?

I have the KX16.dll KX32.dll and KX95.dll in my netlogon share, and I am planning on getting KXRPC service on each and every PDC/BDC in the domain, so do I really need to push down the Files to the user workstations. ( Only if they are Win95/98, NT functionality works fine without the script)

Please advise,

Sincerely,
Ed
eziots@lifespan.org

Check the following portion of my batch file. NT is a breeze with Kix, but 95 has had some issues. I support 500 people also and copying kix down to the c:\windows directory took a LOT of headaches away.

GOTO KIX

REM set the destination directory for KiXtart files
REM for Windows directory use SET KIXDIR=%WINDIR%

:KIX
SET KIXDIR=%windir%
REM The following line points the machine to the server running the Kix RPC service

SET kxrpc=\\servername

REM set the full UNC path to the KiXtart script
REM (the Z: drive cannot be used here, it no longer exists when
REM the KiXtart script is running from RunOnce)

SET KIXSCRIPT=\\SERVERNAME\NETLOGON\KIXTART.KIX

REM set the filename of the KiXtart version tag;
REM change this name to upgrade to a newer version of KiXtart

SET KIXVER=KIX361.TAG

REM ---------------------------------------------------------------------

REM perform a completely new install or upgrade of KiXtart
REM if the current version tag can not be found

IF EXIST %KIXDIR%\%KIXVER% GOTO KIXCOPIED
COPY %0\..\KIX32.EXE %KIXDIR% /Y >NUL
COPY %0\..\KX16.DLL %KIXDIR% /Y >NUL
COPY %0\..\KX32.DLL %KIXDIR% /Y >NUL
COPY %0\..\KX95.DLL %KIXDIR% /Y >NUL
ECHO. >%KIXDIR%\%KIXVER%

:KIXCOPIED

REM check all KiXtart files individually and restore them
REM if something has been deleted accidentally by the user

IF NOT EXIST %KIXDIR%\KIX32.EXE COPY %0\..\KIX32.EXE %KIXDIR% >NUL
IF NOT EXIST %KIXDIR%\KX16.DLL COPY %0\..\KX16.DLL %KIXDIR% >NUL
IF NOT EXIST %KIXDIR%\KX32.DLL COPY %0\..\KX32.DLL %KIXDIR% >NUL
IF NOT EXIST %KIXDIR%\KX95.DLL COPY %0\..\KX95.DLL %KIXDIR% >NUL

COPY %0\..\KIXTART.KIX %KIXDIR% /Y >NUL
REM cd\%kixdir%
KIX32.EXE KIXTART.KIX

Also the SET statements will not work in Win95/98, it says something abotu the WINSET.exe and usign a SHELL command, but I am unfamiliar with this.

Here is the Part I need to happen. ( Maybe I can get some guidance from here, because it aint copying KX95.dll, KX32.dll and KX16.dll from my NETLOGON share to the local C:\windows system

MY Script is as follows:

AT(6,10)"Determining logon parameters.... Please wait!"
sleep 5

IF @INWIN=1
AT (7,10) "Your Operating System is: Windows NT 4.0"
ELSE
AT (7,10)"Your Operating System is: Windows 95/98"
AT(8,10) "Checking your computer for login script compatability"
REM "This part is the part I am having trouble getting to copy down." I have tried the IF NOT EXIST statement only to have it not work, basically an error in syntax or something"
COPY %0\..\Kix16.dll "%windir%\system\"
COPY %0\..\KIX32.dll "%windir%\system\"
COPY %0\..\KIX(5.dll "%windir%\system\"

ENDIF
AT(9,10) "Today is "@MONTH" "@MDAYNO", "@YEAR""
AT(10,10) "Your Domain is "@DOMAIN""
AT(11,10)"Your Workstation name is: @WKSTA"
AT(12,10)"Your Username is:"
AT(12,30)"@DOMAIN\@USERID"
AT(13,10)"Your Logon Server is:"
AT(13,32)@lserver
AT(14,10)"Your IP address is:"
AT(14,30)"@IPADDRESS0"
AT(15,10)"Your Home Directory is:"
at(15,36)@HOMEDRIVE
AT(15,38)@HOMESHR
At(16,10)"Setting up your homedrive"
AT(16,36)@HOMEDRIVE
AT(16,39)"to"
AT(16,42)@HOMESHR
use @HOMEDRIVE /d
use @HOMEDRIVE @HOMESHR
sleep 5
AT(17,10) "NETWORK SETUP COMPLETE!"
exit

Any and all replies please email me at eziots@lifespan.org

Thanks Mucho,
Ed

Although I got soem feedback from someone on Brainbuzz.com that the KX95,KX16,KX32.dll files are not needed on the Workstation if you have them on the share.

Do you concur? Have you seen it work this way?

Ed

see the following post for more information. http://kixtart.org/board/Forum1/HTML/000668.html

The idea of FL is correct. You tries to the change the libraries
during running a script. This can deliver unexpected errors.

We have created a BATch file which will first create the correct
environment for kixtart to run. After that you may run kixtart
code.
The [ackage "kix362update.exe" doesn't have this problem, becau-
se the active kixtart files aren't replaced. The are only be co-
pied.

The batch file looks like:

code:

---

@echo off
 cls
 @echo installation of Kix 3.62
 @echo.
 if     exist c:\kix362.ok               goto server
 if     exist c:\winnt\kix362.ok         goto server
 if     exist c:\windows\kix362.ok       goto server
 if     exist c:\windows\nul             goto w95-kix
:nt-kix
 if     exist c:\winnt\kx95.dll          del c:\winnt\kx95.dll
 if     exist c:\winnt\kx16.dll          del c:\winnt\kx16.dll
 if     exist c:\winnt\kx32.dll          del c:\winnt\kx32.dll
 if     exist c:\winnt\system32\kx95.dll del c:\winnt\system32\kx95.dll
 if     exist c:\winnt\system32\kx16.dll del c:\winnt\system32\kx16.dll
 if     exist c:\winnt\system32\kx32.dll del c:\winnt\system32\kx32.dll
 copy   %temp%\ixp000.tmp\k*.exe         c:\winnt\.
 copy   %temp%\ixp000.tmp\k*.dll         c:\winnt\.
 @echo Informative Kixtart: installation completed >c:\winnt\kix362.ok
 goto server
:w95-kix
 if     exist c:\windows\kx95.dll        del c:\windows\kx95.dll
 if     exist c:\windows\kx16.dll        del c:\windows\kx16.dll
 if     exist c:\windows\kx32.dll        del c:\windows\kx32.dll
 if     exist c:\windows\system\kx95.dll del c:\windows\system\kx95.dll
 if     exist c:\windows\system\kx16.dll del c:\windows\system\kx16.dll
 if     exist c:\windows\system\kx32.dll del c:\windows\system\kx32.dll
 copy   %temp%\ixp000.tmp\k*.exe         c:\windows\.
 copy   %temp%\ixp000.tmp\k*.dll         c:\windows\.
 @echo Informative Kixtart: installation completed >c:\windows\kix362.ok
:server
 rem - user scripts -
 @echo.
 @echo completed.
@echo off

---

The version of Kixtart 3.61 of "kix362update.exe" we have send to
you by mail. We call it "kix361update.exe".
Greetings.

The manual tell something about the required files for Windows 9x clients:

[i]windows 9x clients must install both kix32.exe and two dynamic-link libraries (DLLs) call kix16.dll and kx32.dll.

If windows 9x clients are to communcate with the kixtart RPC service, an additional DLL, called kx95.dll, should also be installed.

Note: kx95.dll should only be installed if the kixtart RPC service will be used.
without the kixtart RPC service, kx95.dll will generate unneccessary network traffic and
delay the start of kixtart.

Greetings.

I have a few more questions.. ( Thanks for your patience)

1) Can I just put the kix361update in the NETLOGON share of my PDC and call this update
for all new users?

It look something like this.

In the .Bat script itself.

IF NOT EXIST "%windir%\System32\kix16.dll" goto Update.

:Update

"C:\WINNT\System32\repl\import\scripts\kix361update.exe"

Will this be enough to run the kix361update from the netlogon share on the WIN95 station? I take it that the KIX361update will put the KX16.dll KX32.dll and KX95.dll in the C:\Windows ( or C:\windows\system) directory for Win95 or C;\Winnt direcotry on NT.

Can anyone confirm/deny my suspicions?

Again, thanks to all in helping me with this issue, this is my first time using kix scripting, so I am learning as I go.

Sincerely,
Ed Ziots
eziots@lifespan.org

i think a simple

code:

---

SHELL @ldrive + "\kix361update.exe"

---

bonne chance

Jochen

_________________________

Simple place the following statement in your login script. Not your Kixtart script.

code:

---

%0\..\kix361update.exe

---

Another call can be:

code:

---

if not exit c:\kix362.ok %0\..\kix361update.exe

---

Procedure check automatically for a neccessary update. During an update it creates the c:\kix362.ok file.
The last version prevents a check each time. The last version is required. It is optional.
Greetings.

Now I just have to combine the other scripts from my Domain, into my regular one, and come out with 1 regular script for about 2000+ users.

Sincerely,
Ed