Dear,
Based on Lonkero reaction we have modify our tool a little bit.
It wasn't possible to verify wkix32.exe version.
Now we have add an option to it.
With the call
- kixcheck.exe
it will verify for the kix32, kx16.dll, kx32.dll & kx95.dll files.
it is the default selection.
the output will be
code:
KixCheck 2.01 (c) scripting@wanadoo.nl 2002
Found as C:\WINDOWS\KIX32.EXE (08-07-2002 20:41:24 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
+ C:\WINDOWS\KX95.DLL (19-11-2001 05:00:00 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: complete.
- kixcheck.exe wkix32
it will verify for the wkix32, kx16.dll, kx32.dll & kx95.dll files.
code:
KixCheck 2.01 (c) scripting@wanadoo.nl 2002
Found as C:\WINDOWS\WKIX32.EXE (29-05-2002 16:56:14 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
+ C:\WINDOWS\KX95.DLL (19-11-2001 05:00:00 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: complete.
The help information (= kixcheck ?) is
code:
KixCheck 2.01 (c) MCA - scripting@wanadoo.nl - 2001, 2002
------------------------------------------------------------------------------
KixCheck [kix32|wkix32]
For simplicity we introduce also the wkixcheck.exe tool.
Only the differences are:
default it will search for the wkix32.exe instead of kix32.exe file.
The output will be
code:
WkixCheck 2.01 (c) scripting@wanadoo.nl 2002
Found as C:\WINDOWS\WKIX32.EXE (29-05-2002 16:56:14 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
+ C:\WINDOWS\KX95.DLL (19-11-2001 05:00:00 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: complete.
code:
WkixCheck 2.01 (c) scripting@wanadoo.nl 2002
Found as C:\WINDOWS\KIX32.EXE (08-07-2002 20:41:24 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
+ C:\WINDOWS\KX95.DLL (19-11-2001 05:00:00 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: complete.
The possible calls in your script can be:
- to verify kix32.exe
code:
@echo off
%0\..\kixcheck.exe
if errorlevel 1 %0\..\kix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
or
code:
@echo off
%0\..\kixcheck.exe kix32
if errorlevel 1 %0\..\kix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
or
code:
@echo off
%0\..\wkixcheck.exe kix32
if errorlevel 1 %0\..\kix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
- to verify wkix32.exe
code:
@echo off
%0\..\wkixcheck.exe
if errorlevel 1 %0\..\wkix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
or
code:
@echo off
%0\..\wkixcheck.exe wkix32
if errorlevel 1 %0\..\kix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
or
code:
@echo off
%0\..\kixcheck.exe wkix32
if errorlevel 1 %0\..\kix410update.exe /q
kix32.exe %0\..\your_script.kix
@echo off
greetings.
btw: the amount of bytes transfer is reducing from 150 KB to 10 KB by using this tool.
downloading of 150 KB can't be also a very big problem. A short connection f.e. to verify
your mail can transfer much more bytes.
this "problem" is only important for dial-up connections.
