MCA
(KiX Supporter)
2000-07-27 05:48 AM
KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

Each time it was necessary for us to select the proper kixtart editor.
For the extension KIX and SCR we have create some additional
registry entries.
So it is possible also to edit kixtart script with the same editor
and run them by using the right-menu list.

To complete it: we are also using a new icon.

The registry code is:

code:

REGEDIT4

[HKEY_CLASSES_ROOT\.KIX]
@="kix32 document"
[HKEY_CLASSES_ROOT\.SCR]
@="kix32 document"

; - special requirement: c:\kedit.ico
; editor of your choose f.e. notepad.exe


[HKEY_CLASSES_ROOT\kix32 document]
@="Kixtart"

[HKEY_CLASSES_ROOT\kix32 document\DefaultIcon]
@="c:\kedit.ico"

[HKEY_CLASSES_ROOT\kix32 document\shell]
@="Edit"

[HKEY_CLASSES_ROOT\kix32 document\shell\open]
@="Kix32 &run"

[HKEY_CLASSES_ROOT\kix32 document\shell\open\command]
@="kix32.exe %1"

[HKEY_CLASSES_ROOT\kix32 document\shell\print]
@="&Print"

[HKEY_CLASSES_ROOT\kix32 document\shell\print\command]
@="notepad.exe /p %1"

[HKEY_CLASSES_ROOT\kix32 document\shell\edit]
@="&Edit"

[HKEY_CLASSES_ROOT\kix32 document\shell\edit\command]
@="notepad.exe %1"


Possible actions of you are:


  • [HKEY_CLASSES_ROOT\kix32 document\DefaultIcon]
    @="c:\kedit.ico"

    it can be changed to another icon, or it can be removed (result: @="")
  • notepad.exe can be changed to another editor you like.
  • no specification of path by kix32.exe and notepad.exe require
    they are available by the serach through your path-list.
    kix32.exe will be available after installation it in the c:\windows
    or c:\winnt directory.
    automatic installation can taken place by kix362update, which you can found
    on the site http://home.wanadoo.nl/scripting .

At the same site you will find the above code (= kixedit.reg) and
the referenced icon kedit.ico.

Greetings.

[This message has been edited by MCA (edited 27 July 2000).]

MCA
(KiX Supporter)
2000-07-30 07:48 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

We add new capability to change the HKCR registry keys.
After running the kixedit.reg you will get also the
menu option Kix32 run with debug.

Programs: kix362registry.exe
Site: http://home.wanadoo.nl/scripting

The registry code is:

code:

REGEDIT4

[-HKEY_CLASSES_ROOT\.kix]
[-HKEY_CLASSES_ROOT\.scr]
[-HKEY_CLASSES_ROOT\kix32 document]

; - create Kixtart 3.62 registry entries
; -
; - requirements: kix32.exe + regedit.exe are available
; - options: c:\kedit.ico
; - editor of your choose f.e. notepad.exe

[HKEY_CLASSES_ROOT\.kix]
@="kix32 document"
[HKEY_CLASSES_ROOT\.scr]
@="kix32 document"

[HKEY_CLASSES_ROOT\kix32 document]
@="Kixtart"

[HKEY_CLASSES_ROOT\kix32 document\DefaultIcon]
@="c:\\kedit.ico"

[HKEY_CLASSES_ROOT\kix32 document\shell]
@="Edit"

[HKEY_CLASSES_ROOT\kix32 document\shell\open]
@="Kix32 &run"

[HKEY_CLASSES_ROOT\kix32 document\shell\open\command]
@="kix32.exe %1"

[HKEY_CLASSES_ROOT\kix32 document\shell\debug]
@="Kix32 run with &debug"

[HKEY_CLASSES_ROOT\kix32 document\shell\debug\command]
@="kix32.exe %1 /d"

[HKEY_CLASSES_ROOT\kix32 document\shell\print]
@="&Print"

[HKEY_CLASSES_ROOT\kix32 document\shell\print\command]
@="notepad.exe /p %1"

[HKEY_CLASSES_ROOT\kix32 document\shell\edit]
@="&Edit"

[HKEY_CLASSES_ROOT\kix32 document\shell\edit\command]
@="notepad.exe %1"


To prevent running more programs for a special result
we have combine it to a IExpress package. This package
is a copy kix362update.exe which is extended with
kixedit.reg and a new version of install.kix.
The package will use notepad as kixtart script editor.
You can use the kixedit.reg file to change this selec-
tion.

The IExpress code is:

code:

[Version]
Class=IEXPRESS
SEDVersion=3
[Options]
PackagePurpose=InstallApp
ShowInstallProgramWindow=1
HideExtractAnimation=1
UseLongFileName=0
InsideCompressed=0
CAB_FixedSize=0
CAB_ResvCodeSigning=0
RebootMode=N
InstallPrompt=%InstallPrompt%
DisplayLicense=%DisplayLicense%
FinishMessage=%FinishMessage%
TargetName=%TargetName%
FriendlyName=%FriendlyName%
AppLaunched=%AppLaunched%
PostInstallCmd=%PostInstallCmd%
AdminQuietInstCmd=%AdminQuietInstCmd%
UserQuietInstCmd=%UserQuietInstCmd%
SourceFiles=SourceFiles
[Strings]
InstallPrompt=
DisplayLicense=
FinishMessage=
TargetName=V:\kix362registry.exe
FriendlyName=Kixtart 3.62/1.03 install at local workstation + create HKCR associations
AppLaunched=Kix32.exe
PostInstallCmd=c:\temp\ixp000.tmp\Kix32.exe c:\temp\ixp000.tmp\install.kix
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="Install.kix"
FILE1="Kix32.exe"
FILE2="Kx16.dll"
FILE3="Kx32.dll"
FILE4="Kx95.dll"
FILE5="kixedit.reg"
FILE6="Kedit.ico"

[SourceFiles]
SourceFiles0=V:\

[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
%FILE3%=
%FILE4%=
%FILE5%=
%FILE6%=


Greetings.

[This message has been edited by MCA (edited 30 July 2000).]

MCA
(KiX Supporter)
2000-10-24 01:11 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

A new Iexpress package has created. It is an update for Kixtart 3.63 edition.
It not only install automatically kix32 to your windows directory, but also it creates
file associations + additional elements to your menu.

programs: kix363registry.exe
site: http://home.wanadoo.nl/scripting

Greetings.


btw: it requires:


  • directory c:\temp exist
  • environment variable tmp value must be c:\temp

btw: kix363update.exe doesn't create file associations in the registry.


MCA
(KiX Supporter)
2001-03-22 11:28 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

New Iexpress package has been created. Previously versions
required


  • directory c:\temp exist
  • environment variable tmp value must be c:\temp

The new versions doesn't have any requirement.
For kixtart 3.62 version:

  • kix362update.exe
  • kix362registry.exe

For kixtart 3.63 version:

  • kix363update.exe
  • kix363registry.exe

The registry versions install kixtart to your %systemroot%
folder and add file associations for kixtart to your HKCR registry
keys. So you have additional elements to your menu.
The update versions install kixtart also to your %systemroot%
folder and remove file associations for kixtart from your
registry.

Possible calls in your logon procedure can be:


  • x:\kixtart\kix362update.exe /q
  • %0\..\kix363registry.exe /q
  • if not exist c:\kix363.ok %0\..\kix363update.exe /q

After using above programs there will be created a control
file c:\kix362.ok or c:\kix363.ok. So it isn't
necessary to run the installation process again.

Greetings.


BTW: packages contains an update of install.kix which you can
find also on site http://home.wanadoo.nl/scripting .


MCA
(KiX Supporter)
2001-03-23 03:03 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

An example of debug information of running install.kix, which
will be processed during execution of kix36?update.exe or
kix36?registry.exe files.

code:

Kixtart 3.63 - W95 debug mode (vs 2.00) 23:36:14

Informative INSTALL: copy c:\temp\ixp002.tmp\kix32.exe c:\windows\kix32.exe

size.old = 163840
size.new = 163840
time.old = 2000/10/15 00:00:00
time.new = 2000/10/15 00:00:00

company name
filedescription KiXtart main executable
fileversion 3, 63, 0, 0
internalname KIX32
language 0409English
legalcopyright Copyright Microsoft Corp. 1999
legaltrademarks $
originalfilename KIX32.EXE
privatebuild
productname KiXtart
productversion 3, 63, 0, 0
specialbuild

Informative INSTALL: copy c:\temp\ixp002.tmp\kx16.dll c:\windows\kx16.dll

size.old = 47104
size.new = 47104
time.old = 1999/09/01 00:00:00
time.new = 1999/09/01 00:00:00

company name
filedescription
fileversion
internalname
language
legalcopyright
legaltrademarks
originalfilename
privatebuild
productname
productversion
specialbuild

Informative INSTALL: copy c:\temp\ixp002.tmp\kx32.dll c:\windows\kx32.dll

size.old = 32768
size.new = 32768
time.old = 1999/09/01 00:00:00
time.new = 1999/09/01 00:00:00

company name
filedescription KiXtart 32 bit Thunk DLL
fileversion 3, 60, 0, 0
internalname KX32
language 0409English
legalcopyright Copyright © Microsoft Corp. 1999
legaltrademarks
originalfilename KX32.DLL
privatebuild
productname KiXtart
productversion 3, 60, 0, 0
specialbuild

Informative INSTALL: copy c:\temp\ixp002.tmp\kx95.dll c:\windows\kx95.dll

size.old = 36864
size.new = 36864
time.old = 1999/09/01 00:00:00
time.new = 1999/09/01 00:00:00

company name
filedescription KiXtart RPC client DLL
fileversion 3, 60, 0, 0
internalname KX95
language 0409English
legalcopyright Copyright © Microsoft Corp. 1999
legaltrademarks
originalfilename KX95.DLL
privatebuild
productname KiXtart
productversion 3, 60, 0, 0
specialbuild


logevent = Kixtart-UPDATE 2.00 script completed successfully (23:36:14 - 23:36:44) (kix32.exe kx16.dll kx32.dll kx95.dll) to "c:\windows\"

Kixtart 3.63 update incompleted. ('c:\temp\IXP002.TMP\' -> 'C:\WINDOWS\')


Greetings.

MCA
(KiX Supporter)
2001-07-13 06:48 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

We have create and publish the new tool kixcheck. It doesn't
need any parameter. It will check all available KiXtart modules
addressable by your %path% specification.
In incorrect or incomplete will automatically delete the c:\kix????.ok
files from your local workstation.
It isn't necessary to remove them, because the program returns also an
ERRORLEVEL, which can be used by your BATch file.
Possible codes:

code:

%0\..\kixcheck.exe
if errorlevel 1 %0\..\kix363update.exe /q


or
code:

%0\..\kixcheck.exe >nul
if not exist c:\kix363.ok %0\..\kix363update.exe /q


or
code:

%0\..\kix363update.exe /q


The last one will always update your environment with the correct
files.
Possible output of KixCheck can be
code:

KixCheck 1.03 (c) scripting@wanadoo.nl 2001

Found as C:\WINDOWS\KIX32.EXE (15-10-2000 14:50:40 163840 bytes)
+ C:\WINDOWS\KX16.DLL (01-09-1999 16:00:00 47104 bytes)
+ C:\WINDOWS\KX32.DLL (01-09-1999 16:00:00 32768 bytes)
+ C:\WINDOWS\KX95.DLL (01-09-1999 16:00:00 36864 bytes)

path C:\WINDOWS;C:\WINDOWS\COMMAND

KiXtart environment: complete



See also the new topic
http://kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=2&t=001950
for furthur comment from other other members.
Greetings.


LonkeroAdministrator
(KiX Master Guru)
2001-07-13 03:24 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

It seems that .udf is gonna be the standard file extension for udf's.
so why can't we add it too to kix-documents? well, could do fully own reg-key udf-file as "User Defined Kix-function"


JochenAdministrator
(KiX Supporter)
2001-07-13 05:05 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Thank God I use UltraEdit !

I can achieve this by setting this in Options/File Associations ...

btw. I'm not related to IDM Computer Solutions Inc. in any way , et cetera , et cetera .. it's just a great Kix editor !


Jochen

MCA
(KiX Supporter)
2001-07-16 02:19 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

At this moment all kind of extensions are circulating. We find it to
early to modify our scripts with possible extensions.
A very nice one is: .k2k which is related to KiXtart 2001 release.
Greetings.

MCA
(KiX Supporter)
2001-07-20 06:44 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

The registry file kixedit.reg has been updated. It will now
support file association links with

  • .kix
  • .k2k (new)
  • .scr
  • .udf (new)

The iexpress package kix400registry.exe will make the same
file associations.
Package release compliant with kixtart 4.00 rc1 (build 45) release.
Greetings.


MCA
(KiX Supporter)
2001-11-21 06:43 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

A new iexpress package of kixtart 4.00 finale release (build 62)
has been created.
The package kix400registry.exe contains also extensions:

  • it logs also information about windows XP (input by kdyer last night)
  • the installation mode 'update/registry' will also be logged

This version will also (re)create the file associations with .k2k,
.udf and .kix.

An example of latest issue

code:

[Kixtart NT4]
kix32.exe 4.00=2001/11/21 02:05:04 -> 2001/11/19 04:00:00 196608
kx16.dll 4.00=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 47104
kx32.dll 4.00=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 49152
kx95.dll 4.00=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 49152
Kixtart 4.00=installation completed at 2001/11/21 02:05:05 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\winnt\"
Kixtart 4.00 mode=update


or
code:

[Kixtart NT4]
kix32.exe 4.00=2001/11/21 02:03:16 -> 2001/11/19 04:00:00 196608
kx16.dll 4.00=2001/11/21 02:03:16 -> 2001/11/19 04:00:00 47104
kx32.dll 4.00=2001/11/21 02:03:17 -> 2001/11/19 04:00:00 49152
kx95.dll 4.00=2001/11/21 02:03:17 -> 2001/11/19 04:00:00 49152
Kixtart 4.00=installation completed at 2001/11/21 02:03:17 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\winnt\"
Kixtart 4.00 mode=registry


greetings.


btw: running a "kix400update" will remove existing file associations
with .k2k, .udf, .kix and .scr.

MCA
(KiX Supporter)
2002-01-09 11:42 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

Dear,

We have create an iexpress package which contains the wkix32.exe file.
During the installation process
[/list]

  • it will verify the files wkix32.exe, kx16.dll, kx32.dll & kx95.dll
    missing files will be added. incorrect files will be replaced.
  • it will not influence the registry file association settings
  • the control file will be kix401w.ok instead of kix401.ok.
    [/list]
    The file on our site http://home.wanadoo.nl/scripting
    is
    wkix401update.exe
    A possible call in your logon batch file can be:
    code:

    @echo off
    %0\..\wkix401update.exe /q
    rem
    rem - your script call
    rem
    @echo off

    We didn't create file association entries with wkix32.exe, because the way
    of correct calling can be different on different windows environments.

    The other related iexpress packages are:

    • kix401registry.exe
      (install kix32.exe with related DLLs files. it will remove the file associations
      .k2k, .kix, .scr and .udf and also it will remove
      the menu issues)

      (creates c:\kix401.ok as control file)

    • kix401update.exe
      (install kix32.exe with related DLLs files. it will add the file associations
      .k2k, .kix, .scr and .udf and also it will add
      the menu issues)

      (creates c:\kix401.ok as control file)


    Any question, comment or remark is welcome.
    greetings.

  • MCA
    (KiX Supporter)
    2002-01-22 04:32 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    A new iexpress package of kixtart 4.02 finale release (build 71)
    has been created.
    The package kix402registry.exe contains also extensions:

    • it logs also information about windows XP (input by kdyer last night)
    • the installation mode 'update/registry' will also be logged

    This version will also (re)create the file associations with .k2k,
    .udf and .kix.

    An example of latest issue

    code:

    [Kixtart NT4]
    kix32.exe 4.02=2001/11/21 02:05:04 -> 2001/11/19 04:00:00 196608
    kx16.dll 4.02=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 47104
    kx32.dll 4.02=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 49152
    kx95.dll 4.02=2001/11/21 02:05:05 -> 2001/11/19 04:00:00 49152
    Kixtart 4.02=installation completed at 2001/11/21 02:05:05 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\winnt\"
    Kixtart 4.02 mode=update


    or
    code:

    [Kixtart NT4]
    kix32.exe 4.02=2001/11/21 02:03:16 -> 2001/11/19 04:00:00 196608
    kx16.dll 4.02=2001/11/21 02:03:16 -> 2001/11/19 04:00:00 47104
    kx32.dll 4.02=2001/11/21 02:03:17 -> 2001/11/19 04:00:00 49152
    kx95.dll 4.02=2001/11/21 02:03:17 -> 2001/11/19 04:00:00 49152
    Kixtart 4.02=installation completed at 2001/11/21 02:03:17 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\winnt\"
    Kixtart 4.02 mode=registry


    greetings.


    btw: running a "kix402update" will remove existing file associations
    with .k2k, .udf, .kix and .scr.

    MCA
    (KiX Supporter)
    2002-04-11 04:04 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    A new iexpress package of kixtart 4.10 beta 1 (build 84) release
    has been created.

    Also all other iexpress packages are upgraded.
    New functions:
    • it can show a MessageBox during the installation of any kind of package.
      it is only necessary to define the environment variable kix-show for
      activation.
      To prevent a box each time we will show only a box
      - by installation of new kixtart release.
      - by installation of another type of kixtart (kix32.exe / wkix32.exe)
      - by an incomplete set of kixtart files. a complete set contain: kix32.exe/wkix32.exe, kx16.dll, kx32.dll, kx95.dll
      The other environment is kix-debug, which will create the debug file c:\kixtart.logand which will show other MessageBox.
    • now the check-file c:\kix???.ok file will show the build version
      of your KiXtart release.
    • only the actual check-file will remain on your local drive.
    Current availablepackages
    • kix362update.exe (kix32.exe)
    • kix363update.exe (kix32.exe)
    • kix400update.exe (kix32.exe)
    • kix401update.exe (kix32.exe)
    • kix402update.exe (kix32.exe)
    • kix410update.exe (kix32.exe)
    • kix362registry.exe (kix32.exe)
    • kix363registry.exe (kix32.exe)
    • kix400registry.exe (kix32.exe)
    • kix401registry.exe (kix32.exe)
    • kix402registry.exe (kix32.exe)
    • kix410registry.exe (kix32.exe)
    • wkix400update.exe (wkix32.exe)
    • wkix401update.exe (wkix32.exe)
    • wkix402update.exe (wkix32.exe)
    • wkix410update.exe (wkix32.exe)
    An example of new kix???.ok
    code:
    [Kixtart NT4]
    kix32.exe 4.02=2002/04/10 00:27:53 -> 2002/01/18 00:00:00 204800 (build 071)
    kx16.dll 4.02=2002/04/10 00:27:53 -> 2001/11/19 00:00:00 47104
    kx32.dll 4.02=2002/04/10 00:27:54 -> 2001/11/19 00:00:00 49152
    kx95.dll 4.02=2002/04/10 00:27:55 -> 2001/11/19 00:00:00 49152
    Kixtart 4.02=installation completed at 2002/04/10 00:27:55 (+kix32.exe +kx16.dll +kx32.dll =kx95.dll) to "c:\winnt\"
    Kixtart 4.02 mode=registry

    greetings.

    btw: running a kix???update will remove existing file associations
    with .k2k, .udf, .kix and .scr.

    btw: we have also create wkix???update.exe which will not influence the existing
    file associations. it is related to the WKIX32.EXE file.


    MCA
    (KiX Supporter)
    2002-06-20 11:52 PM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    All our iexpress package for updating your clients has been updated.
    Issues
    • we create the check file also in %windir% directory.
      this check file kix???.ok.
      the problem was that in some situations the file c:\kix???.ok couldn't
      be created. for backwards compatibility we create two check files
      - c:\kix???.ok
      - %windir%\kix???.ok
      btw: we are using "HKLM\Software\Microsoft\Windows\CurrentVersion\Run\Windir" value.
    • during the creation of file associations with kix32 we aren't using
      the external kixedit.reg file. it is using internal kixtart func-
      tions.
    • to prevent also problems with the installation of c:\kixedit.ico file,
      we move it also to the %windir% directory.
    • the control-file is restyled and as kixtart users you can easily read
      information from it.
      an example:
      code:
      [KiXtart]
      kix32.exe=2002/06/18 20:19:09 -> 2002/05/29 16:59:06 225280 (build 095)
      kx16.dll=2002/06/18 20:19:09 -> 2001/08/27 20:17:29 47104
      kx32.dll=2002/06/18 20:19:09 -> 2002/03/29 12:38:08 49152
      kx95.dll=2002/06/18 20:19:09 -> 2001/11/19 05:00:00 49152
      KiXtart=installation completed at 2002/06/18 20:19:09 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      KiXtart release=ME -> kix 4.10 Release Candidate 2
      KiXtart mode=registry

      btw: the old format was
      code:
      [Kixtart ME]
      kix32.exe 4.10 Beta 1=2002/05/01 17:04:13 -> 2002/04/03 00:00:00 221184 (build 084)
      kx16.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2001/08/27 00:00:00 47104
      kx32.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2002/03/29 00:00:00 49152
      kx95.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2001/11/19 00:00:00 49152
      Kixtart 4.10 Beta 1=installation completed at 2002/05/01 17:04:13 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      Kixtart 4.10 Beta 1 mode=registry

    • we have rename the debugging file from "c:\kixtart.log" to "%tmp%\kixtart.txt".
      btw: this file will created when environment variable "kix-debug" exist.
      btw: by problem you should mail also this file to us.
      an example of it
      tuesday 2002/06/18 20:19:09- kixtart 4.10 Release Candidate 2/3.03e script starting.
      -
      -curdir: c:\windows\temp\ixp000.tmp
      -scriptdir: c:\windows\temp\ixp000.tmp
      -scriptname: start2.kix
      -startdir: c:\windows\temp\ixp000.tmp
      -
      -userid: -/-
      -user priv: guest
      -version: inwin=2/dos=4.90/productsuite=/producttype=Windows Me/csd=
      -
      - start-20:19:09- 0 The operation completed successfully.
      - 1-20:19:09- 0 The operation completed successfully.
      - 2-20:19:09- 0 The operation completed successfully.
      - 3-20:19:09- 0 The operation completed successfully.
      - 426-20:19:10- 6 The handle is invalid.
      - end-20:19:10- 6 The handle is invalid.

      -
      -tuesday 2002/06/18 20:19:10- kixtart 4.10 Beta 1/3.03e script ending.
      -
      -Intel Pentium III (0 Mhz, memory 511 MB)
      -

    Still the special environment variable exist
    • kix-debug
      it creates a logfile in your temporary directory. name is %tmp%\kixtart.txt.
    • kix-show
      it shows information about installation progress by some MessageBox's.
    Your logon BATch file can be something like:
    code:
    @echo off
    %0\..\kix410update.exe /q
    kix32 %\..\your_script.kix
    @echo

    or
    code:
    @echo off
    %0\..\kixcheck.exe
    if errorlevel 1 %0\..\kix410update.exe /q
    kix32 \\server\netlogon\your_script.kix
    @echo off

    or
    code:
    @echo off
    if not exist %windir%\kix410.ok %0\..\kix410update.exe /q
    if not exist %windir%\kix410.ok goto net
    kix32 \\server\netlogon\your_script.kix
    goto end
    :net
    \\server\netlogon\kix32 \\server\netlogon\your_script.kix
    :end
    @echo off

    We were using our tool kixcheck in above logon BATch files
    which return an errorlevel 1 when kixtart binaries aren't installed
    in a correct way.
    The output of "kixcheck" is:
    • for a correct installation:
      code:
      KixCheck 1.05 (c) scripting@wanadoo.nl 2001

      Found as C:\WINDOWS\KIX32.EXE (29-05-2002 16:59:12 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.

    • for an incomplete the output look like:
      code:
      KixCheck 1.05 (c) scripting@wanadoo.nl 2001

      Found as C:\WINDOWS\KIX32.EXE (29-05-2002 16:59:12 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)

      path c:\windows;c:\windows\command

      KiXtart environment: incomplete. remove "c:\kix*.ok" files.

    greetings.
    (our reaction 3000+ to the board)

    [ 20 June 2002, 23:52: Message edited by: MCA ]


    MCA
    (KiX Supporter)
    2002-07-08 08:31 PM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Now compliant with Kixtart 4.10 final release (build 98)

    MCA
    (KiX Supporter)
    2002-07-08 10:13 PM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Now compliant with Kixtart 4.10 final release (build 99)

    MCA
    (KiX Supporter)
    2002-07-19 12:02 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    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.


    MCA
    (KiX Supporter)
    2002-08-15 02:18 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    Based on the input from Kent Dyer & Les Ligetfa we
    have extend the iexpress packages a little bit.
    New is:
    • implementation of "terminal service" model.
      we are using drive based on "systemroot" registry setting. it solves
      problems with unavailable C-drive.
      for the temporary files it will use as prefix %tmp% environment
      variable.
    • status of file association .scr untouch by another association.
    • additional information will be written to debugging file. So you can
      see what the actual registry settings for .K2K, .KIX, .SCR and .UDF are.
    • script returns now also a errorlevel- 0 = a complete installation done
      - 1 = a incomplete installation done
      this value can use in your BATch file.
      f.e.
      code:
      @echo off
      %0\..\kix410update.exe /q
      if errorlevel 1 goto server
      if errorlevel 0 goto client
      goto server
      :server
      %0\..\kix32.exe %0\..\your_script.kix
      goto end
      :client
      kix32 %0\..\your_script.kix
      :end
      @echo off

    • in the NTx environment it isn't necessary to install the kx16.dll,
      kx32.dll and kx95.dll.
      we make it possible such installation, but for backward compatibility
      we introduce the additional environment variable kix-only-required.
      its value isn't important.
      the control file shows the result of such installation.
    Current environment variables to control packages are
    • kix-debug
    • kix-only-required
    • kix-show
    Examples:
    • a standard installation
      code:
      [KiXtart]
      kix32.exe=2002/08/14 02:35:01 -> 2002/07/08 20:41:12 225280 (build 099)
      kx16.dll=2002/08/14 02:35:02 -> 2001/08/27 20:17:29 47104
      kx32.dll=2002/08/14 02:35:02 -> 2002/03/29 12:38:08 49152
      kx95.dll=2002/08/14 02:35:02 -> 2001/11/19 05:00:00 49152
      KiXtart=installation completed at 2002/08/14 02:35:02 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      KiXtart release=ME -> kix 4.10
      KiXtart mode=registry

      kix-only-required specified.
      code:
      [KiXtart]
      kix32.exe=2002/08/14 02:46:02 -> 2002/07/08 20:41:12 225280 (build 099)
      KiXtart=installation completed at 2002/08/14 02:46:02 (+kix32.exe -kx16.dll -kx32.dll -kx95.dll) to "c:\windows\"
      KiXtart release=NT4 -> kix 4.10
      KiXtart mode=registry (only required files)

      -kx16.dll, -kx32.dll and -kix95.dll were removed.

      kix-only-required specified.
      code:
      [KiXtart]
      kix32.exe=2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
      KiXtart=installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
      KiXtart release=NT4 -> kix 4.10
      KiXtart mode=registry (only required files)

      ?kx16.dll, ?kx32.dll and ?kix95.dll aren't available on drive.
    • the debugging output when kix-debug & kix-only-required are specified
      in a NTx environment:
      code:
      Kixtart 4.10 - NT4 debug mode (vs 3.07)               02:57:34

      Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe

      size.old = 225280
      size.new = 225280
      time.old = 2002/07/08 20:41:12
      time.new = 2002/07/08 20:41:12

      company name
      filedescription KiXtart main executable
      fileversion 4, 10, 0, 0
      internalname KIX32
      language 0409English
      legalcopyright Copyright Ruud van Velsen 2002
      legaltrademarks $
      originalfilename KIX32.EXE
      privatebuild
      productname KiXtart
      productversion 4, 10, 0, 0
      specialbuild Build 099

      => KiXtart - kix32.exe - 2002/08/14 02:57:36 -> 2002/07/08 20:41:12 225280 (build 099)
      => KiXtart - - installation completed at 2002/08/14 02:57:36 (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
      Informative INSTALL: creation of KIX file associations.
      =>
      => .kix kix32 document
      => .k2k kix32 document
      => .scr kix32 document
      => .udf kix32 document
      => kix32 document Edit
      =>
      => KiXtart - KiXtart release - NT4 -> kix 4.10
      => KiXtart - KiXtart mode - registry (only required files)

      logevent = Kixtart-UPDATE 3.07 script completed successfully (02:57:34 - 02:57:36) (+kix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"

      Kixtart 4.10 update completed. ('X:\' -> 'c:\windows\')

    • the debugging output when kix-debug & kix-only-required are specified
      in a 95x environment:
      code:
      Kixtart 4.10 - ME debug mode (vs 3.07)               02:59:26

      Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe

      size.old = 225280
      size.new = 225280
      time.old = 2002/07/08 20:41:12
      time.new = 2002/07/08 20:41:12

      company name
      filedescription KiXtart main executable
      fileversion 4, 10, 0, 0
      internalname KIX32
      language 0409English
      legalcopyright Copyright Ruud van Velsen 2002
      legaltrademarks $
      originalfilename KIX32.EXE
      privatebuild
      productname KiXtart
      productversion 4, 10, 0, 0
      specialbuild Build 099

      Informative INSTALL: copy x:\kx16.dll c:\windows\kx16.dll

      size.old = 47104
      size.new = 47104
      time.old = 2001/08/27 20:17:29
      time.new = 2001/08/27 20:17:29

      company name
      filedescription
      fileversion
      internalname
      language
      legalcopyright
      legaltrademarks
      originalfilename
      privatebuild
      productname
      productversion
      specialbuild

      Informative INSTALL: copy x:\kx32.dll c:\windows\kx32.dll

      size.old = 49152
      size.new = 49152
      time.old = 2002/03/29 12:38:08
      time.new = 2002/03/29 12:38:08

      company name
      filedescription KiXtart 32 bit Thunk DLL
      fileversion 3, 61, 1, 0
      internalname KX32
      language 0409English
      legalcopyright Copyright Ruud van Velsen. 2001
      legaltrademarks
      originalfilename KX32.DLL
      privatebuild
      productname KiXtart
      productversion 3, 61, 1, 0
      specialbuild

      Informative INSTALL: copy x:\kx95.dll c:\windows\kx95.dll

      size.old = 49152
      size.new = 49152
      time.old = 2001/11/19 05:00:00
      time.new = 2001/11/19 05:00:00

      company name
      filedescription KiXtart RPC client DLL
      fileversion 3, 60, 0, 0
      internalname KX95
      language 0409English
      legalcopyright Copyright Ruud van Velsen. 2001
      legaltrademarks
      originalfilename KX95.DLL
      privatebuild
      productname KiXtart
      productversion 3, 60, 0, 0
      specialbuild

      => KiXtart - kix32.exe - 2002/08/14 02:59:31 -> 2002/07/08 20:41:12 225280 (build 099)
      => KiXtart - kx16.dll - 2002/08/14 02:59:31 -> 2001/08/27 20:17:29 47104
      => KiXtart - kx32.dll - 2002/08/14 02:59:31 -> 2002/03/29 12:38:08 49152
      => KiXtart - kx95.dll - 2002/08/14 02:59:31 -> 2001/11/19 05:00:00 49152
      => KiXtart - - installation completed at 2002/08/14 02:59:31 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      Informative INSTALL: creation of KIX file associations.
      =>
      => .kix kix32 document
      => .k2k kix32 document
      => .scr kix32 document
      => .udf kix32 document
      => kix32 document Edit
      =>
      => KiXtart - KiXtart release - ME -> kix 4.10
      => KiXtart - KiXtart mode - registry

      logevent = Kixtart-UPDATE 3.07 script completed successfully (02:59:26 - 02:59:31) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"

      Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

    • a Kix410registry.exe installation when .scr has already another
      file association:
      code:
      Kixtart 4.10 - ME debug mode (vs 3.06)               01:30:11

      Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe

      => KiXtart - kix32.exe - 2002/08/08 01:30:18 -> 2002/07/08 20:41:12 225280 (build 099)
      => KiXtart - kx16.dll - 2002/08/08 01:30:18 -> 2001/08/27 20:17:29 47104
      => KiXtart - kx32.dll - 2002/08/08 01:30:18 -> 2002/03/29 12:38:08 49152
      => KiXtart - kx95.dll - 2002/08/08 01:30:18 -> 2001/11/19 05:00:00 49152
      => KiXtart - - installation completed at 2002/08/08 01:30:18 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      Informative INSTALL: creation of KIX file associations.
      =>
      => .kix kix32 document
      => .k2k kix32 document
      => .scr kix32 document test
      => .udf kix32 document
      => kix32 document Edit
      =>
      => KiXtart - KiXtart release - ME -> kix 4.10
      => KiXtart - KiXtart mode - registry

      logevent = Kixtart-UPDATE 3.06 script completed successfully (01:30:11 - 01:30:19) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"

      Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

    • a Kix410update.exe installation when .scr has already another
      file association:
      code:
      Kixtart 4.10 - ME debug mode (vs 3.06)               01:30:58

      Informative INSTALL: copy x:\kix32.exe c:\windows\kix32.exe

      => KiXtart - kix32.exe - 2002/08/08 01:31:03 -> 2002/07/08 20:41:12 225280 (build 099)
      => KiXtart - kx16.dll - 2002/08/08 01:31:03 -> 2001/08/27 20:17:29 47104
      => KiXtart - kx32.dll - 2002/08/08 01:31:03 -> 2002/03/29 12:38:08 49152
      => KiXtart - kx95.dll - 2002/08/08 01:31:03 -> 2001/11/19 05:00:00 49152
      => KiXtart - - installation completed at 2002/08/08 01:31:03 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
      =>
      => .kix
      => .k2k
      => .scr kix32 document test
      => .udf
      => kix32 document
      =>
      => KiXtart - KiXtart release - ME -> kix 4.10
      => KiXtart - KiXtart mode - update

      logevent = Kixtart-UPDATE 3.06 script completed successfully (01:30:58 - 01:31:03) (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"

      Kixtart 4.10 update completed. ('X:\' -> 'C:\WINDOWS\')

    • the control file when you are installation kixtart files on f.e. X-drive
      code:
      [KiXtart]
      kix32.exe=2002/08/07 23:42:53 -> 2002/07/08 20:41:12 225280 (build 099)
      kx16.dll=2002/08/07 23:42:53 -> 2001/08/27 20:17:29 47104
      kx32.dll=2002/08/07 23:42:53 -> 2002/03/29 12:38:08 49152
      kx95.dll=2002/08/07 23:42:53 -> 2001/11/19 05:00:00 49152
      KiXtart=installation completed at 2002/08/07 23:42:53 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "x:\windows\"
      KiXtart release=ME -> kix 4.10
      KiXtart mode=registry

    greetings.


    Kdyer
    (KiX Supporter)
    2002-08-15 09:32 PM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    MCA,

    Made the following change to the START1.KIX script, so that we don't have to introduce an environment variable.

    code:
      $required_mode="no"
    IF ($nt_mode = "yes")
    $required_mode="yes"
    ELSE
    $required_mode="no"
    ENDIF

    Also, made the following change for the registry changes:
    code:
    $associat = "No" 
    ...
    ; --------------------------------------------------------------------------
    ; - HKCR registry update -
    ; --------------------------------------------------------------------------
    IF $associat = "Yes"
    ...
    ENDIF

    Thanks,

    Kent


    MCA
    (KiX Supporter)
    2002-11-15 02:16 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Now compliant with
    - Kixtart 4.11 final release (build 102)
    - Kixtart 4.12 final release (build 112)
    greetings.

    btw: Kent, we doesn't implement your latest suggestion at this release.
    Before doing this we want to know "work new iexpress package for all windows versions?".

    (TO_DO)

    [ 15. November 2002, 04:52: Message edited by: MCA ]


    MCA
    (KiX Supporter)
    2002-11-15 02:20 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Current available versions are
    - kix362update.exe
    - kix363update.exe
    - kix402update.exe
    - kix410update.exe
    - kix411update.exe
    - kix412update.exe

    - kix362registry.exe
    - kix363registry.exe
    - kix402registry.exe
    - kix410registry.exe
    - kix411registry.exe
    - kix412registry.exe

    - wkix402update.exe
    - wkix410update.exe
    - wkix411update.exe
    - wkix412update.exe

    We have remove the following versions:
    - kix400update.exe
    - kix401update.exe
    - kix400registry.exe
    - kix401registry.exe
    - wkix400update.exe
    - wkix401update.exe
    greetings.


    MCA
    (KiX Supporter)
    2003-01-20 02:03 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    Based on "KiXtart 2001 - 4.20 release candidate 1 (build 123)" we have create
    new iexpress packages.
    Available now
    - kix420registry.exe
    - kix420update.exe
    - wkix420update.exe
    Now available by

    Summary of Site
    &
    Home - Kix Downloads

    pages.
    greetings.


    MCA
    (KiX Supporter)
    2003-02-27 01:26 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    We upgrade all our packages. The console-less version doesn't require KIX32.EXE for
    the installation process.
    We must only change our installation scripts for WKIX32.EXE installation. Previous-
    ly we show a MessageBox for developpers, but with the specification like

    wkix32.exe /I winstall.kix

    the installation process will hang. Reason: a hidden MessageBox shows up, but you
    doesn't have the capability to enter something.

    The new main scripts for the WKIX32 installations are
    winstall.kix
    code:
      CLS
    IF setconsole("hide")
    ENDIF
    ;
    ; NT/95 install kixtart - Kixtart 3.62, 3.63, 4.00, 4.01, 4.02, 4.10, 4.11, 4.12, 4.20
    ;
    ; (c) scripting@wanadoo.nl - 2000, 2001, 2002, 2003
    ;
    ; vs 3.00 - program
    ;
    ; 1.00 (20010605) original version. created for IExpress package.
    ; - split script for with/without debugging.
    ; - activate $debug_mode when variable %kix-debug% is declared.
    ; - shows also @curdir value.
    ; 2.00w (20020110) - used by installation of console-less wkix32 package.
    ; 2.01w (20020410) - shows correct check-file name "c:\kix???w.ok".
    ; 2.02w (20020815) - using $system_drive for logging information (input by Kent Dyer).
    ; - changing "kixtart.log" to "kixdebug.txt".
    ; 3.00w (20030225) - suppress MessageBox window. with "/I" specified package will hang, when
    ; environment variable "kix-debug" or "kix-show" was created.
    ;
    $prgrm_version="3.00"
    ;
    $debug_mode="no"
    IF (len(ExpandEnvironmentVars(CHR(37)+"kix-debug"+CHR(37))) <> 0)
    $debug_mode="yes"
    ENDIF
    ;
    IF ($debug_mode = "yes")
    $message="Installation of Kixtart "+@kix+" CONSOLE-LESS version started from '"+LCASE(@curdir)+"'."
    $title="Kixtart "+@kix
    ; IF (MessageBox($message, $title, 340, 300) <> 0)
    ; ENDIF
    ? $message
    ENDIF
    IF ($debug_mode <> "yes")
    call "wstart1.kix"
    ELSE
    call "wstart2.kix"
    ENDIF
    :end
    IF (@inwin = 1)
    $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot")
    ELSE
    $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot")
    ENDIF
    IF (len($destination_directory) = 0)
    $destination_directory=@lanroot
    ENDIF
    IF (Substr($destination_directory,len($destination_directory),1) <> "\")
    $destination_directory=$destination_directory+"\"
    ENDIF
    $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on -
    ;
    IF (RedirectOutput("CON") = 0)
    ENDIF
    $debug_mode="no"
    IF (len(ExpandEnvironmentVars(CHR(37)+"kix-debug"+CHR(37))) <> 0)
    $debug_mode="yes"
    ENDIF
    ;
    IF ($debug_mode <> "yes")
    ? "Informative INSTALL: no creation of debug list '%tmp%\kixdebug.txt'"
    ELSE
    ? "Informative INSTALL: create debug list '%tmp%\kixdebug.txt'"
    IF (Exist($system_drive+"kix"+substr(@kix,1,1)+substr(@kix,3,2)+"w.ok") = 1) OR (Exist($destination_directory+"kix"+substr(@kix,1,1)+substr(@kix,3,2)+"w.ok") = 1)
    $message="Installation of Kixtart "+@kix+" CONSOLE-LESS version completed from '"+LCASE(@curdir)+"'."
    $message=$message+" File '"+UCASE("kix"+substr(@kix,1,1)+substr(@kix,3,2)+"w.ok")+"' created."
    ELSE
    $message="Installation of Kixtart "+@kix+" CONSOLE-LESS version incompleted from '"+LCASE(@curdir)+"'."
    $message=$message+" No file '"+UCASE("kix"+substr(@kix,1,1)+substr(@kix,3,2)+"w.ok")+"' created."
    ENDIF
    $title="Kixtart "+@kix
    ; IF (MessageBox($message, $title, 340, 300) <> 0)
    ; ENDIF
    ? $message
    ENDIF
    break on
    flushkb

    wstart1.kix
    code:
      CLS
    BREAK ON
    IF SetConsole("hide")
    ENDIF
    ;
    ; NT/95 install kixtart - Kixtart 3.62, 3.63, 4.00, 4.01, 4.02, 4.10, 4.11, 4.12, 4.20
    ;
    ; (c) scripting@wanadoo.nl - 2000, 2001, 2002, 2003
    ;
    ; vs 4.01 - program
    ;
    ; 1.00 (20000715) original version. created for IExpress package.
    ; 1.01 (20000715) - additional information written to check-file.
    ; 1.02 (20000715) - additional information about starting script.
    ; system tries to find "c:\temp\kixtart.dbg" file, which will
    ; create a info file "c:\temp\kixtart.txt".
    ; automatic remove of "c:\temp\kixtart.dbg" + "c:\temp\kixtart.txt" by next run.
    ; - change "source_directory" to "c:\temp\ixp000.tmp\",
    ; because "@curdir" is "@homeshr" directory.
    ; - CHANGE iexpress package changed. calling command
    ; "kix32.exe install.kix"
    ; to
    ; "c:\temp\ixp000.tmp\kix32.exe c:\temp\ixp000.tmp\install.kix".
    ; sometime actual drive isn't correct.
    ; 1.03 (20000730) - add HKCR registry entries to 'edit', 'run', 'run debug' + 'print' kixtart scripts.
    ; first it will removing existing HKCR registry entries.
    ; 1.04 (20001025) - update to kixtart 3.63
    ; 2.00 (20010320) - use %tmp% variable as temporary path.
    ; - use @curdir as location of "%temp%\ixp00?.tmp" directory.
    ; - use flexible "kix36?.ok" file.
    ; 2.01 (20010401) - kixtart 2001 beta1 compliancy
    ; - kix32.exe (= console-less version)
    ; - kix32c.exe (= console version)
    ; - introduction of "$debug_file"
    ; - introduction of "$update_ok". all kixtart files
    ; must be available at "$destination_directory".
    ; - check files
    ; - kix400.kix <= kix32.exe
    ; - kix400c.kix <= kix32c.exe (with "kix.console" file)
    ; - introduction of "$kix_console_mode".
    ; - additional information written to eventlog.
    ; 2.02 (20010605) - split script for with/without debugging.
    ; - activate $debug_mode when variable %kix-debug% is declared.
    ; - shows also @curdir value.
    ; - fix: for too late flushing write-buffers on windows95
    ; 2.03 (20011120) - add "windows XP"
    ; 2.04 (20011120) - additional information written to check-file about update/registry mode.
    ; 3.00 (20020110) - remove also .k2k & .udf registry keys by an update.
    ; 3.01 (20020410) - activate $show_mode when variable %kix-show% is declared.
    ; - remove other check-files (del "c:\kix*.ok").
    ; 3.02 (20020530) - convert "kixedit.reg" to internal code.
    ; - move "kedit.ico" to "%systemroot% directory. mostly "c:\windows" or
    ; "c:\winnt" directory.
    ; - change "c:\kix???.ok" location to "%systemroot%\kix???.ok". prevent
    ; permission problems.
    ; for compatibility reasons we create both control files.
    ; 3.03 (20020530) - restyle check-file.
    ; - change "kixedit.reg" to "kedit.ico" as check.
    ; 3.04 (20020805) - implementation of "terminal service" model (input by Kent Dyer)
    ; - additional information about starting script.
    ; system tries to find $system_drive+"temp\kixtart.dbg" file, which will
    ; create a info file $system_drive+"temp\kixtart.txt".
    ; automatic remove of $system_drive+"temp\kixtart.dbg" + $system_drive+"temp\kixtart.txt" by next run.
    ; - change "source_directory" to $system_drive+"temp\ixp000.tmp\"
    ; because "c:" drive not available in a terminal environment.
    ; - UNCHANGE iexpress package changed. calling command
    ; "kix32.exe install.kix".
    ; - remove $debug_file elements. unnecessary.
    ; 3.05 (20020805) - additional information during debugging.
    ; remark: set RedirectOutput($_debug_file,1) in start2.kix file
    ; to overwrite previous content.
    ; 3.06 (20020805) - additional checks during creation and removing file associatios.
    ; f.e. no change of ".scr" when it is already associated (input by Les Ligetfa).
    ; - re-add $debug_file elements.
    ; 3.07 (20020805) - activate $required_mode when variable %kix-only-required% is declared.
    ; 3.08 (20020815) - translate kixtart symbols by kixref specifications.
    ; 4.00 (20030215) - $required_mode becomes default setting (request by Kent Dyer).
    ; environment variable %kix-only-required% becomes obsolete.
    ; - environment variable %kix-complete% makes an installation of all kixtart binaries possible.
    ; 4.01 (20030225) - suppress MessageBox window. with "/I" specified package will hang, when
    ; environment variable "kix-show" was created.
    ;
    ; external variables kix-complete
    ; kix-debug
    ; kix-only-required (obsolete since 4.00)
    ; kix-show
    ;
    $prgrm_version="4.01"
    ;
    IF (@inwin = 1)
    $nt_mode="yes"
    ELSE
    $nt_mode="no"
    ENDIF
    ;
    $tmp_directory=ExpandEnvironmentVars("%tmp%")
    IF (Substr($tmp_directory,Len($tmp_directory),1) <> "\")
    $tmp_directory=$tmp_directory+"\"
    ENDIF
    ;
    $required_mode="yes"
    IF ($nt_mode = "no")
    $required_mode="no"
    ENDIF
    IF (Len(ExpandEnvironmentVars(Chr(37)+"kix-complete"+Chr(37))) <> 0)
    $required_mode="no"
    ENDIF
    $debug_mode="no"
    IF (Len(ExpandEnvironmentVars(Chr(37)+"kix-debug"+Chr(37))) <> 0)
    $debug_mode="yes"
    ENDIF
    $show_mode="no"
    IF (Len(ExpandEnvironmentVars(Chr(37)+"kix-show"+Chr(37))) <> 0)
    $show_mode="yes"
    ENDIF

    ; ---------------------------------------------------------------------------
    ; - site defined settings -
    ; ---------------------------------------------------------------------------

    $debug_file=$tmp_directory+"kixtart.txt"

    ; ---------------------------------------------------------------------------

    $os=""
    $os_dos=@dos
    SELECT
    CASE ($nt_mode = "yes") AND ($os_dos = "5.1") ; - Windows XP -
    $os="XP"
    CASE ($nt_mode = "yes") AND ($os_dos = "5.0") ; - Windows 2000 -
    $os="W2K"
    CASE ($nt_mode = "yes") ; - Windows NT -
    $os="NT4"
    CASE ($nt_mode <> "yes") AND ($os_dos = "4.90") ; - Windows ME -
    $os="ME"
    CASE ($nt_mode <> "yes") AND ($os_dos = "4.10") ; - Windows 98 -
    $os="W98"
    CASE ($nt_mode <> "yes") AND ($os_dos = "4.0") ; - Windows 95 -
    $os="W95"
    CASE 1
    $os="???" ; - undetermined -
    ENDSELECT
    $time_start=@time
    ;
    IF ($debug_mode = "yes")
    BREAK ON
    DEL $debug_file
    IF (RedirectOutput($debug_file,1) = 0)
    ENDIF
    $log_info="Kixtart-UPDATE "+$prgrm_version+" script started."
    IF LogEvent(0, 1, $log_info, "", "Kixtart UPDATE @kix")
    ENDIF
    ELSE
    BREAK OFF
    DEL $debug_file
    IF (RedirectOutput("nul",1) = 0)
    ENDIF
    ENDIF

    IF ($debug_mode = "yes")
    ? "Kixtart "+@kix+" - "+$os+" debug mode (vs "+$prgrm_version+")"+" "+$time_start
    ?
    ENDIF

    ; --------------------------------------------------------------------------
    ; - install kixtart at local workstation -
    ; - -
    ; - 1. calculates source/destination directory -
    ; - 2. check for update -
    ; - - GetFileSize -
    ; - - GetFileTime -
    ; - - GetFileVersion -
    ; - 3. update any kixtart file, when installed version isn't the same. -
    ; - first it removes unwanted fileattributes -
    ; - (hidden, readonly, system) -
    ; - 4a. create information file, which can be checked by batch -
    ; - procedure. it eliminates a unwanted download + installation. -
    ; - 4b. log update information to eventvwr log. -
    ; - -
    ; - call by installation procedure -
    ; - fe. "if not exist %systemroot%\kix362.ok %0\..\kix362update.exe /q" -
    ; - "if not exist %systemroot%\kix420.ok %0\..\kix410update.exe /q" -
    ; - "if not exist %systemroot%\kix420w.ok %0\..\wkix410update.exe /q" -
    ; --------------------------------------------------------------------------

    $source_directory=@curdir
    IF (Substr($source_directory,Len($source_directory),1) <> "\")
    $source_directory=$source_directory+"\"
    ENDIF
    IF ($nt_mode = "yes")
    $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot")
    ELSE
    $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot")
    ENDIF
    IF (Len($destination_directory) = 0)
    $destination_directory=@lanroot
    ENDIF
    IF (Substr($destination_directory,Len($destination_directory),1) <> "\")
    $destination_directory=$destination_directory+"\"
    ENDIF
    $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on -
    ;
    $kix_console_mode="yes" ; - wkix32.exe -
    ;
    $max_kix_files=4
    DIM $kix_files[$max_kix_files+1]
    $kix_files[0]="kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok" ; - check file -
    $kix_files[1]="wkix32.exe"
    $kix_files[2]="kx16.dll"
    $kix_files[3]="kx32.dll"
    $kix_files[4]="kx95.dll"
    ;
    $first_installation="yes"
    IF (Exist($system_drive+$kix_files[0]) = 0)
    DEL $system_drive+"kix*.ok" ; - other installed kixtart versions removing always -
    ENDIF
    IF (Exist($destination_directory+$kix_files[0]) = 1)
    $first_installation="no"
    ELSE
    DEL $destination_directory+"kix*.ok" ; - other installed kixtart versions -
    ENDIF
    ;
    $update="no"
    $update_info=""
    $i=1
    WHILE ($i <= $max_kix_files)
    $source_file=$source_directory+$kix_files[$i]
    $destination_file=$destination_directory+$kix_files[$i]
    IF (Exist($destination_file) = 1)
    IF (SetFileAttr($destination_file, 128) <> 0)
    ENDIF
    IF ($debug_mode = "yes")
    DEL $destination_file ; - activates an automatic update for debugging script -
    ENDIF
    ENDIF
    $update="yes"
    IF (Exist($source_file) = 1)
    $update="no"
    IF (GetFileSize($source_file) <> GetFileSize($destination_file))
    $update="yes"
    ENDIF
    IF (GetFileTime($source_file) <> GetFileTime($destination_file))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"filedescription") <> GetFileVersion($destination_file,"filedescription"))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"fileversion") <> GetFileVersion($destination_file,"fileversion"))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"internalname") <> GetFileVersion($destination_file,"internalname"))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"language") <> GetFileVersion($destination_file,"language"))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"originalfilename") <> GetFileVersion($destination_file,"originalfilename"))
    $update="yes"
    ENDIF
    IF (GetFileVersion($source_file,"productname") <> GetFileVersion($destination_file,"productname"))
    $update="yes"
    ENDIF
    ENDIF
    ;
    IF ($update = "yes") OR ($debug_mode = "yes")
    COPY $source_file $destination_file /h
    $update_info=$update_info+" +"+Lcase($kix_files[$i])
    ELSE
    $update_info=$update_info+" ="+Lcase($kix_files[$i])
    ENDIF
    IF (@error <> 0)
    ? "Warning INSTALL: error "+@error+" ("+@serror+")"
    ENDIF
    IF ($debug_mode = "yes")
    ? "Informative INSTALL: copy "+Lcase($source_file)+" "+Lcase($destination_file)
    ?
    ? " size.old = "+GetFileSize($source_file)
    ? " size.new = "+GetFileSize($destination_file)
    ? " time.old = "+GetFileTime($source_file)
    ? " time.new = "+GetFileTime($destination_file)
    ?
    ? " company name "+GetFileVersion($source_file,"company name")
    ? " filedescription "+GetFileVersion($source_file,"filedescription")
    ? " fileversion "+GetFileVersion($source_file,"fileversion")
    ? " internalname "+GetFileVersion($source_file,"internalname")
    ? " language "+GetFileVersion($source_file,"language")
    ? " legalcopyright "+GetFileVersion($source_file,"legalcopyright")
    ? " legaltrademarks "+GetFileVersion($source_file,"legaltrademarks")
    ? " originalfilename "+GetFileVersion($source_file,"originalfilename")
    ? " privatebuild "+GetFileVersion($source_file,"privatebuild")
    ? " productname "+GetFileVersion($source_file,"productname")
    ? " productversion "+GetFileVersion($source_file,"productversion")
    ? " specialbuild "+GetFileVersion($source_file,"specialbuild")
    ?
    ENDIF
    $i=$i+1
    IF ($nt_mode = "yes") AND ($required_mode = "yes")
    $i=$max_kix_files+1
    ENDIF
    LOOP
    ;
    IF ($nt_mode = "yes") AND ($required_mode = "yes")
    $i=2 ; - remove DLL's -
    WHILE ($i <= $max_kix_files)
    $destination_file=$destination_directory+$kix_files[$i]
    IF (Exist($destination_file) = 1)
    IF (SetFileAttr($destination_file, 128) <> 0)
    ENDIF
    DEL $destination_file
    $update_info=$update_info+" -"+Lcase($kix_files[$i])
    ELSE
    $update_info=$update_info+" ?"+Lcase($kix_files[$i])
    ENDIF
    $i=$i+1
    LOOP
    ENDIF
    ;
    IF ($debug_mode = "yes")
    DEL $system_drive+$kix_files[0] ; - activates an automatic update for debugging script -
    DEL $destination_directory+$kix_files[0] ; - other installed kixtart versions -
    ENDIF
    ;
    $update_ok="yes" ; - all kixtart files must be available at $destination_directory -
    $i=1
    WHILE ($i <= $max_kix_files)
    $destination_file=$destination_directory+$kix_files[$i]
    IF (Exist($destination_file) <> 1)
    $update_ok="no"
    $update_info=$update_info+" unknown_file."+Lcase($kix_files[$i])
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", Lcase($kix_files[$i]), @date+" "+@time+" -> unknown file")
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", Lcase($kix_files[$i]), @date+" "+@time+" -> unknown file")
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - "+Lcase($kix_files[$i])+" - "+@date+" "+@time+" -> unknown file"
    ENDIF
    ELSE
    $build_info=GetFileVersion($destination_file,"specialbuild")
    IF (Len($build_info) <> 0)
    $build_info=" ("+Lcase($build_info)+")"
    ELSE
    $build_info=""
    ENDIF
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", Lcase($kix_files[$i]), @date+" "+@time+" -> "+GetFileTime($destination_file)+" "+GetFileSize($destination_file)+$build_info)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", Lcase($kix_files[$i]), @date+" "+@time+" -> "+GetFileTime($destination_file)+" "+GetFileSize($destination_file)+$build_info)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - "+Lcase($kix_files[$i])+" - "+@date+" "+@time+" -> "+GetFileTime($destination_file)+" "+GetFileSize($destination_file)+$build_info
    ENDIF
    ENDIF
    $i=$i+1
    IF ($nt_mode = "yes") AND ($required_mode = "yes")
    $i=$max_kix_files+1
    ENDIF
    LOOP
    $i=$max_kix_files
    IF ($update_ok = "yes")
    $update_info="("+Ltrim(Rtrim(Lcase($update_info)))+") to "+'"'+Ltrim(Rtrim(Lcase($destination_directory)))+'"'
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", "KiXtart", "installation completed at "+@date+" "+@time+" "+$update_info)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", "KiXtart", "installation completed at "+@date+" "+@time+" "+$update_info)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - "+Lcase($kix_files[$i])+" - installation completed at "+@date+" "+@time+" "+$update_info
    ENDIF
    ELSE
    $update_info="("+Ltrim(Rtrim(Lcase($update_info)))+") to "+'"'+Ltrim(Rtrim(Lcase($destination_directory)))+'"'
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", "KiXtart", "installation incompleted at "+@date+" "+@time+" "+$update_info)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", "KiXtart", "installation incompleted at "+@date+" "+@time+" "+$update_info)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - "+Lcase($kix_files[$i])+" - installation incompleted at "+@date+" "+@time+" "+$update_info
    ENDIF
    ENDIF
    IF ($update_ok <> "yes")
    IF (Exist($system_drive+$kix_files[0]) = 1)
    IF ($debug_mode <> "yes")
    DEL $system_drive+$kix_files[0] ; - kixtart version is incompleted -
    ENDIF
    ENDIF
    IF (Exist($destination_directory+$kix_files[0]) = 1)
    IF ($debug_mode <> "yes")
    $destination_directory+$kix_files[0] ; - kixtart version is incompleted -
    ENDIF
    ENDIF
    ENDIF

    ; --------------------------------------------------------------------------
    ; - HKCR no registry update -
    ; --------------------------------------------------------------------------

    IF ($debug_mode = "yes")
    ? " =>"
    ? " => .kix "+ReadValue("HKEY_CLASSES_ROOT\.kix","")
    ? " => .k2k "+ReadValue("HKEY_CLASSES_ROOT\.k2k","")
    ? " => .scr "+ReadValue("HKEY_CLASSES_ROOT\.scr","")
    ? " => .udf "+ReadValue("HKEY_CLASSES_ROOT\.udf","")
    ? " => kix32 document "+ReadValue("HKEY_CLASSES_ROOT\kix32 document\Shell","")
    ? " =>"
    ENDIF
    ;
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", "KiXtart release", $os+" -> kix "+@kix)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", "KiXtart release", $os+" -> kix "+@kix)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - KiXtart release - "+$os+" -> kix "+@kix
    ENDIF
    IF ($required_mode = "yes")
    $message=" (only required files)"
    ELSE
    $message=""
    ENDIF
    IF (Exist($source_directory+"kedit.ico") = 1)
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", "KiXtart mode", "registry"+$message)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", "KiXtart mode", "registry"+$message)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - KiXtart mode - registry"+$message
    ENDIF
    ELSE
    IF WriteProfileString($system_drive+$kix_files[0], "KiXtart", "KiXtart mode", "update"+$message)
    ENDIF
    IF WriteProfileString($destination_directory+$kix_files[0], "KiXtart", "KiXtart mode", "update"+$message)
    ENDIF
    IF ($debug_mode = "yes")
    ? " => KiXtart - KiXtart mode - update"+$message
    ENDIF
    ENDIF

    ; --------------------------------------------------------------------------
    ; - end -
    ; --------------------------------------------------------------------------

    :end_script
    $time_stop=@time
    IF ($update = "yes")
    $log_info="Kixtart-UPDATE "+$prgrm_version+" script completed successfully"
    $log_info=$log_info+" ("+$time_start+" - "+$time_stop+") "+Ltrim(Rtrim($update_info))
    IF ($kix_console_mode = "yes")
    $log_info=$log_info+" (CONSOLE-LESS)"
    ENDIF
    IF ($debug_mode = "yes")
    ?
    ? " logevent = "+$log_info
    ?
    ENDIF
    IF ($update_ok = "yes")
    IF LogEvent(0, 1, $log_info, "", "Kixtart UPDATE @kix"+"c")
    ENDIF
    ELSE
    IF LogEvent(0, 1, $log_info, "", "Kixtart UPDATE @kix"+"e")
    ENDIF
    ENDIF
    ENDIF
    IF ($update_ok = "yes")
    $update_ok=""
    ELSE
    $update_ok="in"
    ENDIF
    IF ($kix_console_mode = "yes")
    ? "Kixtart "+@kix+" (console-less) update "+$update_ok+"completed. ('"+$source_directory+"' -> '"+$destination_directory+"')"
    ELSE
    ? "Kixtart "+@kix+" update "+$update_ok+"completed. ('"+$source_directory+"' -> '"+$destination_directory+"')"
    ENDIF
    IF (RedirectOutput("CON") = 0)
    ENDIF
    IF ($kix_console_mode = "yes")
    ? "Kixtart "+@kix+" (console-less) update "+$update_ok+"completed. ('"+$source_directory+"' -> '"+$destination_directory+"')"
    ELSE
    ? "Kixtart "+@kix+" update "+$update_ok+"completed. ('"+$source_directory+"' -> '"+$destination_directory+"')"
    ENDIF
    ?
    IF ($debug_mode = "yes")
    ? "Informative INSTALL: create debug list '"+$debug_file+"'"
    ELSE
    ? "Informative INSTALL: no creation of debug list '"+$debug_file+"'"
    ENDIF
    :end
    IF ($show_mode = "yes")
    $title="KiXtart "+@kix+" (CONSOLE-LESS version)"
    $message=""
    IF ($first_installation = "yes")
    IF (Exist($system_drive+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1) OR (Exist($destination_directory+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1)
    $message="Installation of KiXtart "+@kix+" completed"
    ELSE
    $message="Installation of KiXtart "+@kix+" incompleted"
    ENDIF
    ELSE
    IF (Exist($system_drive+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1) OR (Exist($destination_directory+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1)
    $message="Installation of KiXtart "+@kix+" completed"
    ELSE
    $message="Installation of KiXtart "+@kix+" incompleted"
    ENDIF
    ENDIF
    ? $message
    IF (Len($message) <> 0)
    IF (Exist($source_directory+"kedit.ico") = 1)
    $message=$message+" (registry mode - "+Lcase($destination_directory)+")."
    ELSE
    $message=$message+" (update mode - "+Lcase($destination_directory)+")."
    ENDIF
    IF ($required_mode = "yes")
    $message=$message+" only required files."
    ENDIF
    ; IF (MessageBox($message, $title, 340, 15) <> 0)
    ; ENDIF
    ENDIF
    ENDIF
    BREAK ON
    FLUSHKB
    ;
    IF (Exist($system_drive+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1) OR (Exist($destination_directory+"kix"+Substr(@kix,1,1)+Substr(@kix,3,2)+"w.ok") = 1)
    EXIT(0)
    ELSE
    EXIT(1)
    ENDIF

    As console-less SED file we are using now (wkix???update.sed)
    code:
    [Version]
    Class=IEXPRESS
    SEDVersion=3
    [Options]
    PackagePurpose=InstallApp
    ShowInstallProgramWindow=1
    HideExtractAnimation=1
    UseLongFileName=0
    InsideCompressed=0
    CAB_FixedSize=0
    CAB_ResvCodeSigning=0
    RebootMode=N
    InstallPrompt=%InstallPrompt%
    DisplayLicense=%DisplayLicense%
    FinishMessage=%FinishMessage%
    TargetName=%TargetName%
    FriendlyName=%FriendlyName%
    AppLaunched=%AppLaunched%
    PostInstallCmd=%PostInstallCmd%
    AdminQuietInstCmd=%AdminQuietInstCmd%
    UserQuietInstCmd=%UserQuietInstCmd%
    SourceFiles=SourceFiles
    [Strings]
    InstallPrompt=
    DisplayLicense=
    FinishMessage=
    TargetName=X:\wkix420update.exe
    FriendlyName=Kixtart 4.20/4.01 installation at local workstation (console-less version)
    AppLaunched=wkix32.exe /i dummy.kix
    PostInstallCmd=wkix32.exe /i winstall.kix
    AdminQuietInstCmd=
    UserQuietInstCmd=
    FILE0="winstall.kix"
    FILE1="kx16.dll"
    FILE2="kx32.dll"
    FILE3="kx95.dll"
    FILE4="wkix32.exe"
    FILE5="wstart1.kix"
    FILE6="wstart2.kix"
    FILE7="dummy.kix"

    [SourceFiles]
    SourceFiles0=X:\

    [SourceFiles0]
    %FILE0%=
    %FILE1%=
    %FILE2%=
    %FILE3%=
    %FILE4%=
    %FILE5%=
    %FILE6%=
    %FILE7%=

    As console SED file we are using now (kix???update.sed)
    code:
    [Version]
    Class=IEXPRESS
    SEDVersion=3
    [Options]
    PackagePurpose=InstallApp
    ShowInstallProgramWindow=1
    HideExtractAnimation=1
    UseLongFileName=0
    InsideCompressed=0
    CAB_FixedSize=0
    CAB_ResvCodeSigning=0
    RebootMode=N
    InstallPrompt=%InstallPrompt%
    DisplayLicense=%DisplayLicense%
    FinishMessage=%FinishMessage%
    TargetName=%TargetName%
    FriendlyName=%FriendlyName%
    AppLaunched=%AppLaunched%
    PostInstallCmd=%PostInstallCmd%
    AdminQuietInstCmd=%AdminQuietInstCmd%
    UserQuietInstCmd=%UserQuietInstCmd%
    SourceFiles=SourceFiles
    [Strings]
    InstallPrompt=
    DisplayLicense=
    FinishMessage=
    TargetName=X:\kix420update.exe
    FriendlyName=Kixtart 4.20/4.00 installation at local workstation (console version)
    AppLaunched=kix32.exe dummy.kix
    PostInstallCmd=kix32.exe install.kix
    AdminQuietInstCmd=
    UserQuietInstCmd=
    FILE0="install.kix"
    FILE1="kix32.exe"
    FILE2="kx16.dll"
    FILE3="kx32.dll"
    FILE4="kx95.dll"
    FILE5="start1.kix"
    FILE6="start2.kix"
    FILE7="dummy.kix"

    [SourceFiles]
    SourceFiles0=X:\

    [SourceFiles0]
    %FILE0%=
    %FILE1%=
    %FILE2%=
    %FILE3%=
    %FILE4%=
    %FILE5%=
    %FILE6%=
    %FILE7%=

    For client upgrade information see

    Kix upgrade: what are those new features? can upgrade be done without any danger?

    When you are using the way we are upgrading you get more information about what was going wrong.

    On our site you can find packages for a lot of Kixtart versions.
    Currently available
    - kix362update.exe
    - kix363update.exe
    - kix402update.exe
    - kix410update.exe
    - kix411update.exe
    - kix412update.exe
    - kix420update.exe

    After completion an installation you will get a control file with information
    about what was done.
    An example
    code:
    [KiXtart]
    kix32.exe=2003/02/18 03:28:15 -> 2003/02/16 00:00:00 237568 (build 129)
    kx16.dll=2003/02/18 03:28:15 -> 2001/08/27 00:00:00 47104
    kx32.dll=2003/02/18 03:28:15 -> 2002/03/29 00:00:00 49152
    kx95.dll=2003/02/18 03:28:15 -> 2002/11/11 00:00:00 49152 (build 003)
    KiXtart=installation completed at 2003/02/18 03:28:15 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
    KiXtart release=ME -> kix 4.20
    KiXtart mode=update

    greetings.

    btw: symbol  - on our pages has been linked to related http://kixtart.org topic.

    btw: modifications based in input from kdyer


    MCA
    (KiX Supporter)
    2003-02-27 01:26 AM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    Now TO_DO_completed. Last issue incorporated in new topic. Topic F14-429.
    greetings.

    (please don't move this topic to another forum)


    MCA
    (KiX Supporter)
    2003-10-16 08:06 PM
    Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities

    Dear,

    Add new kix422update.exe & kix422registry.exe. Compliant with KiXtart 4.22 release candidate 1.
    Update of kix420update.exe, kix421update.exe, kix420registry.exe & kix421registry.exe.

    An example of check file.
    code:
    [KiXtart]
    kix32.exe=2003/10/10 01:28:56 -> 2003/08/25 16:32:07 241664 (build 137)
    kx16.dll=2003/10/10 01:28:56 -> 2001/08/27 20:17:29 47104
    kx32.dll=2003/10/10 01:28:56 -> 2002/03/29 12:38:08 49152
    kx95.dll=2003/10/10 01:28:56 -> 2002/11/11 08:50:03 49152 (build 003)
    KiXtart=installation completed at 2003/10/10 01:28:56 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
    KiXtart release=Windows Me -> kix 4.22 Release Candidate 1
    KiXtart mode=registry

    greetings.

    btw: Also wkix422update.exe, wkix421update.exe & wkix420update.exe has been updated.