XnView Software

Hello, I found that can not save my own configuration for Xnview(I use Win8.1 x86 system).

It can be seen the effects after saved the options, but when you closed the software and turn it again(Such as open a photo later).
All the configurations were turned back to be default, you had better change it again, however this problem still here.

Thanks for fixing it.

march2nd wrote:I ... can not save my own configuration for Xnview (I use Win8.1 x86 system).

Possibly a UAC problem?

Could you try launching XnView with Admin rights and check if your configuration is saved?

If launching with Admin rights works, you could then try changing the following setting and check if your configuration is saved when you launch XnView from a User account:

Tools > Options -- System integration -- Integration tab -- Save options : 'As INI in folder -- User'

same thing for me with the last version.

I had to downgrad to 2.05 version , every thing then is correct ( Windows 7 - 64)

[Deleted]

I don't see any problem on my Windows 7 SP1 x64 system:

o XnView 2.20 Minimal, Standard and Extended installed in turn from a user account with a UAC prompt for the Admin password...

o Each version run from a user account...

o All ini file locations tested for Standard version: configuration changes written correctly even for the ini located in the Registry when being run from a user account...

But for the Standard version, which launches first time with a Configuration wizard, changing the ini location in Tools > Options... results in the Configuration wizard running again next time the program is launched, and the possibility of creating a new ini file, resulting in the previous settings being lost.

where is saved your xnview.ini?

Yet didn't try latest but version 2.13 / Windows 7 works fine as long as the option to store XnView.ini is set to "User". The issue is where the option is set to either "XnView" or "Windows" and users do not have admin-rights on the system. These options should allow all users of the system to share the same features / setup of XnView but in either case the .ini file become read-only

Suggestion: As the Windows directory is protected, why not using C:\ProgramData?
This is the equiv. to "All Users\Application Data" in Windows XP and many programs uses it to store the config files that are common to all users, including those with limited rights

Note: It's the same with XnView MP so please to improve both builds.

Developers used to build and test software on their machine with admin rights. Also, many users of XnView installed it on their private PC / single user having admin rights. In this context, a system prompt to confirm access to a protected file (xnview.ini) is not a big deal. It's different when users have standard user's rights: All members of a family or a laptop for mixed private and professional use: In hese contexts,entering the admin password is not an option.

Using the binaries repositories to store user's configuration is an outdated design. The options for Integration should be "Individual User" (by default) or "Shared all Users" (common setup for all users). There is no need for a 3rd option: If an administrator would like to forbid/restrict changes of the .ini file he has got all the tools from the system to do so.

I made a suggestion here already: http://newsgroup.xnview.com/viewtopic.php?f=17&t=1547.