FreeCommander Forum

On my flash drive I want to run a portable copy of FreeCommanderXE. But I need to have both the 32bit and 64bit versions in case I have to use a 32 bit OS.

So I put the files from both zip distributions into the same folder.

My problem is that since I have two FCXE executables, I have to rename one of them in order to keep them in the same folder.
But that causes two FreeCommander.ini files to be made.
And I want to use the same settings.

How can I tell FC to use a custom ini file?

Command line parameters

/Ini=Starts FC with a different INI file instead of freecommander.ini.
A new file will be created only if the defined file does not exist.
/NewIni=Starts FC with a different INI file instead of freecommander.ini.
A new file will always be created. If the defined file exists, it will be deleted first.

That means I'd have to always launch FC from a shortcut in order to add the parameter.

I was hoping there might be a hidden option in the fcStart.ini file to specify which settings file to use. Marek?

There is no hidden option currently.

Marek - okay, thanks for answering.

Why not to create separate 32/64bit version as it is done in Total Commander?
- 32 bit only
- 64 bit only
- 32/64bit

Timon, because then the changes are not replicated unless I do it manually.
I want one settings file to rule them all.

So I suggested (to Marek) to make one more 'combined' 32+64bit version (in 1 installer) that would use the same settings regardless what version (32 or 64 bit) you are running.

+1 I think that is a good idea.

Maybe the combined setup is only necessary for the portable version.

I just set the settings folder path for the 32 bit test version to be the same as my main 64 bit version in Settings/Start program/Configuration folder/Following folder (relative paths are accepted).

Joby, you're missing the clencher.
That works just fine for the *folder*
but to have both FreeCommander 64 and 32 in the same directory, you have to rename one.
Then FC will create an ini file with the same name as the executable.
Which means you get two ini files = two settings files.

I keep them in separate directories, side by side. The 32 bit XE uses the 64 bit settings, because my fcStart.ini file stores that settings folder path. There is no Settings folder in my 32 bit XE.

oooooooohhhhh

I get it!
That way the executables can both have the same name and therefore can have the same ini file name.

That's actually rather clever. I feel kind of dumb that I didn't think of it, seeing as how I think of myself also as clever... haha

Thanks for that!

For anyone bumping into this thread and looking for a visual aid, here is a nice setup for 32 and 64 bit XE using the same settings (and portable):

- folder structure:





- both fcStart.ini files look like this (and may/should be edited prior to XE launch):



- settings (no need to change if you edited both fcStart.ini files first):



Note: Of course, one can go even further and use a batch file, compiled .ahk script, or apps like yaP (free, small and very good) to create a launcher for the corresponding XE version for the current OS.

My yaP example (I renamed yaP.exe and yaP.ini to FreeCommanderPortable.exe and FreeCommanderPortable.ini respectively):



Config .ini file (only the relevant part, the rest being identical to the offered example config):

Same ini for 32 and 64-bit FCXE only works if you don't use different wlx-plugins for lister or packer addons.

e.g. ulister.wlx64 for 64-bit and ulister.wlx for 32-bit FreeCommander.