Uninstall logs revisited

[NewsArchive]

In an earlier post my inquiry regarding uninstall logs ( see "WebUpdate
Uninstall Questions" - 10/11/2005 ) was not completely answered and
Friedrich was looking into handling multiple logs.

One solution was to use the "Delete Tree" function but that scares the h***
out of me because if %_SB_INSTALLDIR% should somehow be populated with an
incorrect folder name the risk of doing "serious" damage to the users
computer is significant. I'm not sure I feel comfortable with the risk.

In an ideal world it would be great if during the web update a temporary
uninstall log file could be created just for the roll back capability if
needed and then removed when the update install is completed successfully.
However, during this update it would make sense to be able to add/append the
new log items to the original uninstall log that was created during the
initial install.

I'm not completely certain I'm making a lot of sense here, but I really
would like to find a way to "completely" cleanup/uninstall every folder and
file that has been installed either during the initial install or any one of
multiple update installs.

Any suggestions or help other than using the "Delete Tree" function would be
most welcome.

Thanks

Lee

[NewsArchive]

Lee,

For an uninstall, the %_SB_INSTALLDIR% variable always points to the
location where the uninstall executable resides. And of course, you
can use the script to perform additional "security checking" or call
into your own (Clarion) DLLs to handle uninstall actions.

I am still investigating improved rollback solutions (e.g. "in-memory
rollback" - in this case the rollback info is not written to a log).

BTW, we are using the Delete Tree function in all SB5 Editions without
any problem.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

Friedrich,

Thank you for the response. I have created my own custom install that
hopefully will get done what I need. Future installations are not a problem
at all. I am still attempting to clean up the mess that was left behind when
GetAFile shut down their file hosting servers with no warning.

I have an undetermined number of users that still have the web update
information pointing to GetAFile in the registry and of course they are
unable to download and install my update as a result.

I'm certain you can imagine what it would be like if the server providing
your updates for SB suddenly went away and you had to get all your users
corrected and pointed to a new download site. That's basically what I'm
dealing with but of course not on as grand a scale as you would be faced
with.

Any way you cut it, it's a nightmare.

Thanks again.

Lee