743 - Custom ini path and fcStart.ini conflict

Discussion and questions - donor version.
Post Reply
Message
Author
User avatar
Dreamer
Site Admin
Posts: 3137
Joined: 19.08.2007, 21:40
Location: Slovakia

743 - Custom ini path and fcStart.ini conflict

#1 Post by Dreamer » 02.04.2017, 17:59

- In Settings > start program > configuration folder > select "Following folder" option
- add custom path, e.g. "C:\abc\FreeCommander\Settings"
- close FC
- download and update installation by unpacking the files from the zip file
- start FC
= default settings are used and saved to install FC folder

I'd like to use a custom path for Settings, the problem is fcStart.ini file.

How to solve this problem:

1. (Workaround) unselect fcStart.ini file every time FC is updated/unpacked from zip file.

2. Another start ini file with higher priority than fcStart.ini

3. Don't include the fcStart.ini in the future install zip files.

User avatar
Dreamer
Site Admin
Posts: 3137
Joined: 19.08.2007, 21:40
Location: Slovakia

Re: 743 - Custom ini path and fcStart.ini conflict

#2 Post by Dreamer » 24.08.2017, 22:01

I found a bit better workaround.

Change the attribute of the file fcStart.ini to "Read-only".

When you unpack/copy the new portable version, and you forget to unselect this file, confirmation dialog will be displayed.

BTW how is it working in the setup version, when you use a custom path for settings folder, and you update/install new version? If the file fcStart.ini is replaced, custom path can't be used - is it a bug, or is it working different?

Marek
Author
Author
Posts: 2212
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: 743 - Custom ini path and fcStart.ini conflict

#3 Post by Marek » 25.08.2017, 16:32

Setup does not contain fcStart.ini.
The file is created in FC if needed (when the user change the settings folder).

Your idea is good. I have set "Read-only" for fcStart.ini in the zip file.

User avatar
Dreamer
Site Admin
Posts: 3137
Joined: 19.08.2007, 21:40
Location: Slovakia

Re: 743 - Custom ini path and fcStart.ini conflict

#4 Post by Dreamer » 25.08.2017, 18:29

Marek wrote:
25.08.2017, 16:32
Setup does not contain fcStart.ini.
The file is created in FC if needed (when the user change the settings folder).
Why it can't work the same with portable version?
Marek wrote:
25.08.2017, 16:32
Your idea is good. I have set "Read-only" for fcStart.ini in the zip file.
It doesn't work this way, existing file must be read-only, otherwise confirmation dialog is not shown.

BTW user have to change the settings folder location in Settings first, and then change the attribute to read-only, otherwise it's not possible to change the folder location in Settings. It's just a workaround for users who are already using custom path and it's not perfect, because there is one confirm dialog for other files, then another dialog for read-only file, so they must click "overwrite all" and then click "no" or "skip" for the read-only ini file, it's still better to unselect the file every time and use this just as "backup".

Marek
Author
Author
Posts: 2212
Joined: 10.04.2006, 07:48
Location: Germany
Contact:

Re: 743 - Custom ini path and fcStart.ini conflict

#5 Post by Marek » 25.08.2017, 20:22

Why it can't work the same with portable version?
We have only one freecommander.exe version for portable and setup.
It doesn't work this way, existing file must be read-only, otherwise confirmation dialog is not shown.
Yes, the file fcStart.ini has now the attribute "Read-only" in the zip file and after unpack too.
BTW user have to change the settings folder location in Settings first, and then change the attribute to read-only, otherwise it's not possible to change the folder location in Settings.
I have already changed it for the next release. The user can change the settings if the file fcStart.ini is readonly.

User avatar
Dreamer
Site Admin
Posts: 3137
Joined: 19.08.2007, 21:40
Location: Slovakia

Re: 743 - Custom ini path and fcStart.ini conflict

#6 Post by Dreamer » 25.08.2017, 23:04

OK, I'm thinking about some workaround, even some automation of installation.

New FC file is downloaded in the same folder, just the file name is different, but perhaps it might be possible, somehow, to create some .bat file, to unpack all files except the fcStart.ini to target folder, automatically? Even using FC, or 7Zip - using the command line parameters?

Or the setup version of the FC with the command line parameters to install automatically, silent mode? But the setup version must be unpacked too...

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest