QuickSearch eXtended

[praetor]

2praetor:
Sry, the GUI relies on a ini file in the current directory. You could try to move the totalcmd folder to a directory like "D:\data\totalcmd\".

So the tcmatch.ini is created in the INI directory, but then not taken into account in relation to the GUI if it is not in the program directory? The mechanism is somehow unclear to me. Unfortunately, I cannot move the "totalcmd" program folder as I wish as I do not have admin rights on the computer.

[AntonyD]

2praetor
make portable TotalCMD setup . and copy all files into your personal folder.
BUT first of all try all things on your home computer - where you DO have all rights.

[Samuel]

There are 2 separate processes. "tcmatch.dll" the main engine and "tcmatch.exe" the gui, that currently doesn't support a relocated ini file.

[praetor]

.... that currently doesn't support a relocated ini file.

really a shame

[AntonyD]

2praetor
Did you try the portable TotalCmd?

[ghisler(Author)]

There are 2 separate processes. "tcmatch.dll" the main engine and "tcmatch.exe" the gui, that currently doesn't support a relocated ini file.

That really doesn't make sense. Maybe disable the relocated ini when writing to the ini in the program directory is possible?

[igor3v]

I have a problem installing QuickSearch eXtended:
TC 11.02 64 bit is located under c:\program files\totalcmd\
The INI files are in the user path.
I copied all files from QuickSearch eXtended to the program directory.
After restarting the TC, a tcmatch.ini was created in the INI path, as expected.
But when I start the search, the advanced search interface of QuickSearch eXtended doesn't appear! What could be the reason?

I just ran into the same situation with TC 11.03 64-bit and QuickSearch eXtended version 2.3.1 (according to the "tcmatch.pdf" section 5).
It took a couple of hours for me to understand what's going on , but now it perfectly works.

Long story short, the installation steps are:

1. Install the plugin automatically by opening the downloaded zip file from within Total Commander and choosing “yes” in the popup.
   • Provide TC with the elevated access permissions, so that it would be allowed to copy files into "c:\Program Files\totalcmd\", if necessary.
2. Note that the "tcmatch.ini" file ended up in the ini dir (%USRPROFILE%\AppData\Roaming\GHISLER). The "dll" and "exe" files ended up in the exe dir ("c:\Program Files\totalcmd\").
3. Move "tcmatch.ini" to the exe dir ("c:\Program Files\totalcmd\").
4. To be able to modify the settings stored in the "tcmatch.ini" using the "QuickSearch eXtended" UI, provide yourself with the Full access permissions to the "tcmatch.ini" file (using the Windows file properties dialog).
5. Restart TC.
6. Remember that "QuickSearch eXtended" panel might not be shown immediately after you click CTRL+S, you might need to start typing for it to show up. Before that, the quick search panel would look just like the plain built-in quick search panel.

Before I got to that, I tried a whole bunch of unnecessary/ineffective steps:

1. I tried installing the plugin manually (by unpacking the zip file to the "c:\Program Files\totalcmd\").
2. At some point, I noticed that Windows file properties dialog for all the "tcmatch*.*" files shows the "Unblock" dialog box (the one you commonly get for the downloaded files). This probably happened after I tried to install the plugin manually by unpacking the downloaded zip file. I had to unblock each file manually.
3. I've noticed that I can manually start "tcmatch64.exe" from within TC x64, and "minimize" the settings UI. With that, "tcmatch64.exe" keeps running, and CTRL+S works as expected. The "System informer" shows that the "tcmatch64.dll" module is now loaded into "Totalcmd64.exe". But:
   • The icons of the buttons are missing (the buttons are plain gray). I'm not sure why, but the issue disappeared later.
   • This only works up until TC restart. After each TC restart, CTRL+S produces the built-in quick search panel again. The "tcmatch64.dll" is not loaded and "tcmatch64.exe" is not running.
4. I provided myself with the full read-write permissions for the entire "c:\Program Files\totalcmd\" folder.
5. Following this post (and also this post), I added

   Code: Select all

   tcmatch=c:\Program Files\totalcmd\tcmatch.dll
   tcmatch64=c:\Program Files\totalcmd\tcmatch64.dll
   

   to the [Configuration] section in the "%USERPROFILE%\AppData\Roaming\GHISLER\wincmd.ini" .
6. I tried to catch the moment, when the "tcmatch64.dll" is (not) getting loaded (and/or "tcmatch64.exe"), expecting that this should happen at TC startup. (No, it is not loaded at startup. Not even after you press CTRL+S. Only when you start typing in there.)
7. I've noted that, surprisingly, if I start "tcmatch64.exe" in one TC x64, the CTRL+S starts to work in all new TC instances, even x32.
8. For the TC x64, I also tried some old suggestions to move tcmatch files to ini folder. Nothing really changed.

[Horst.Epp]

Having TC and its plugins installed under Program files creates all sorts of unnecessary permission settings and problems.
Creating a portable version under any normal tree removes all these problems.
Please don't say that this would reduce the security,
If any virus or Trojan can write on your system, it will do so regardless of the locations.

[igor3v]

2Horst.Epp,
Well, the issues I was experiencing are not related to the permissions (personally, I was mostly stuck with the very last point).

I mentioned the "installation step" about providing the R/W permissions for the "tcmatch.ini" just as a reminder for the people to do this, if necessary.
Because many people do install TC to a Read-Only folder, regardless of whether this is a good or a bad idea...

[Christo]

Long story short, the installation steps are:
[*]Move "tcmatch.ini" to the exe dir ("c:\Program Files\totalcmd\").
[*]To be able to modify the settings stored in the "tcmatch.ini" using the "QuickSearch eXtended" UI, provide yourself with the Full access permissions to the "tcmatch.ini" file (using the Windows file properties dialog).

Thanks for your advice.