Dear,
Take a look at the iexpress documentation we have created. It contains
the steps and input we are using for the creation of a new iexpress
update package.
Of course we doesn't have any problem with it to create your own version.
Possible problems with some of you are:
- we want to install only the file kix32.exe for the NTx environments.
- we want to install them on another location than the "c:\windows" or "c:\winnt"
directory (= %windir% directory).
- requirements for wkix402update are different.
Our point for above issues:
- all packages should work for all windows versions. also the newer one we doesn't
know yet.
- all packages should clear in their task. the defined environment variables are
more for the experience kixtart users.
- we must choose a location which will contain always the right rights.
- installation doesn't or may not required additional actions before it comes
active. f.e.your script can return unexpected result when your kixtart binaries
are located in a new directory which isn't an element of the default PATH set-
ting .
- at least the other feedback influence it also.
Of course we are very interesting in the way you have implement your own
version.
Lonkero, can you mail me your version of "wkixcheck" and "wkixupdates".
Les, your ideas aren't gone. Still some things in our mail box. Your idea
about a separate script for creating or removing file associations we like. For
backwards compatibility it will take a little bit longer. It is high on our prio-
rity list by new update. New updates will created after the release of a new
kixtart release.
we keep kixupdate and wkixupdate as separate file for the general
users. For them it is very clear what will happen:
- wkixupdate will install "wkix32.exe"
- kixupdate will install "kix32.exe"
they don't like all kind of environment variables which can influence the
way of installation for all windows and kixtart versions.
greetings.
(TO_DO)
