Dear Les,
You make some good points. Some answers and questions about it:
- In previous versions, you included the DLLs regardless of platform. Do you intend
to install the DLLs only on Wintendo with the new version?
Answer:
It has impact on all kind of other tools and script of our site, which doesn't mean
we are thinking about it. Ruud advise also not install them in a none windows9x envi-
ronment.
We put in on our TO-DO list. - In previous versions you bundled KiX32 and WKiX32 separately. Do you plan to
change that and have both in one package?
Answer:
In an earlier reaction we want to keep it clear which version you are installing.
- WKIX32 may not influence KIX32
- for the not-experts the installation must be clear
Questions:
- what is the actual goal for combining them?
- are you trying to install both versions at the same time or to install only one
version based on specified parameter? we are also restricted by the way iexpress
software is working.
A possible way of passing information through installation script is by using
environment variables like kix-debug and kix-show. - In previous versions you would explicitly remove associations to .SCR that could
affect screensavers. Do you plan to leave the registry alone in the new version?
Answer:
it is a good point. For our environments the SCR association isn't necessary.
All our scripts are using KIX or K2K as extension.
Indeed it isn't always necessary to change or to remove file associations. We suggest
to remove only those file associations, when they were created by the kixregistry
version.
Also we suggest to remove SCR association for the Kixtart 4.x releases.
The Kixtart 3.x releases are all using the SCR extension.
Question:
- what is the problem for your environment when the scr association is gone
or modified? File associations are useful for a fast and easy way of opening a
specific file type. - In previous versions, the errorlevel returned could not be trusted. Will the
new version correctly return errorlevel?
Answer:
- some things of kixcheck and wkixcheck are already on our TO-DO list, which
makes it easier and more accurate to recognize your kixtart environment.
Questions:
- what are you meaning with "the errorlevel returned could not be trusted"? do you have
an example?
- did the control file kix???.ok contains the actual and correct status? can you
run the installation with following script
code:
@echo off
set kix-debug=ok
%0\..\kix410update.exe /q
rem -
rem - rest of your script -
rem -
@echo off
and return the debugging output and control file on the board or as mail.
Your suggestions will put on our list, but an implementation must have to wait during
our vacation.
Of course in some situations we love some additional information from you.
greetings.
btw: kdyer suggestions will be implemented before our vacation.
(TO_DO)
[ 30 July 2002, 03:21: Message edited by: MCA ]
