1 reply to this topic

[agaskell]

If I install onto a Windows 95 machine *without* the cache
installation option selected, I get an orphaned msi file for each
installation, located at: [windowsfolder]Installer. Rebooting the
machine *does not* delete the file. These files continue to accumulate
at each install. Since the naming convention of these orphaned msi
files cannot be predicted, it is not possible to write a script to
remove them on uninstall. As an example e02ad.msi is the name of one
of my orphaned files.

If I install onto a Windows 2000 machine, under the same conditions
this orphaned file (and the Installer folder) are not created.

Can someone please help? I am using InstallShield Developer 7.

[hambone]

i believe you will find that the 'orphaned msis' are actually cached copied of the original msi.  in the case of win2000/winxp by default the {windowsdir}/installer directory is there but hidden from view.