#50400 - 2002-04-11 04:01 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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???.okcode:
[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.
|
Top
|
|
|
|
#50401 - 2002-06-20 11:50 PM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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)
|
Top
|
|
|
|
#50402 - 2002-07-08 08:32 PM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Now compliant with Kixtart 4.10 final release (build 98)
|
Top
|
|
|
|
#50403 - 2002-07-08 10:14 PM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Now compliant with Kixtart 4.10 final release (build 99)
|
Top
|
|
|
|
#50404 - 2002-07-19 12:01 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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.
|
Top
|
|
|
|
#50405 - 2002-08-15 02:17 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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.
|
Top
|
|
|
|
#50406 - 2002-10-07 06:46 PM
Re: .KIX -> .EXE: Package and compact your script...
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
As a follow-up to the update - Deployment of Kix Scripts.
Made the following modifications to the INSTALL.KIX file:
code:
IF (@inwin = 1) $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE SHELL "%comspec% /c md "+$destination_directory ENDIF ELSE $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE SHELL "%comspec% /c md "+$destination_directory ENDIF ENDIF
In the START1.KIX, made the following modification:
code:
IF ($nt_mode = "yes") $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE SHELL "%comspec% /c md "+$destination_directory ENDIF ELSE $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE SHELL "%comspec% /c md "+$destination_directory ENDIF ENDIF
Thanks!
Kent
|
Top
|
|
|
|
#50407 - 2002-11-15 02:11 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Now compliant with - Kixtart 4.11 final release (build 104) - Kixtart 4.12 final release (build 112) greetings. [ 01. December 2002, 08:08: Message edited by: MCA ]
|
Top
|
|
|
|
#50408 - 2002-11-15 02:22 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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.
|
Top
|
|
|
|
#50409 - 2002-12-01 08:04 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Kent,
Would it be nice for your situation, when the iexpress package creates also the subdirectory scripts?
Also we understand that in your environment kixtart is installing in a correct way. That means: - within W9x environment also the necessary DLL's will be installed. - within NTx environment only the KIX32.EXE will be installed. After confirmation by you we will change our script in such a way, that it isn't necessary to specify an environment variable for it.
Please confirm our request. greetings.
(other related topic F2-639) [ 01. December 2002, 08:09: Message edited by: MCA ]
|
Top
|
|
|
|
#50411 - 2002-12-01 08:10 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Thanks Lonkero. Already correct it.
|
Top
|
|
|
|
#50412 - 2002-12-05 05:46 PM
Re: .KIX -> .EXE: Package and compact your script...
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
quote:
Also we understand that in your environment kixtart is installing in a correct way. That means: - within W9x environment also the necessary DLL's will be installed. - within NTx environment only the KIX32.EXE will be installed. After confirmation by you we will change our script in such a way, that it isn't necessary to specify an environment variable for it.
These are correct. I believe the DLL being unecessary has been talked about.
(1) Why copy the DLLs when not used in an NT Environment? (2) Why Associate .KIX, .KX, .UDF files unless you are a "scripter" like you and me? (3) The C:\Scripts folder change I implemented below is because we ran into a security issue when a "locked down" user could not write a file even to %windir%.
Here are the changes made to the package:
>> ISNTALL.KIX << Original -
code:
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
Change to -
code:
IF ($nt_mode = "yes") $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE MD $destination_directory ENDIF ELSE $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE MD $destination_directory ENDIF ENDIF
>> START1.KIX <<
Original -
code:
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
Change to -
code:
IF ($nt_mode = "yes") $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows NT\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE MD $destination_directory ENDIF ELSE $destination_directory=ReadValue("HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion", "SystemRoot") $system_drive=Substr($destination_directory,1,3) ; - This will show C: or M: or what drive windows is installed on - $destination_directory=$system_drive+"\Scripts" IF GETFILEATTR($destination_directory) & 16 ELSE MD $destination_directory ENDIF ENDIF
Change $update="no"
For the Registry..
Add in a line - $associat = "No"
Above - $required_mode="no"
IF $associat = "Yes"
Add in an ENDIF below -
code:
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 ENDIF ;>> Added
Thanks,
Kent
|
Top
|
|
|
|
#50413 - 2002-12-05 06:20 PM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
We will make it possible that anyone will have the capability to install all kixtart files regardless NT or not. In our opinion the iexpress package should be bullet-proof for new windows releases. It is possible that a new release requires all files.
As reaction on (1) after releasing a new version it will only copy necessary kixtart files to client. For NTx only kix32.exe and for W9x also the DLLs.
With the new release no environment variable is necessary for above way of installation.
(2) for the general users (= none "scripters") we are using always the kix???update.exe version for installation. we are removing existing file associations with during these installation. Only the kix???registry.exe will create kixtart file associations.
(3) we will think about "how to implement this".
Kent, can you mail me those kixtart scripts? Later this month we try to have the new releases. At the same time we try to have documentation about the way it can and should use. At the moment we read many times the same questions. Of course we will send you for testing a copy of the new one, before ma- king them public.
Thanks and greetings.
|
Top
|
|
|
|
#50415 - 2002-12-05 11:14 PM
Re: .KIX -> .EXE: Package and compact your script...
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
|
Top
|
|
|
|
#50416 - 2003-01-20 02:02 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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.
|
Top
|
|
|
|
#50417 - 2003-10-16 08:07 PM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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
Now available by
Summary of Site & Home - Kix Downloads
pages greetings.
btw: Also wkix422update.exe, wkix421update.exe & wkix420update.exe has been updated.
|
Top
|
|
|
|
#50419 - 2003-10-17 03:54 AM
Re: .KIX -> .EXE: Package and compact your script...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
Of course, that was possible.
Sometime people were asking "where are the new packages for kixtart 4.22 release". For those beta-testers it can be handy.
With previous upgrades it was a very simple process to create those package. By changing the @kix layout we MUST not only modify our internal scripts, but also the kixstrip program for the debugging part. Now the process is the same again.
When Ruud goes for GOLD we can distribute that version with related package very fast. greetings.
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
1 registered
(Allen)
and 382 anonymous users online.
|
|
|