I came upon and d/l xnview (newest version) because of its powerful image conversion options. After much stumbling around I managed to actually convert several images. When I tried some more today the program showed NO formats to convert to. Reinstall did not help. D/Led Xnconvert since mostly want to convert images. Could not figure out wha tto do with unzipped files. Ran XnVview uninstall from explorer window. Noticed that .ini file did not uninstall. Edited .ini file noting that all convert file types set to zero. Set gif type to 1 and reinstalled. Convert option allowed gif output option. Deleted .ini. Reinstalled and saved new ini for safe keeping.
The problems:
1. .ini file NOT uninstalled (probably because not part of install process.
2. All file types in .ini file set to zero and reassociating file within XnView did not overwite. I probably caused this by messing with program options but could not recover.
3. No clue as to how to install and use XnConvert.
Jer
Corrupt ini file
Moderators: helmut, XnTriq, xnview
Re: Corrupt ini file
Jer et al,
thank you for your long description and problem list. Some comments:
The settings in the .ini file have nothing to do with the file associations. Have a look at options, category "File types", that's the settings you have changed when editing the .ini file.
Jer, please slow down a bit: Downloading and installing software can be done quickly. But you should not expect that all applications open up with a nice and friendly wizard asking you what they can do for you. Please have a look at the posts here, have a look at the Rules and Guidelines of this board, have a look at XnView and take your time to learn how things work.
Regards,
Helmut
thank you for your long description and problem list. Some comments:
The two .ini files 'xnview.ini' and 'bookmark.ini' which are used to store the settings and the bookmarks of XnView, are indeed not part of of the installation and deinstallation. This is on purpose since many people update XnView by uninstalling a version and then installing the new version. Since all those people shouldn't loose their settings, we decided to exclude these two files. Sure enough, the deinstallation routine could be smarter and ask the user whether he/she wants to uninstall the .ini files and default to 'Do not uninstall .ini files', too, but this has not been done, yet.Jer wrote: ...
1. .ini file NOT uninstalled (probably because not part of install process.
When exiting XnView, it writes a complete new .ini file. Editing .ini files can be done, but when doing so each user should know what he/she does and it's at own risk. Normally XnView is forgiving, looks as if in your case you made a setting that XnView really didn't like and therefore GPFed at start-up.Jer wrote:2. All file types in .ini file set to zero and reassociating file within XnView did not overwite. I probably caused this by messing with program options but could not recover.
The settings in the .ini file have nothing to do with the file associations. Have a look at options, category "File types", that's the settings you have changed when editing the .ini file.
XnView allows multi conversion, too, so for most purposes XnView is sufficient and you will not need nconvert. nconvert is for DOS scripting and batch conversion of images. You can call nconvert using the command shell or write batch scripts. Please lookup the group 'nconvert' or the web to learn more about command shells and batch scripting.Jer wrote:3. No clue as to how to install and use XnConvert.
Jer, please slow down a bit: Downloading and installing software can be done quickly. But you should not expect that all applications open up with a nice and friendly wizard asking you what they can do for you. Please have a look at the posts here, have a look at the Rules and Guidelines of this board, have a look at XnView and take your time to learn how things work.
Regards,
Helmut