Sorry for reviving this post, but I think it's the best place for my question.
I have TC ini files in program directory, and I sometimes call SALister with its own ini file in its own directory.
SALister version 6.5 reads lsplugin.ini from the same directory as lister.ini in SALister directory.
SALister version 7 creates its own lsplugin.ini in Windows directory.
¿Is there a way to tell SALister 7 that it must use lsplugin.ini from its own directory?
i am a newbie, and i speak spanish; thanks for your patience.
What about facinlaburo's questions on the INI files used by the standalone liste v7?
To the best of my knowledge - i.e. I may be wrong - standalone lister has always tried to create and use a wincmd.ini in the %windir% folder.
(The little biest can no longer do so on Vista and above, because I refuse to run T.C. or lister elevated by default.)
I have never seen lister.exe create or use an infi-file named lsplugin.ini.
To the best of my knowledge - i.e. I may be wrong - the only way of making lister.exe use a particular ini-file is by passing its path and name on the commandline:
I have never seen lister.exe create or use an infi-file named lsplugin.ini.
Install for example SVG viewer plugin in SALister - then a lsplugin.ini will be created in the default ini directorty for your OS (c:\windows dir for Windows XP).
And I can't get it to put it anywhere else.
The little biest can no longer do so on Vista and above
I'll check that tomorrow on Win 7
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14 TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Thanks for the answers. I'll try to explain with more detail.
The plugins I use in SALister are Imagine, Multimedia Factory, Font, PEViewer, SumatraPDF and Syn.
Font, PEViewer and SumatraPDF creates their own sections in lsplugin.ini.
My lsplugin.ini for TC is in program directory.
My lsplugin.ini for SALister (options are different from TC's one) is in SALister directory. SALister 6.5 reads it OK without any parameter, but SALister 7 doesn't recognize it and creates a new lsplugin.ini in Windows directory.
I wonder if there is a way to tell SALister 7 that it must read lsplugin.ini from its own directory, as 6.5 does. The info file (lister.txt) doesn't say anything about it.
All this on XP SP3.
i am a newbie, and i speak spanish; thanks for your patience.
Creating files in %windir% on Vista, Windows 7 and Server 2008 (R2): provided you are using the default UAC settings and provided you launch lister.exe un-elevated, it cannot write to its favourite %windir%\wincmd.ini. (To the best of my knowledge - but who is going to depend on it? )
Oh, your initial explanation of the problem was clear enough. But thanks for explaining once more nevertheless.
It was just me starting to confuse things a bit.
One source of trouble is that lister.txt which comes with lister.exe really is not too precise on where lister.exe will create/expect the file wincmd.ini and it does not mention lsplugin.ini at all.
I should have added at least one plugin to my lister.exe and find out what lister.exe v7 does before writing a not so helpful reply.
Hello, karlchen.
lsplugin.ini is a file that contains settings for some lister plugins. It's created in same directory as wincmd.ini
The file doesn't exist if you're not using a plugin that needs to store its settings. Examples of plugins that stores its settings there are Font, SumatraPDF and PEViewer.
AFAIK, the logical behaviour would be that if SALister uses lister.ini instead of wincmd.ini then it would use its own lsplugin.ini (version 6.5 behaves so). I couldn't manage version 7 to do the same thing.
Got you thinking
PD: I'm doing all this with administrator privileges.
i am a newbie, and i speak spanish; thanks for your patience.
I you start TC with the /S=L parameter and use an ini-file in a separate directory (not TC's directory) - then TC will start Lister as standalone - AND it will make and use lsplugin.ini in the same directory as the main ini file.
This way I don't need SALister anymore, I just use internal lister as SALister, with the advantage of having the latest version.
I made a Start Menu entry for my needs -and use it with a hotkey-, that looks like this (just for anyone that may have similar interest):
)
