Anyone have documentation on this file and how to make changes.

The last entry has the location of the isscript file. I would like to change this file to reside 1-2 levels higher up the directory tree. No matter what changes I make setup.exe just seems to append any path on to the current location that setup.exe is run from. This one app contains about 9 of these isscript files and it would be great to have just one taking up space on my server. Changing the ScroptDriven entry to equal 0 makes the msi not install correctly. I hate scripted MSIs... why even have an msi? [:@]
Here is the file:


[Info]
Name=INTL
Version=1.00.000
DiskSpace=8000 ;DiskSpace requirement in KB

[Startup]
CmdLine=NOTADDREMOVE=1
SuppressWrongOS=Y
ScriptDriven=1
ScriptVer=8.1.0.293
DotNetOptionalInstallIfSilent=N
OnUpgrade=1
RequireExactLangMatch=0404,0804
Product=Camera Access Library
PackageName=Camera Access Library.msi
MsiVersion=2.0.2600.0
EnableLangDlg=Y
DoMaintenance=Y
ProductCode={7B7E0478-F53C-49DB-BB34-C877B7B35BF8}
ProductVersion=8.1.0.17
SuppressReboot=Y
PackageCode={F418F1AB-A799-4C52-99AB-07B1417DF245}

[SupportOS]
Win95=1
Win98=1
WinME=1
WinNT4=1
Win2K=1

[Win95]
MajorVer=4
MinorVer=0
MinorVerMax=1
BuildNo=950
PlatformId=1

[Win98]
MajorVer=4
MinorVer=10
MinorVerMax=11
BuildNo=1998
PlatformId=1

[WinME]
MajorVer=4
MinorVer=90
MinorVerMax=91
BuildNo=3000
PlatformId=1

[WinNT4]
MajorVer=4
MinorVer=0
MinorVerMax=1
BuildNo=1381
PlatformId=2
ServicePack=1536

[Win2K]
MajorVer=5
MinorVer=0
MinorVerMax=1
BuildNo=2195
PlatformId=2

[Languages]
count=7
default=409
key0=804
key1=409
key2=40c
key3=407
key4=410
key5=411
key6=40a
[Camera Access Library.msi]
Type=0
Location=Camera Access Library.msi
[Setup.bmp]
Type=0
[instmsiw.exe]
Type=0
Location=..\Common\instmsiw.exe
[instmsia.exe]
Type=0
Location=..\Common\instmsia.exe
[ISScript.msi]
Type=0
Location=ISScript8.Msi
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I wouldn't mess with that file and keep it stock. If you want to custumize your installation it is fairly easy to pass MSI commands via the command line using the /v switch.

example:setup.exe /s /v"/qb"

You can set any properties you like, I would try that.

http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpPropReference.htm
Answered 11/30/2007 by: Coriolus
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity