Software Deployment

Hi NACM,
as you may encountered yourself, the file Quicktime.qtp goes to the [Profiles Folder]\All Users\Application Data\Apple Computer\QuickTime.
To put that file into an MST, you need to perform the following tasks:

Configure Quicktime to your needs and save the Quicktime.qtp file to a working directory.
Generate a config.ddf file with the following entries and put it also to the working directory:
-----
.Set CabinetNameTemplate=config*.cab
.Set CabinetName1=config.cab
.Set ReservePerCabinetSize=8
.Set MaxDiskSize=CDROM
.Set CompressionType=MSZIP
.Set InfFileLineFormat=(*disk#*) *file#*: *file* = *Size*
.Set InfHeader=
.Set InfFooter=
.Set DiskDirectoryTemplate=.
.Set Compress=ON
.Set Cabinet=ON
QuickTime.qtp QuickTime.qtp
-----

Now we can generate the cabfile:
makecab /f config.ddf
should leave you with config.cab in the working directory.
(The 'makecab' utility is part of the standard installation on WindowsXP).

(The following things should be done best with ORCA)

Load QickTime.msi
Go to 'Transform : 'New Transform', this opens an empty transform.

Add the following row to the 'Component table':
com.apple.QuickTime {a new GUID goes here} QuickTimeCommonAppDataFolder 0 QuickTime.qtp
(To generate an new GUID, in ORCA go to View : Summary Information... and press the 'New GUID' Button. Copy the resulting GUID and paste it to appropriate place in the above row)

Add the following row to the 'FeatureComponents table':
QuickTimeEssentials com.apple.QuickTime

Add the following row to the 'File table':
QuickTime.qtp com.apple.QuickTime QUICKT~1.QTP|QuickTime.qtp 12805 0 545

Make a new row to the 'Binary table':
Add row..., name it 'config.cab' and for the data entry browse for the newly created config.cab file.

Add the following row to the 'Media table':
2 545 2 #Binary.config.cab

Go to 'Transform : 'Generate Transform...', name and save it.

That's it!
You could also add the 'com.apple.QuickTime.plist' file which holds the User Registration for the pro version. This file goes to the same directory and therefore, it could be appended to the same component.

Hope this helps a bit.
Regards, Nick

Hi Sleeper,
do not repackage this MSI with wise! Version 7.1.3 is now a native MSI built with Installshield. If you have to alter it, use ORCA and build a transform.
Regards, Nick

Thank you Nick, i made a transform like you said and it work fine now
Thank's again !
[;)]

Newbie here!

Is it okay to build a transform using Wise or do you have to use ORCA absolutely...

I remember that prior to 7.1.3 mst weren't working properly but now everything looks okay with the .mst I made with Wise for Windows Installer 6.1.

Just want to make sure I'm not missing anything before I deploy this...

Using ORCA would work anytime, just more work but if you know your way around tables there shouldn't be any problems.
Using Wise for InstallShield packages may sometimes not work and wise will add info/tables by default not "suited".
Don't know for creating transforms using InstallShield as I don't use it.

Has anyone use an QT.QTP file in MST? I tried to use this, but it won't successful. Any suggestions on how to use this file? Thanks

Nice nheim!

Rated this one for your time & effort.

You can also use InstallTailor which is included with Wise Packae Studio to create the Transform for Quicktime which works well then you can also copy the file to the appropriate location needed within the Transform. This should only take 10-15 minutes.

KJ

Wise Packager

@ KJ,
don't exactly see how you could add a file to transform with InstallTailor. AFAIK InstallTailor only captures properties which change during the 'InstallUISequence' portion of the setup.
What should work, is to open 'QuickTime.msi' in 'Wise Windows Installer Editor', add the needed changes (incl. adding files) and save it as an MST. But most likeley, you need to open it in ORCA afterwards again and remove the garbage, WWIE also added (see the starting messsage of this thread). That's the reason, why i prefer to use ORCA for this kind of work.

To AngelD,
thanks for the flowers :-)

Regards, Nick

ORIGINAL: AngelD

Using ORCA would work anytime, just more work but if you know your way around tables there shouldn't be any problems.
Using Wise for InstallShield packages may sometimes not work and wise will add info/tables by default not "suited".
Don't know for creating transforms using InstallShield as I don't use it.


InstallShield will add junk also, so this is how I deal with it:

- copy the original MSI to a new name.
- make the new name something like <originalname>_IS.msi
- open the new <originalname>_IS.msi with InstallShield, make some trivial little change you don't care about (just so as to touch the file) and save it.
- Then, make the changes you care about, but save AS <originalname>_IS_changed.msi
- generate a TRANSFORM using <originalname>_IS_changed.msi against base msi <originalname>_IS.msi
- Install the original vendor msi with your new transform

Because the transform was made by diffing two MSI's BOTH of which contained the IS_added junk, the transform should have minimal traces of the junk in it.

Anyway, this is what I do & I have had good luck with it.

- William -

InstallShield will add junk also
Well, it shouldn't matter which one to use then ;)

After working with the preferred tool one will know what's getting added and just remove that "junk" with ORCA before releasing the MSI/MST.