#64761 - 2002-04-22 03:43 AM
Re: KX*.dll then
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Have not investigated 3.62, but 3.63 and 4.02 has the same DLL versions which are 3.60.0.
HTH,
- Kent
|
|
Top
|
|
|
|
#64763 - 2002-04-23 05:57 AM
Re: KX*.dll then
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
First: a binary comparison shows DLLs aren't the same.
Secondly: the latest documentation (kixtart 4.10 build 84) talks about
Required files for Windows 9x Clients / Updating from previous versions
Windows 9x clients must install both Kix32.exe and two dynamic-link libraries
(DLLs) called KX16.DLL and KX32.DLL.
If Windows 9x clients are to communicate with the KiXtart RPC service, an
additional DLL, called KX95.DLL, should also be installed. Please see the
separate paragraph on the KiXtart RPC service for full details.
Note
KX95.DLL should only be installed if the KiXtart RPC service will be used.
Without the KiXtart RPC service, KX95.DLL will generate unnecessary network
traffic and delay the start of KiXtart.
- To update KiXtart for Windows 9x clients, make sure to replace all com-
ponents: KIX32.EXE, KX32.DLL, KX16.DLL.
If the KiXtart RPC service is used, make sure to also replace KX95.DLL and KXRPC.EXE.
We advise to upgrade always all files. With our packages it can easily be done.
f.e. upgrading to KiXtart 4.02 can be done with kix402upgrade.exe package.
your batch should looks like:
code:
@echo off
%0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
Also you should replace all KXRPC on your servers.
greetings.
btw: this latest version has new DLLs.
btw: see next reaction about the complete story of using our packages.
|
|
Top
|
|
|
|
|
#64764 - 2002-04-23 05:59 AM
Re: KX*.dll then
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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:
- kix362update.exe
- kix363update.exe
- kix400update.exe
- kix401update.exe
- kix402update.exe (the required one)
- kix410update.exe
Each time it will verify the correctness of your release. Incorrect
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:
- x:\kixtart\kix402update.exe /q
- %0\..\kix402update.exe /q
- if not exist c:\kix402.ok %0\..\kix402update.exe /q
- \\server\NETLOGON\kix402update.exe /q
Second line can be something like:
- kix32 %0\..\your_script.kix
- kix32 \\server\netlogon\your_script.kix
Results of your BATCH can be:
for network environments (= update package will transfer during each logging on)code:
@echo off
%0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
or for dial-up environments (= update package will transfer only once)
code:
@echo off
if not exist c:\kix402.ok %0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
After using above programs there will be created a control
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
- only 150 KBytes will be transfered to your workstation. the package has been compressed.
- always the correct set of kixtart files will be used. during the execution of scripts
the user can already starts working. - during installation or updating kixtart you will not get share violation error or busy file
error. the install.kix scripts runs with his own kixtart version. - for RAS users we create additional authorizations which will run minimum set of script code.
for them the logon procedure containts as statement:
if not exist c:\kix363.ok %0\..\kix363update.exe /q
greetings.
btw: related kixtart topic http://kixtart.org/board/Forum2/HTML/000583.html
|
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 1114 anonymous users online.
|
|
|
