Adobe AR8 native install deletes (or attempts to) system files
During a troubleshooting phase of why certain files were deleting off the root of the c:\ and breaking an image installation here's what I found when running the Acrobat Reader 8 install with verbose logging. Just thought I should put this out there in case anyone else runs into the problem. Here's the portion of the log file that shows the file deletion process. To fix I removed the ISSetupFilesCleanup CA from all sequences. This is from the re-distributable download of Reader 8.
MSI (s) (24:48) [17:16:16:763]: Doing action: ISSetupFilesCleanup
Action start 17:16:16: ISSetupFilesCleanup.
MSI (s) (24:90) [17:16:16:773]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2C.tmp, Entrypoint: SFCleanupEx
1: Deleting Support File: \1STBOOT.BAT
1: Deleting Support File: \AUTOEXEC.BAT
1: Deleting Support File: \BOOT.IBM
1: Deleting Support File: \BOOT.INI
1: Deleting Support File: \BOOTLOG.PRV
1: Deleting Support File: \BOOTLOG.TXT
1: Deleting Support File: \BOOTSECT.DOS
1: Deleting Support File: \CONFIG.SYS
1: Deleting Support File: \DRVSPACE.BIN
1: Deleting Support File: \hiberfil.sys
1: Deleting Support File: \HIIT.LOG
1: Deleting Support File: \IO.SYS
1: Deleting Support File: \MSDOS.SYS
1: Deleting Support File: \NTDETECT.COM
1: Deleting Support File: \ntldr
1: Deleting Support File: \pagefile.sys
1: Deleting Support File: \SYSLEVEL.IBM
Action ended 17:16:17: ISSetupFilesCleanup. Return value 1.
MSI (s) (24:48) [17:16:16:763]: Doing action: ISSetupFilesCleanup
Action start 17:16:16: ISSetupFilesCleanup.
MSI (s) (24:90) [17:16:16:773]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI2C.tmp, Entrypoint: SFCleanupEx
1: Deleting Support File: \1STBOOT.BAT
1: Deleting Support File: \AUTOEXEC.BAT
1: Deleting Support File: \BOOT.IBM
1: Deleting Support File: \BOOT.INI
1: Deleting Support File: \BOOTLOG.PRV
1: Deleting Support File: \BOOTLOG.TXT
1: Deleting Support File: \BOOTSECT.DOS
1: Deleting Support File: \CONFIG.SYS
1: Deleting Support File: \DRVSPACE.BIN
1: Deleting Support File: \hiberfil.sys
1: Deleting Support File: \HIIT.LOG
1: Deleting Support File: \IO.SYS
1: Deleting Support File: \MSDOS.SYS
1: Deleting Support File: \NTDETECT.COM
1: Deleting Support File: \ntldr
1: Deleting Support File: \pagefile.sys
1: Deleting Support File: \SYSLEVEL.IBM
Action ended 17:16:17: ISSetupFilesCleanup. Return value 1.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
jmcfadyen
17 years ago
you should log this in the packages section of this site. im sure it will trip up many people to come.
Posted by:
AngelD
17 years ago
Instead of removing the ISSetupFilesCleanup custom action as it is there for removing the extracted support files you should fix the problem instead.
Correct me if I'm wrong but the installation was made with a transform that was generated in some how. During the transform creation the ISSETUPFILESCOMPLETED property was added and it is this little bugger that makes the path for the extracted support files to be lost and point to the root of the drive instead.
Remove the property and all should be fine.
This is an old bug which you can read about at http://support.installshield.com/kb/view.asp?articleid=Q111491
Correct me if I'm wrong but the installation was made with a transform that was generated in some how. During the transform creation the ISSETUPFILESCOMPLETED property was added and it is this little bugger that makes the path for the extracted support files to be lost and point to the root of the drive instead.
Remove the property and all should be fine.
This is an old bug which you can read about at http://support.installshield.com/kb/view.asp?articleid=Q111491
Posted by:
anonymous_9363
17 years ago
What's the difference between those 2 actions? The net effect is the same. I don't know what happened to my original reply to this on Friday which stated that I routinely remove almost *all* of the IS actions.
Posted by:
AngelD
17 years ago
Hi Ian,
I don't know why your "original" reply didn't get through, but why would you want to remove all IS CAs? Some of them may be required for the installation to proper correctly.
Which 2 CAs are you referring too?
If the MSI contains the ISSetupFilesExtract CA this action will when being executed set the ISSETUPFILESCOMPLETED property to Complete or Completed (don't recall the exact value). If this is set then the path to the extracted support files will no longer be resolved which is why the root driver will be addressed instead by the ISSetupFilesCleanup CA.
The net effect is the same.
What do you mean here?
Cheers!
I don't know why your "original" reply didn't get through, but why would you want to remove all IS CAs? Some of them may be required for the installation to proper correctly.
Which 2 CAs are you referring too?
If the MSI contains the ISSetupFilesExtract CA this action will when being executed set the ISSETUPFILESCOMPLETED property to Complete or Completed (don't recall the exact value). If this is set then the path to the extracted support files will no longer be resolved which is why the root driver will be addressed instead by the ISSetupFilesCleanup CA.
The net effect is the same.
What do you mean here?
Cheers!
Posted by:
anonymous_9363
17 years ago
ORIGINAL: AngelDFor InstallShield apps which wrap an MSI, I will always run Setup just far enough to 'extract' that MSI. After that, *most* the IS CAs - ike 'ISSetAllUsers' (or whatever it is, I can't recall exactly) - are just a nuisance so they'll be commented-out in my transform.
...why would you want to remove all IS CAs? Some of them may be required for the installation to proper correctly.
ORIGINAL: AngelDI meant that either deleting/commenting-out the CA or editing the property results in the same thing - you're altering the MSI's behaviour - so what's the difference?
The net effect is the same.
What do you mean here?
Posted by:
AngelD
17 years ago
The ISSETUPFILESCOMPLETED property shouldn't be included in the transform in the first place, that is why I mensioned do it the right way. As the ISSetupFilesExtract CA extracts files that will be used during installation/uninstall it's nice to have them removed at the end which is the ISSetupFilesCleanup CA's task. But yes, the result in the end is the same thing except for the removal of the extracted supporting files. I any way like to have clean and nice MSIs as possible.
Often many functions called from the ISScriptbridge.dll (binary) is used from InstallShield packages and that's why I state that you wouldn't want to remove them as these may be required for the installation to do what it should do.
Regarding the ISSetAllUsers CA, well that one may be an exception if it's not added from the Directory (or Property) table.
Often many functions called from the ISScriptbridge.dll (binary) is used from InstallShield packages and that's why I state that you wouldn't want to remove them as these may be required for the installation to do what it should do.
Regarding the ISSetAllUsers CA, well that one may be an exception if it's not added from the Directory (or Property) table.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
