FreeCommander Forum

Hi, thanks for your program - it looks like the best free file manager choice for me. Now about a bug.

No matter which FreeCommander.ini location you set in options, it still tries to create and use FreeCommander.ini in its install folder. And as long as this folder's owner is set to TrustedInstaller (or something) and default user rights are set to 'Read/Execute', creating or writing files is impossible, so FreeCommander cannot save its settings.

I created that file and made it fully availaible for all users, but this (as any other) is a "dirty" way, which should be fixed.

Thanks for your attention, and again, for your software

I would prefer to have the option to specify that the INI should be stored WITH THE INSTALL of the actual application.

I'm a single user on my PC and I don't want to fuss with all that "roaming profile" and multi-identity stuff.

I really like having one single INI that is in the same folder as the one single EXE that I use to start Free Commander.

So, I hope they never take away that option.

Bearded Kirklander wrote:I would prefer to have the option to specify that the INI should be stored WITH THE INSTALL of the actual application.

I'm a single user on my PC and I don't want to fuss with all that "roaming profile" and multi-identity stuff.

I really like having one single INI that is in the same folder as the one single EXE that I use to start Free Commander.

So, I hope they never take away that option.

Well, it means that in Windows 7 (and I think in Vista too) you should mess with user rights instead.

Not having had much access to Vista (I refuse to install it) I may find myself in deep water.

That being said, I did use it in a work environment for a few months and found the Run As.. option to get around most issues. Here is what I would do:

1. Use Explorer to go to the FC install directory.
2. Right click Freecommander.exe and select Run As..
3. Provide admin password.
4. Change the option to store the ini file in the users folder.
5. Save settings and exit FC.
6. Test by running FC as you usually would.