MSI MoveFiles table question

I'm packaging an app (Oracle ADI) and have discovered that in my captured package, one of the files required for uninstalling the app does not get installed.

I could handle this easy enough in Wise Package Studio by adding a line of Wise Script to copy the file from point A to Point B, but I'm trying to learn how to do it right in the MSI (which I created myself, which is why I'm not using a transform).

Typically when we install a package to a target PC, we copy the installation files to %TEMP\[foldername], %TEMP% being C:\Documents and Settings\[user name]\Local Settings\Temp. I'm not sure, though, how to reference this folder in my MSI tables.

The file in question I'm trying to move is DeIsL1.isu. I've made changes to 3 of the MSI tables as outlined below:

Component table:

Component ComponentID Directory Attributes Condition KeyPath
MSI_DeIsL1.isu [unique GUID] US 0 DeIsL1.isu

MoveFile table:

FileKey Component SourceName DestName SourceFolder DestFolder Options
MSI_DeIsL1.isu MSI_DeIsL1.isu DeIsL1.isu MSI_DeIsL1.isu Source_isu US 1

Property table:

Property Value
Dest_isu C:\OA_DOC\US
Source_isu %TEMP%\ADI

Based on my log error when I ran the install ("Could not access network location %TEMP%\ADI7211"), I'm guessing I might need to make an addition to the Directory table, but I'm not positive how to do this, assuming I'm headed in the right direction with this.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 12 years ago
Red Belt
This file is a record of the installation by the original installer and is referred to for uninstalling. Since you're using an MSI for both, I wouldn't bother with it.

In principle, though, you're right. You do need entries in the Directory table. Those entries need to form the entire tree, as far as the 'US' folder and the source folder. That is to say, you need an entry for 'OA_DOC' folder, then the 'US' folder which will have OA_DOC as its parent. Ditto for the 'ADI' folder branching from %TEMP%.
Posted by: pjgeutjens 12 years ago
Red Belt
Typically when we install a package to a target PC, we copy the installation files to %TEMP\[foldername]

I have a sneaking suspicion you're using MSIs as a glorified Robocopy to get your installer files to the local machine...
Really not what MSIs are for, and if I'm mistaken, Ian is right, you won't need the .isu file once you've made your own MSI.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ