Folder Tabs with multiple TC versions installed

ElQuia · Post by *ElQuia » 2011-10-07, 16:03 UTC

Hi guys. Got an issue:
I have installed on the same PC (my main one) three iterations of TC:

1- The "main" or "work" one, x86 beta 4, lots of plugins, extra progs, toolbars, etc. installed. Location is D:\Program Files\Totalcmd

2- A Lean installation, nearly "pure" x86 beta4 also with few plugins, etc. Use is mainly for testing plugins, etc. Location is: C:\totalcmdx86

3- 64bit 8beta 4 kind of lean also, with all the x64 plugins that I find useful (still missing a lot

- I really mis Plugin manager here). Location is: D:\Program Files\Totalcmdx64

wincmd.ini for each is in the program directory with absolute paths. When I upgrade I do it in the following order: 2 first, then 3 and last 1 aka my main installation so being last system (Win7 x64) will have it "registered" for stuff like "open with total commander", etc.

THE PROBLEM: each time I upgrade, all three iterations "pick up" the folder tab configuration of my main installation!!!!, losing the one they had. Even if in their own wincmd.ini the "lefttabs" and "righttabs" are DIFFERENT than those of main (1) installation.

All other individual configurations as per each wincmd.ini are kept. The only bugger is the tabs

Please help? Ideas?

MVV · Post by *MVV » 2011-10-07, 16:22 UTC

It seems that installer works in some wrong way here.

BTW you may upgrade TC manually - just unpack files from tcxxx.exe/install.cab and files from tcxxx.exe/install.cab/en or tcxxx.exe/install.cab/de (depending on your help language) to TC folder and replace existing files. This way no INI or registry changes will be made.

ElQuia · Post by *ElQuia » 2011-10-07, 16:50 UTC

MVV wrote:It seems that installer works in some wrong way here.

BTW you may upgrade TC manually - just unpack files from tcxxx.exe/install.cab and files from tcxxx.exe/install.cab/en or tcxxx.exe/install.cab/de (depending on your help language) to TC folder and replace existing files. This way no INI or registry changes will be made.

Will try that next time, thanks. I still would like to know why it happens and FROM WHERE are the other non mail installs reading the tab configuration...
Because if I delete all tabs in one of them it chantes my main install tabs also!!!

MVV · Post by *MVV » 2011-10-07, 17:03 UTC

AFAIK installer tries to copy some settings from existing installation (if one found) to new one... but I argee that it shouldn't do it if new one is already tweaked.

ElQuia · Post by *ElQuia » 2011-10-07, 17:13 UTC

Just discovered what is happening: renamed my main TC dir, other 2 installations fell back to default.

They are reading the last install config file, EVEN if during install I specified program directory.

Now, WHERE is the setting that controls that behaviour?

GUESS it must be this registry key:

Key Name: HKEY_CURRENT_USER\Software\Ghisler
Class Name: <NO CLASS>
Last Write Time: 110807 - 21:09

Key Name: HKEY_CURRENT_USER\Software\Ghisler\Total Commander
Class Name: <NO CLASS>
Last Write Time: 111007 - 10:31
Value 0
Name: IniFileName
Type: REG_SZ
Data: D:\Program Files\TotalCmd\wincmd.ini

Value 1
Name: FtpIniName
Type: REG_SZ
Data: D:\Program Files\TotalCmd\wcx_ftp.ini

Value 2
Name: InstallDir
Type: REG_SZ
Data: D:\Program Files\TotalCmd

The question is: is there any way to change that behaviour??
I really would like each install reading its OWN wincmd.ini!!!

MVV · Post by *MVV » 2011-10-07, 17:40 UTC

Maybe you can try to remove registry key with path to previous installation before installing new one? So installer won't find previous installations - until it is fixed.

Are you sure you're using own INI for each installation? Do you have UseIniInProgramDir=7 parameter in each wincmd.ini? Have you deleted wincmd.ini from C:\Users\You\AppData\Local\GHISLER dir?

Balderstrom · Post by *Balderstrom » 2011-10-07, 17:42 UTC

What TC should have, is like what Notepad2 does.
It has a notepad2.ini, which if you put a single line in it, tells it where the actual config file is.
e.g.

Code: Select all

[Notepad2]
Notepad2.ini=%APPDATA%\NotePad2\Notepad2.ini

As opposed to TC's normal behaviour of looking in the registry unless you specify a wincmd.ini file to load in the (shortcut) command parameters.

ElQuia · Post by *ElQuia » 2011-10-07, 18:00 UTC

MVV wrote:Maybe you can try to remove registry key with path to previous installation before installing new one? So installer won't find previous installations - until it is fixed.

Are you sure you're using own INI for each installation? Do you have UseIniInProgramDir=7 parameter in each wincmd.ini? Have you deleted wincmd.ini from C:\Users\You\AppData\Local\GHISLER dir?

I did not have the line UseIniInProgramDir=7 in any of them.
When I installed I opted for the program dir as ini location file.... dont know why the installer did not do it.

Now I added it and it seems to work, will test more and be back

THANKYOU GUYS!!!

ElQuia · Post by *ElQuia » 2011-10-07, 18:02 UTC

Balderstrom wrote: As opposed to TC's normal behaviour of looking in the registry unless you specify a wincmd.ini file to load in the (shortcut) command parameters.

How do I do that?

Edit: found it /i= path

Now THE REAL COOL TRICK WOULD BE HAVING A MIXED 32 64 BIT SETUP... but I guess that is impossible because of plugins??

It makes sense when using from a portable CD (for virus infected machines) or from a pen drive.... one install goes for xp, vista and 7 be they 32 or 64

AGAIN GUYS THANKS A LOT!!!!

Balderstrom · Post by *Balderstrom » 2011-10-07, 19:12 UTC

You don't - it's something Mr.Ghisler should consider. It would fix almost all known problems with having multiple versions installed - Especially with the current x64.

Except now we have x64 TC that suggests it be installed in "Program Files (x86)", which apparently isn't disallowed by the OS, but it's really bad practice to install 64bit applications in a x86/32 bit folder.

MVV · Post by *MVV » 2011-10-07, 19:18 UTC

ElQuia, if you set INI placement during TC installation, installer writes settings into registry. And depending on registry settings TC will use INI file. But parameter UseIniInProgramDir allows to override registry and always use INI in TC dir.

TC allows to install both versions to same folder, it will load automatically corresponding plugin (you need to place plugins together, one with W?X and other with W?X64 extensions).

Don't forget that you still may use 32-bit version on 64-bit machines.

Except now we have x64 TC that suggests it be installed in "Program Files (x86)"

I never install TC to Program Files, I always install it to TOTALCMD dir in root folder of drive (D: or E: if available - it allows to reinstall system w/o touching TC).

ElQuia · Post by *ElQuia » 2011-10-07, 19:40 UTC

MVV wrote: TC allows to install both versions to same folder, it will load automatically corresponding plugin (you need to place plugins together, one with W?X and other with W?X64 extensions).

mmm, in a simple setup I guess yes.. I am using TC for nearly everything, quick image or video browsing, file unpacking, docs browsing, etc. ulister for example, needs a redist subfolder, x86 redist folder has the same name as x64--- maybe I prefer to let x646 plugins and tools mature some more before merging both... (I miss plugin manager from alexey, he doesnt have an x64 pc to develop) ... and keep separate versions for now....

Don't forget that you still may use 32-bit version on 64-bit machines..

well sooner or later 32 bit will go the windows 3.1 way.... when it's available i use x64 progs. with TC, x64 is too new, so it testing for me... long waited, but gotta be patient haha..