Removed files from C: root
Hello!
Strange problems with files on C: root. On some machines all files from C: root is removed when we run a MSI with a MST file. All files but those with attribute R. And it’s only when we add the MST file the files are removed. When we run the MSI alone no files are removed.
And it doesn’t stop there… It doesn’t happen on all machines?! Only on a few of the installations.
So, what could be wrong? Have anyone heard of this strange behavior? Is it the oldest newbie error?
Please help!
Staffan Nilsson – Stockholm - Sweden
Strange problems with files on C: root. On some machines all files from C: root is removed when we run a MSI with a MST file. All files but those with attribute R. And it’s only when we add the MST file the files are removed. When we run the MSI alone no files are removed.
And it doesn’t stop there… It doesn’t happen on all machines?! Only on a few of the installations.
So, what could be wrong? Have anyone heard of this strange behavior? Is it the oldest newbie error?
Please help!
Staffan Nilsson – Stockholm - Sweden
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
17 years ago
There must be something in the RemoveFile table or a CA that does it. Why? - it is very strange. Most MSI's avoid installing to or removing from the root.
Posted by:
revizor
17 years ago
As a wild guess, can you double-check environment variables on the computers that have that issue?
Also, see what changes are overlayed by MST file - from what you've described, the issue is caused by something within the MST...
Also, see what changes are overlayed by MST file - from what you've described, the issue is caused by something within the MST...
Posted by:
AngelD
17 years ago
Correct me if I'm wrong but the MSI is an InstallShield based MSI and you have used Wise or maybe a InstallShield tool to generate the MST.
When the MST is generated it will add hard-coded properties and one of them is called ISSETUPFILESCOMPLETED. So when the ISSetupFilesCleanup custom action is executed the temporary location for the InstallShield support files is messed up and therefore pointing to the root drive. Just remove the ISSETUPFILESCOMPLETED property from the transform to fix your problem.
When the MST is generated it will add hard-coded properties and one of them is called ISSETUPFILESCOMPLETED. So when the ISSetupFilesCleanup custom action is executed the temporary location for the InstallShield support files is messed up and therefore pointing to the root drive. Just remove the ISSETUPFILESCOMPLETED property from the transform to fix your problem.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
