|
|
|||||||
I was wondering if anyone could give me some help or suggestions. I have a Win9x machine that sometimes runs the login script and other times doesn't. It sometimes takes 2 to 3 reboots in order for it to run. I have looked in the Kixtart.log file to see what is happening and this is what I see: Failed to locate/connect to a kxrpc server Error: The network path was not found. Failed to load KX32.dll Error: One of the library files needed to run this application cannot be found. (0x485/1157) Any help would be greatly appreciated... Thanks, Ryan [ 29 April 2002, 15:56: Message edited by: rhughes1977 ] |
||||||||
|
|
|||||||
Kinda sounds like you may have a Win9x dll on the machine, assuming it is an isolated case and other Win2K machines are fine. |
||||||||
|
|
|||||||
My bad I meant to say that I have a win9x machine in my previous post |
||||||||
|
|
|||||||
OK, that makes more sense. Copy all the binaries (.exe & .dll) to %windir%. |
||||||||
|
|
|||||||
Dear, An easy way of installing kixtart on your clients is by using our iexpress packages. There are different versions for different Kixtart releases. At the moment there are five releases:
files will be replaced and missing files will be added. Regardless of file attributes. To prevent running more times weare using a control files. You can easily upgrade it with our iexpress package. Questions: how? A way of installing/updating kixtart of your clients: with only one additional statement For the installation of kixtart at your local workstation we see many version of doing it. Most statements in your BATch file are using for this duty. But there is also a way of doing it with a single statement, which doesn't only copy the required files, but also compare file version information. After completion a logfile will be created at your local workstation. Another way of installing/updating kixtart on your clients: For installing or updating of your clients you can download our packages kix363update.exe, kix400update.exe or kix401update.exe from our site http:\\home.wanadoo.nl\scripting. Possible calls in your logon procedure can be: As first line of your logon procedure you can use one of following formats:
for network environments (= update package will transfer during each logging on) code:or for dial-up environments (= update package will transfer only once)@echo off code:After using above programs there will be created a control@echo off file c:\kix363.ok, c:\kix400.ok, c:\kix401.ok, c:\kix401.ok or c:\kix402.ok. So it isn't necessary to run the installation process again, but we advise to update (or better: verify) kixtart files always. Reason: a security leak for running kixtart from clients. remarks: SECURITY LEAK for running kixtart from clients running kix32.exe from a local workstation can have also unwanted effects. An user can modify or replace your kix32.exe file. f.e. not to run your script but for reading your script. For RAS users it is interesting not to download each time the kixtart required files, but for other users we advise: always check the kixtart files and update them when necessary before running your KIX scripts. FIX for SECURITY LEAK: In our case the first statement of our default logon procedure for network users is always: %0\..\kix363update.exe /q and it will guarantee that kix32.exe file will always the correct one. remarks: performance
btw: related kixtart topic http://kixtart.org/board/Forum2/HTML/000583.html btw: be sure no other kix32.exe and DLLs are active on your clients. |
||||||||
|
|
|||||||
Solved? |