Uninstall name

[Tuesday, February 15, 2005 6:35 PM]

Hi Friedrich,

Yesterday I was installing 4 installs that make up a SQL project on a
client machine. I realized that the uninstall logs were all the same
name and since all installs installed into the same directory I was
only able to uninstall the last one installed. Fortunately I had set
a restore point before I started, so I just restored to that point and
it got rid of the installed stuff. It took me quite a while to find
where I could set the name of the uninstall and then to find where I
could set the name of the uninstall log file. I could only find it in
the script editor. These settings should IMO be on the Add/Remove tab
for the project. The uninstall.exe is on the product tab so at least
it can be found, but I could not find the log name setting anywhere
except in the script.

It also seems that even if the uninstall shortcut is used and it is
pointing to the right unintall log etc. the uninstall pops up the file
dialog to select the uninstall log. This could be very confusing for
end users if you have more than one install into the same directory.
In this case I have separate installs for Crystal Reports, SQL
Anywhere, the program itself and finally one for the CR report files.
The primary destination is all in the same directory so I got 4
installs all putting an uninst.log file in the directory. IMO, the
uninstall log should default to the [PRODUCTNAME].log and the
uninstall.exe should default to "Uninst"[PRODUCTNAME].exe when the
install is created. Maybe it does not, but this was created in build
around 970. These installs were compiled yesterday with build 1042.

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Tuesday, February 15, 2005 7:46 PM]

Arnor,

As a rule, I always give the install and uninstall programs unique names for
the project. Which is available in the general area if memory serves. For
example, I maintain the PlugIT install for Andy. The installer is
SetupPlugIT20.exe and the uninstall is UninstalPlugIT20.exe. Never use the
default names.

My biggest pet peeve with install programs is their uninstall processes. I
can understand leaving behind new folders and files created after
uninstallation (which I would love to give the user the option to remove
those as well), but there is always something left behind with other
packages (so it seems). Run a registry integrity scanner to get an idea of
what is left behind.

The point is that vendors really need to test their uninstalls. The goal is
that the uninstall should leave your machine in a state like the program was
never installed in the first place (exception above).
--
Russ Eggen
www.radfusion.com

[Tuesday, February 15, 2005 8:18 PM]

Hi Russ,

>As a rule, I always give the install and uninstall programs unique names for
>the project. Which is available in the general area if memory serves. For
>example, I maintain the PlugIT install for Andy. The installer is
>SetupPlugIT20.exe and the uninstall is UninstalPlugIT20.exe. Never use the
>default names.

I completely agree, but I just simply didn't realize that they were
using the same names. Changing the uninstall exe name is fairly easy,
but finding the log name was a PITA<g>

>My biggest pet peeve with install programs is their uninstall processes. I
>can understand leaving behind new folders and files created after
>uninstallation (which I would love to give the user the option to remove
>those as well), but there is always something left behind with other
>packages (so it seems). Run a registry integrity scanner to get an idea of
>what is left behind.

Yep - that's why I was clever enough to create a restore point before
I started messing with this. You can make the uninstall remove all
files, if you figure out all the files that your program creates and
put dummy, 0 byte files into the install. I.e. if your program
creates some tps files, create 0 byte files (or whatever), I just use
an editor to create an empty text file that I then copy to the right
filename. Then include these files in your install and the
uninstaller will then take care of removing them. Of course if the
_user_ can create files in different directories, that get's to be
outside the bounds of the uninstall, but then OTOH, the uninstall log
is just a text files so I guess if you wanted to keep track of it
all, you _could_ just update the uninstall.log file...

>The point is that vendors really need to test their uninstalls. The goal is
>that the uninstall should leave your machine in a state like the program was
>never installed in the first place (exception above).

Absolutely! I'm planning to get me a cheap machine to use for testing
only and use tool like Partition Magic to create multiple OS
partitions and then use mirror backup tools to mirror the clean
installed drive to a second drive. When I need it cleaned up again I
can mirror the drive back. This can be used to testing both products,
installs, uninstalls etc. etc.

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Tuesday, February 22, 2005 12:58 PM]

Arnór,

Changed now. There is a new [UNINSTALL_LOG] item on the General Information
screen.

When creating new projects, the [UNINSTALL] compiler variable defaults to
%_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].exe and [UNINSTALL_LOG] defaults to
%_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].log

The Create Installation Log script item now contains [UNINSTALL_LOG].

Thanks,
Friedrich

--
Friedrich Linder
www.lindersoft.com
Fax: 1.954.252.3910

[Tuesday, February 22, 2005 4:35 PM]

Hi Friedrich,

>%_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].exe and [UNINSTALL_LOG] defaults to
>%_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].log
>
>The Create Installation Log script item now contains [UNINSTALL_LOG].

Awsome:)

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA

[Tuesday, February 22, 2005 7:47 PM]

Thanks!

Just to clarify, this sounds like it has no impact on existing uninstall
names, right?

--
Russ Eggen
www.radfusion.com

[Thursday, February 24, 2005 3:58 PM]

Right! :)

Friedrich