#50747 - 2000-07-27 05:48 AM
KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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).]
|
Top
|
|
|
|
#50748 - 2000-07-30 07:48 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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).]
|
Top
|
|
|
|
#50750 - 2001-03-22 11:28 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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 .
|
Top
|
|
|
|
#50751 - 2001-03-23 03:03 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
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:14Informative 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.
|
Top
|
|
|
|
#50760 - 2002-04-11 04:04 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
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
|
|
|
|
#50761 - 2002-06-20 11:52 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
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) [ 20 June 2002, 23:52: Message edited by: MCA ]
|
Top
|
|
|
|
#50762 - 2002-07-08 08:31 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Now compliant with Kixtart 4.10 final release (build 98)
|
Top
|
|
|
|
#50763 - 2002-07-08 10:13 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Now compliant with Kixtart 4.10 final release (build 99)
|
Top
|
|
|
|
#50764 - 2002-07-19 12:02 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
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
|
|
|
|
#50765 - 2002-08-15 02:18 AM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
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
|
|
|
|
#50766 - 2002-08-15 09:32 PM
Re: KIXTART-REGISTRY: create kix associations for edit/run capabilities
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
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
|
Top
|
|
|
|
Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 557 anonymous users online.
|
|
|