Installation always ends up in \\Program Files

[Octopuss]

On Windows7 64bit, despite setting a path in install.inf to either %ProgramFiles% or %ProgramW6432% (I tend to use the former but tried both), TC always ends up in C:\Program Files (x86)\

Interesting detail: configuration file DOES get created in C:\Program Files\

There must be a very little bug related to paths somewhere in the installator.

Relevant part of my install.inf:

Code: Select all

[Installation]
program=Total Commander 64 bit
progver=8.0
progvermajor=8
progverminor=0128
progname=Total Commander
copyright=Copyright © 1993-2012 by Christian Ghisler, All Rights reserved
url=http://www.ghisler.com
publisher=Ghisler Software GmbH
updatecheck=totalcmd64.exe
// User for shortcut creation: Blank for current user, * for all users
UserName=*

[auto]
// Set auto=1 for automatic installation, hidden=1 for invisible installer, with parameters below and from [Installation]
auto=1
hidden=0
lang=1
alllang=1
iniloc=%ProgramFiles%\totalcmd
iniall=1
mkgroup=1
mkdesktop=1

[Versioncheck]
Vernum=2

[Not running]
1=WINDOW,Total Commander
2=TTOTAL_CMD,Total Commander
3=TTOTAL_CMD.UnicodeClass,Total Commander
4=TApplication,Total Commander,Total Commander

[Destination]
Dir=%ProgramFiles%\totalcmd
Ini=wincmd.ini,Configuration,InstallDir

[umbra]

The destination directory is ignored, if there already is/was TC installed. In that case, the installer always does an upgrade.
See http://ghisler.ch/board/viewtopic.php?t=11119

[Octopuss]

Not this case, I uninstalled and completely removed everything first.

[umbra]

Sorry, but I will not write same answers to two threads. Please, check my answer from your other thread (http://ghisler.ch/board/viewtopic.php?t=34554) and decide, in which one we should continue this discussion.

[Octopuss]

I am sorry Guess this section is more appropriate.

2Octopuss
Unfortunately that doesn't help. You have to manually delete its install path from registry. Search for these keys:

Code: Select all

HKEY_CURRENT_USER\Software\Ghisler\Total Commander
HKEY_CURRENT_USER\Software\Wow6432Node\Ghisler\Total Commander
HKEY_LOCAL_MACHINE\SOFTWARE\Ghisler\Total Commander
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Ghisler\Total Commander

Ha! Now we're onto something. It IS a bug then, but different than I originally thought.
As much as this is possibly (half) intentional behavior, I strongly disagree. This is prime example of why registry cleaners exist in the first place.

When software is being uninstalled, EVERYTHING should be eliminated, there's - in my opinion - no argument about that. This of course is not 1% as bad as such mess other applications are capable of producing.

I just find it weird stuff is left in registry when you get the option to remove configuration files and other stuff during installation. That is like making double sure the user really wants to uninstall the program. No point in keeping registry entries at all.

[umbra]

I just find it weird stuff is left in registry when you get the option to remove configuration files and other stuff during installation.

I agree with you. But I don't know, if the current implementation (one shared registry for all installations) allows that.

[Octopuss]

I certainly hope Christian will comment on this

[petermad]

When software is being uninstalled, EVERYTHING should be eliminated

I agree on that. Perhaps an option during uninstallation to keep registry settings, could satisfy everyone...

[ghisler(Author)]

This is intentional - some people think that they have to remove the old version before installing the new, which is just wrong. It would be very bad to remove the location for these people when uninstalling.