Voodoo magic MST
Hi All,
I've got a MST for Java 1.5.0_6 that as far as i can tell does nothing. Macromedia Tuner tells me so and it's all of 4kB, the same as a completely blank MST created on the same MSI. When this MSI runs, it installs normally, but unfortunately (for the users of the ~1500 PCs it was deployed to) then deletes most of the files (not folders) from the root of C:\. Does anyone have any idea how this remarkable MST might be doing this?
Thanks
Brett
(no, I wasn't the one that did the push ;)
I've got a MST for Java 1.5.0_6 that as far as i can tell does nothing. Macromedia Tuner tells me so and it's all of 4kB, the same as a completely blank MST created on the same MSI. When this MSI runs, it installs normally, but unfortunately (for the users of the ~1500 PCs it was deployed to) then deletes most of the files (not folders) from the root of C:\. Does anyone have any idea how this remarkable MST might be doing this?
Thanks
Brett
(no, I wasn't the one that did the push ;)
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
17 years ago
This is a known bug with generated transforms for InstallShield MSIs.
Remove the ISSETUPFILESCOMPLETED property from the Property table.
BUG: Response Transforms Delete "boot.ini"
Remove the ISSETUPFILESCOMPLETED property from the Property table.
BUG: Response Transforms Delete "boot.ini"
Posted by:
brettski
17 years ago
If only the MST had in fact been deleting the BOOT.ini we would have found out earlier. It was only deleting things like autoexec.bat etc that aren't strictly required for WinXP. Looking at the MST, it had that property and removing it fixed the problem. The link you gave doesn't provide much information so i have a couple of questions. Does removing this property have any other effects (ie the package now doesn't clean itself up correctly)? Also, this is the first time i've noticed this problem, so I'm assuming that InstallShield only creates this property sometimes (just checked another MST and it didn't have the property included). Do you know if a particular circumstance causes it to be created or not?
Thanks for your advice.
Brett
Thanks for your advice.
Brett
Posted by:
AngelD
17 years ago
If I recall:
If the "ISSetupFilesExtract" custom action exist the "ISSETUPFILESCOMPLETED" property will be set to Complete when it has been executed.
I think the property in some how is referenced to where the temporary folder where "supporting" files has been extracted and including this property will in the end only refer to the ROOTDRIVE which in your case is C:\ when the custom action is trying to clean up the temporary folder.
There is no issues with removing the "ISSETUPFILESCOMPLETED" property from your MST. In opposite by removing the property it will make sure that the temporary folder (for "supporting" files) is properly cleaned up.
If the "ISSetupFilesExtract" custom action exist the "ISSETUPFILESCOMPLETED" property will be set to Complete when it has been executed.
I think the property in some how is referenced to where the temporary folder where "supporting" files has been extracted and including this property will in the end only refer to the ROOTDRIVE which in your case is C:\ when the custom action is trying to clean up the temporary folder.
There is no issues with removing the "ISSETUPFILESCOMPLETED" property from your MST. In opposite by removing the property it will make sure that the temporary folder (for "supporting" files) is properly cleaned up.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.