New install load wincmd.ini settings from current version TC

[BORG52]

When I install TCMD 8b9 over final 7.56a to new separate folder with selected options: wincmd.ini is located in "program directory", wincmd.ini from 7.56a with all settings/plugins,bookmarks,colors../ is loaded to new TCMD8b9 wincmd.ini /installer read previous install path from registry HKEY_CURRENT_USER\Software\Ghisler\Total Commander\installDir
and next replace it path with new location of TCMD8b9/

This is not separate clean instalation,but is good in some cases.
Need next options in setup program: Clean separate install /without linking to other instalations of TCMD/

This small bug is persistent from old versions to 8b9.
Regards

(Sorry for my English)

[Sir_SiLvA]

As this is not a Bug please move this to suggestions...

[ghisler(Author)]

Hmm, not a bug - TC copies the old ini to the directory indicated by the user, and then sets that as the new location.

[Phred]

It certainly seems to copy the ini files from the old, permanent, installation, but TC8b9 doesn't obey the choice in installation to place it, say, in the program folder ...err directory.
My beta installation still refers back to the user appdata folder where my 756a installation has its inis. I'm expecting Help About to point to D:\totcmd\, as per my installation choice.

[ Isn't it time that we had all references in the program referring to 'folders' rather than 'directories'? So 20th century... This is a users tool, after all. ]

[ghisler(Author)]

Could you please check what is stored in the registry under
HKEY_CURRENT_USER\Software\Ghisler\Total Commander
for the ini locations?

[Phred]

Yes, I can do that re the ini locations - but I see, however, a possible flaw in the thinking here that I believe is far too prevalent in today's open internet world, not to mention other contexts.

The issue is that I'm a user, I log on as a user, I operate 99.999% of the time as a user, and I believe everyone who isn't administering should be a user.

I claim that administrator accounts are for administering, or developing. I wouldn't be an administrator for longer than is necessary than walk down the centre of a highway with my eyes closed.

So I suspect there's a possible contradiction between installing a program - necessarily as an administrator - and locating user appdata files in the folder-tree of the account that is NOT making the installation.

Too many installation routines make the highly flawed assumption, IMO, that a program will be used by an installing administrator and ONLY by that administrator. I suspect TC's Installer is acting much in that way - although I acknowledge that a clean install asks about 'All users' somewhere.

It appears that TC's installer isn't allowing for a completely independent parallel (re)install, of, say, betas. TC8b9's installation and inireloc (and subsequent uninstallation) killed my admin's TC inis.
Perhaps it would be peculiar if it did (however useful).
And it may not be obeying all the installation choices. More to check.
(I normally have two desktop shortcuts - one for me as a user and one for elevation as an administrator.)

Mr G, both of the ini locations are:
C:\Users\Phred\AppData\Roaming\GHISLER\
But that's CURRENT_USER, of course. *I* wasn't 'current' when installing TC8b9.
I install as the administrator 'Manager'.

This is interesting: in the same key I have for the Installdir
C:\Program Files\TC
Yet I have no C:\Program Files\TC folder.
I have
C:\Program Files\Total Commander75 - ~9 MB
C:\Program Files\Total Commander - ~ 400 KB
C:\Program Files\Total Commander704a - ~4 MB
folders.
There's a D:\totalcmd folder too - for TC8b9 - ~6 MB.

Kind regards,
Phred