I'm back with the question of the actual path used by the system (Windows 7 as an example). I put a message some time ago but apparently it didn't triggered that much attention. Further comments were posted with information not verified, assuming that nothing have changed in the Windows world
Unless you have an administrator account (Superuser in Unix world) , the current choice, where to store the XnView configuration file is virtual and drive to the same result: It's always in the user profile folder
This is because from Windows Vista all write tentative to System and Program folders is refused,
limited to read only for normal users (as Unix always did). To preserve compatibility with old programs it creates virtual links to specific folders that emulates these now restricted folders, keeping r/w access. These new folders are in the individual user profile. See below:
Setting: .ini in directory User
About says "C:\Users\
[username]\AppData\Roaming\XnView\xnview.ini"
Actual location "c:\Users\
[username]\AppData\Roaming\XnView" that's correct
Setting: .ini in directory Windows
About says "C:\windows\xnview.ini"
Have a look, you'll never find the .ini file here
Actual location "c:\Users\
[username]\AppData\Local\
VirtualStore\Windows"
emulation not sharable
Setting: .ini in directory XnView
About says "C:\Program Files\XnView\xnview.ini"
Have a look, you'll never find the .ini file here
Actual location "c:\Users\
[username]\AppData\Local\
VirtualStore\Program Files\XnView"
emulation not sharable
Currently, the 3 options available are all equivalent and finally doesn't allow to share settings between users. I suggest that we keep 2 options only:
XnView.ini in the User directory for individual preferences (actual path = %APPDATA%\XnView as for now)
XnView.ini in All users directory to share preferences between users (actual path = %ALLUSERSPROFILE%\XnView)