#98493 - 2003-02-18 04:10 AM
WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
I am trying to get an IExpress Package put together to deploy WKIX32.EXE in our Enterprise.
Here is the WKIX32UPDATE.SED file that I created using MCA's packager as the basis this project.
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=C:\Documents and Settings\Kent\!KIX\wkixpkg\wkix420update.exe
FriendlyName=WKixtart 4.20 installation
AppLaunched=WKIX32
PostInstallCmd=WKIX32 WINSTALL
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="WSTART1.KIX"
FILE1="WINSTALL.KIX"
FILE2="KX16.DLL"
FILE3="KX32.DLL"
FILE4="KX95.DLL"
FILE5="WKIX32.EXE"
[SourceFiles]
SourceFiles0=C:\Documents and Settings\Kent\!KIX\wkixpkg\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
%FILE3%=
%FILE4%=
%FILE5%=
The error seems to be around:
AppLaunched=WKIX32
PostInstallCmd=WKIX32 WINSTALL
If I use WKIX32.EXE to start the installation process, it comes up with a message on how to use WKIX32.EXE. However, I use KIX32.EXE to deploy the files, it does work fine. It would be preferred to use WKIX32.EXE to do this.
I have tried -
Standard executable:
PostInstallCmd=WKIX32.EXE WINSTALL.KIX
Surrounding with Quotes:
PostInstallCmd="WKIX32 WINSTALL"
Using %COMSPEC%:
PostInstallCmd=%COMSPEC% /C WKIX32 WINSTALL
Using a %TEMP% variable:
PostInstallCmd=%TEMP%\IPX0001.TMP\WKIX32 %TEMP%\IPX0001.TMP\WINSTALL
Quotes with %TEMP%:
PostInstallCmd="%temp%\ipx0001.tmp\WKIX32.EXE" "%temp%\ipx0001.tmp\WINSTALL.KIX"
PostInstallCmd=WKIX32.EXE "%temp%\ipx0001.tmp\WINSTALL.KIX"
PostInstallCmd=WKIX32.EXE %temp%\ipx0001.tmp\WINSTALL.KIX
I also went to the http://support.microsoft.com/?kbid=190053 site, which seemed to have no insight to my issue either.
It seems that I am missing something here.
Thanks,
Kent
|
|
Top
|
|
|
|
#98494 - 2003-02-18 04:58 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Kent,
We have prepared the new versions. It will now only install the necessary kixtart binaries.
Only kix32.exe on NTx environments.
Our new sed file for wkix32 installation 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=X:\wkix420update.exe
FriendlyName=Kixtart 4.20/4.00 installation at local workstation (console-less version)
AppLaunched=kix32.exe
PostInstallCmd=kix32.exe winstall.kix
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="winstall.kix"
FILE1="kix32.exe"
FILE2="kx16.dll"
FILE3="kx32.dll"
FILE4="kx95.dll"
FILE5="wkix32.exe"
FILE6="wstart1.kix"
FILE7="wstart2.kix"
[SourceFiles]
SourceFiles0=X:\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
%FILE3%=
%FILE4%=
%FILE5%=
%FILE6%=
%FILE7%=
Of course you see we are installing it with kix32.exe.
Of course wkix32.exe should work also.
Some comment on your calls
- don't specify %TEMP% and \IPX0001.TMP\ in PostInstallCmdf.e. IPX0001.TMP isn't always the same value.
Default it is looking in temporary IPX000x.tmp directory. - missing call: start /w wkix32.exe winstall.kix
greetings.
|
|
Top
|
|
|
|
#98495 - 2003-02-18 05:26 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
Still no go..
"Cannot find file specified.." When using WKIX32.EXE.
Tried both -
AppLaunched=WKIX32.EXE
PostInstallCmd=WKIX32.EXE WINSTALL.KIX
AppLaunched=WKIX32.EXE
PostInstallCmd=%COMSPEC% /C START /W WKIX32.EXE WINSTALL.KIX
Thanks,
Kent
|
|
Top
|
|
|
|
|
#98496 - 2003-02-18 05:31 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
We suggest
code:
AppLaunched=WKIX32.EXE
PostInstallCmd=START /W WKIX32.EXE WINSTALL.KIX
greetings.
|
|
Top
|
|
|
|
#98497 - 2003-02-18 05:41 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
That shows me the help screen on how to launch WKIX32.EXE.
Once the Help screen closes, we see:
quote:
Wkixtart 4.20 installation
Error creating process <START /W WKIX32.EXE WINSTALL.KIX>. Reason: The system cannot find the file specified.
Here is my current .SED File:
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=C:\!KIX\wkixpkg\wkix420update.exe
FriendlyName=WKixtart 4.20 installation
AppLaunched=WKIX32.EXE
PostInstallCmd=START /W WKIX32.EXE WINSTALL.KIX
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="WSTART1.KIX"
FILE1="WINSTALL.KIX"
FILE2="KX16.DLL"
FILE3="KX32.DLL"
FILE4="KX95.DLL"
FILE5="WKIX32.EXE"
[SourceFiles]
SourceFiles0=C:\!KIX\wkixpkg\
[SourceFiles0]
%FILE0%=
%FILE1%=
%FILE2%=
%FILE3%=
%FILE4%=
%FILE5%=
Thanks,
Kent
|
|
Top
|
|
|
|
|
#98498 - 2003-02-18 05:57 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
After publication of the new files and additional information on the board we will
start immediatly with your problem.
Already the new wkix420update.exe file is available on our site. Same link.
greetings.
|
|
Top
|
|
|
|
#98499 - 2003-02-18 06:04 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
OK for now, I can use KIX32 to deploy WKIX32.
Kent
|
|
Top
|
|
|
|
|
#98500 - 2003-02-18 06:09 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
That is the way we are doing it too, but it should be possible with wkix32 also.
greetings.
|
|
Top
|
|
|
|
#98501 - 2003-02-18 06:12 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
I think we are talking "apples to oranges" here. Remember, WKIX32.EXE is a "console-less" version of KiXtart.
You are right in the sense that it "should" work possibly with an /i (invisible-mode) switch.
Thanks,
Kent
|
|
Top
|
|
|
|
|
#98502 - 2003-02-18 06:17 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
Indeed it aren't the same things, but a wkix32 call should work with the right parameters.
btw: on which windows version you are testing it?
greetings.
|
|
Top
|
|
|
|
|
#98503 - 2003-02-18 06:19 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
MCA,
Windows XP - SP-1.
Kent
|
|
Top
|
|
|
|
|
#98504 - 2003-02-21 01:27 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Kent,
We have manipulate our SED file a little bit. We are running
it first on windows me system with
code:
AppLaunched=wkix32.exe
PostInstallCmd=wkix32.exe winstall.kix
This installation works find for windows ME. Debug results
code:
[KiXtart]
wkix32.exe=2003/02/20 22:20:58 -> 2003/02/16 00:00:00 237568 (build 129)
kx16.dll=2003/02/20 22:20:58 -> 2001/08/27 00:00:00 47104
kx32.dll=2003/02/20 22:20:58 -> 2002/03/29 00:00:00 49152
kx95.dll=2003/02/20 22:20:58 -> 2002/11/11 00:00:00 49152 (build 003)
KiXtart=installation completed at 2003/02/20 22:20:58 (+wkix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
KiXtart release=ME -> kix 4.20
KiXtart mode=update
and a part of debugging output is
code:
-thursday 2003/02/20 22:20:57- kixtart 4.20/4.00e script starting (wstart2.kix)
-
-curdir: c:\temp\ixp000.tmp
-scriptdir: c:\temp\ixp000.tmp
-startdir: c:\temp\ixp000.tmp
-
-userid: MCA/MCA
-user priv: guest
-version: inwin=2/dos=4.90/productsuite=0/producttype=Windows Me/csd=
-
-debug file: c:\temp\kixdebug.txt
-debug name: 20030220_222057.820_2716
-
----- start-22:20:57-20030220_222057.820_2716 - 0 The operation completed successfully.
.
.
Kixtart 4.20 (console-less) update completed. ('c:\temp\IXP000.TMP\' -> 'C:\WINDOWS\')
- 464-22:20:58-20030220_222057.820_2716 - 120 This function is not supported on this system.
- 467-22:20:58-20030220_222057.820_2716 - 120 This function is not supported on this system.
With
code:
AppLaunched=wkix32.exe
PostInstallCmd=wkix32e.exe winstall.kix
we get
code:
Error creating process <wkix32e.exe winstall.kix>. Reason: The system cannot find the file specified.
With
code:
AppLaunched=wkix32e.exe
PostInstallCmd=wkix32e.exe winstall.kix
we get
code:
Error creating process <wkix32e.exe>. Reason: The system cannot find the file specified.
Also we see with the tool WinPatrol the message
code:
Do you approve the addition of this program to your computer startup?
Press YES if this program is allowed.
.
Run a DLL as an App 4.90.3000
rundll32.exe c:\windows\system\advpack.dll,DelNodeRunDLL32 c:\temp\IXP001.TMP\
Also the iexpress process will not ending.
With
code:
AppLaunched=
PostInstallCmd=wkix32.exe winstall.kix
we get the message
code:
Error creating process <>. Reason: the specified path is invalid.
On windows XP-SP1 we see with
code:
AppLaunched=wkix32.exe
PostInstallCmd=wkix32.exe winstall.kix
we see also a kixtart help window on our screen.
This was is generated by the AppLaunched specification.
The installation completes in a normal way for the rest.
After changing it to
code:
AppLaunched=kix32.exe
PostInstallCmd=wkix32.exe winstall.kix
FILE0="winstall.kix"
FILE1="kix32.exe"
FILE2="kx16.dll"
FILE3="kx32.dll"
FILE4="kx95.dll"
FILE5="wkix32.exe"
FILE6="wstart1.kix"
FILE7="wstart2.kix"
we doesn't see any problem. Also the package will automatically
executed kix32.exe /? based on AppLaunched specification,
but window isn't opening on your screen and process is terminating
in a normal way.
The control file contains
code:
[KiXtart]
wkix32.exe=2003/02/21 00:22:08 -> 2003/02/16 00:00:00 237568 (build 129)
KiXtart=installation completed at 2003/02/21 00:22:08 (+wkix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
KiXtart release=XP -> kix 4.20
KiXtart mode=update (only required files)
Part of debugging information
code:
-friday 2003/02/21 00:22:08- kixtart 4.20/4.00e script starting (wstart2.kix)
-
-curdir: c:\windows\temp\ixp000.tmp
-scriptdir: c:\windows\temp\ixp000.tmp
-startdir: c:\windows\temp\ixp000.tmp
-
-userid: MCA/MCA
-user priv: admin
-version: inwin=1/dos=5.1/productsuite=256/producttype=Windows XP Professional/csd=Service Pack 1
-
-debug file: C:\WINDOWS\TEMP\kixdebug.txt
-debug name: 20030221_002208.474_1586
-
----- start-00:22:08-20030221_002208.474_1586 - 0 The operation completed successfully.
.
.
Kixtart 4.20 (console-less) update completed. ('C:\WINDOWS\TEMP\IXP000.TMP\' -> 'C:\WINDOWS\')
- 464-00:22:08-20030221_002208.474_1586 - 0 The operation completed successfully.
- 467-00:22:08-20030221_002208.474_1586 - 0 The operation completed successfully.
With specification of dummy program we can reduce our installation
package with about 30 KB.
With
code:
AppLaunched=dummy.exe
PostInstallCmd=wkix32.exe winstall.kix
FILE0="winstall.kix"
FILE1="dummy.exe"
FILE2="kx16.dll"
FILE3="kx32.dll"
FILE4="kx95.dll"
FILE5="wkix32.exe"
FILE6="wstart1.kix"
FILE7="wstart2.kix"
we doesn't see any problem. Also the package will automatically
executed dummy.exe based on AppLaunched specification,
but for a very short time a DOS window shows up.
The control file contains
code:
[KiXtart]
wkix32.exe=2003/02/21 00:23:30 -> 2003/02/16 00:00:00 237568 (build 129)
KiXtart=installation completed at 2003/02/21 00:23:30 (+wkix32.exe ?kx16.dll ?kx32.dll ?kx95.dll) to "c:\windows\"
KiXtart release=XP -> kix 4.20
KiXtart mode=update (only required files)
Part of debugging information
code:
-friday 2003/02/21 00:23:30- kixtart 4.20/4.00e script starting (wstart2.kix)
-
-curdir: c:\windows\temp\ixp000.tmp
-scriptdir: c:\windows\temp\ixp000.tmp
-startdir: c:\windows\temp\ixp000.tmp
-
-userid: MCA/MCA
-user priv: admin
-version: inwin=1/dos=5.1/productsuite=256/producttype=Windows XP Professional/csd=Service Pack 1
-
-debug file: C:\WINDOWS\TEMP\kixdebug.txt
-debug name: 20030221_002330.231_792
-
----- start-00:23:30-20030221_002330.231_792 - 0 The operation completed successfully.
.
.
Kixtart 4.20 (console-less) update completed. ('C:\WINDOWS\TEMP\IXP000.TMP\' -> 'C:\WINDOWS\')
- 464-00:23:30-20030221_002330.231_792 - 0 The operation completed successfully.
- 467-00:23:30-20030221_002330.231_792 - 0 The operation completed successfully.
greetings.
btw: we have send dummy.exe program to you.
|
|
Top
|
|
|
|
|
#98506 - 2003-02-22 12:09 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear Lonkero,
You doesn't have any influence on the specification in the SED file.
Environment variables will not be expanding.
Simple kix32.exe install.kix or wkix32.exe winstall.kix works
in all situations. It bypasses the possible problems when temporary path
name has been changed.
A problem which we can't bypass is the AppLaunch specification.
greetings.
|
|
Top
|
|
|
|
|
#98507 - 2003-02-22 12:57 AM
Re: WKIX32.EXE deployment.
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2127
Loc: Tulsa, OK
|
Can you try...
code:
AppLaunched=WKIX32.EXE
PostInstallCmd=START /W "WKIX32.EXE WINSTALL.KIX"
?
Since you were getting help message I would think was stopping the start command at the space. Also if you are using IExpress?..Try just...
code:
AppLaunched=wkix32.exe winstall.kix
PostInstallCmd=<None>
[ 22. February 2003, 01:00: Message edited by: CitrixMan ]
|
|
Top
|
|
|
|
|
#98508 - 2003-02-24 06:23 AM
Re: WKIX32.EXE deployment.
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Shane,
Been there.. Done that..
No dice..
Kent
|
|
Top
|
|
|
|
|
#98509 - 2003-02-24 06:52 AM
Re: WKIX32.EXE deployment.
|
NTDOC
Administrator
Registered: 2000-07-28
Posts: 11628
Loc: CA
|
Hmmm.. Not sure if locked in-use file is your problem or not, but maybe try looking at this KB for a Registry method of replacing an inuse file.
M$ has a .EXE for it as well.
How to Replace In-Use Files at Windows Restart
|
|
Top
|
|
|
|
|
#98511 - 2003-02-25 12:46 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
Thanks CritixMan, you point me in the right direction with your second
suggestion.
We are using following specification:
code:
AppLaunched=wkix32.exe /i dummy.kix
PostInstallCmd=wkix32.exe /i winstall.kix
dummy.kix script contains only a CLS kixtart command.
Without any window wkix32.exe will be installed in a correct
way. Also it isn't necessary to include kix32.exe in the
console-less update packages. It will reduce the amount of
bytes to transfer.
CitrixMan, something about your suggestions
- suggestion 1
"AppLaunched=wkix32.exe" will active a window on XP.
"PostInstallCmd=start /w wkix32.exe winstall.kix" isn't necessary. This wasn't
the problem. We suggest also to specify in the WKIX32 call the /ioption. - suggestion 2
"PostInstallCmd=<none>" will return an error window. So specification
of a command is necessary.
Based on these results we will repack our iexpress packages.
A possible sound will be disappear also. Sound was made after
a missing script in earlier kixtart releases.
greetings.
btw: kdyer, we think it is also useful information for you.
(TO_DO)
|
|
Top
|
|
|
|
|
#98512 - 2003-02-25 01:38 AM
Re: WKIX32.EXE deployment.
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
NTDOC, during one of those testing we were submitting about 10 update jobs at nearly the same time.
Never we get a situation of hanging. Only an incorrect created package hangs f.e. missing
application to start or waiting for feedback by user on kixtart help window.
Lonkero, possible you were missing also our latest version. PostInstallCmd is a requi-
red key. No specification generates an error window. With the /i specification in
our call we doesn't see any kixtart window at all.
greetings.
|
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 837 anonymous users online.
|
|
|
