Dear,

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

We are using our iexpress package to install kixtart binaries on our clients.
After completion an installation you will get a control file with information
about what was done.
An example
code:
[KiXtart]
kix32.exe=2003/01/19 01:09:56 -> 2003/01/10 13:12:09 237568 (build 123)
kx16.dll=2003/01/19 01:09:56 -> 2001/08/27 19:17:29 47104
kx32.dll=2003/01/19 01:09:56 -> 2002/03/29 11:38:08 49152
kx95.dll=2003/01/19 01:09:56 -> 2002/11/11 07:50:03 49152 (build 003)
KiXtart=installation completed at 2003/01/19 01:09:56 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
KiXtart release=ME -> kix 4.20 Release Candidate 1
KiXtart mode=registry

For more information see

Kix upgrade: what are those new features? can upgrade be done without any danger?
.KIX -> .EXE: Package and compact your script...

greetings.

btw: symbol  - on our pages has been linked to related http://kixtart.org topic.
_________________________
email scripting@wanadoo.nl homepage scripting@wanadoo.nl | Links | Summary of Site Site KiXforms FAQ kixtart.org library collection mirror MCA | FAQ & UDF help file UDF kixtart.org library collection mirror MCA | mirror USA | mirror europe UDF scriptlogic library collection UDFs | mirror MCA