Slow search dialog opening

[eRIZ]

Hi!

When I've been using the TC in 6.xx version, the search dialog was showing almost immediately after ALT+F7.

Now, it takes much more time...

Could the Author correct it?

[karlchen]

Hello, eRIZ.

When I've been using the TC in 6.xx version, the search dialog was showing almost immediately after ALT+F7.
Now, it takes much more time...

Cannot confirm this based on what I see on the machines which I have got access to: Alt+F7 will launch the search dialogue immediately on T.C. 7.02a as well.

Windows platforms used: Win2K Sp4 Rollup1, Win2003 Std Sp1+Sp2, Windows XP Sp1+Sp2, Windows Vista Home Premium (all 32bit versions).

Could the Author correct it?

Cannot answer this question, as it seems that this is not a general problem. Maybe if you can provide more details on your system environment this will help locate the source of your problem.

Regards,
Karl

[eRIZ]

Hmm, Windows XP SP2 and Total Commander 7.02a. 2GB RAM, 1.6GHz CPU.

May it depend on installed plugins?

[karlchen]

May it depend on installed plugins?

Maybe.
If you wish to find out quickly then you might launch T.C. like this and then launch Alt+F7:

Code: Select all

<path_to>\totalcmd.exe /n /I=.\fresh.ini

This will load a new T.C. instance using the non-existant and therefore empty INI file fresh.ini. No plugins will be loaded. So if Alt-F7 will load the search dialogue quickly now, then chances are one of the installed plugins is to be blamed.

Karl

[eRIZ]

I've checked with clean INI. And there is a difference...

With clean INI, search dialog appears quicker than with mine one.

[karlchen]

Hi, eRIZ.

This reads as if the tedious way to solving your problem may work like this:
+ Using the fresh "fresh.ini" re-install one plugin at a time.
+ Check how fast Alt-F7 will be launched.
+ If the problem re-appears, the plugin which has been re-activated last may be to be blamed.

Or the other way round:
+ Use your normal TC INI-file.
+ De-activate one plugin at a time.
+ Check how fast Alt-F7 will be launched.
+ If the problem disappears, the plugin which has been de-activated last may be to be blamed.

Karl