XnView Software

Hi
Could it be made 100% portable? Without leaving files folder or registry key?

Just because i have problem at home, but i like to have on my usb stick, and at work is different.

Would be amazing full portable, xnview mp is a beautiful software but leaves registry keys, trolltech junk keyd and other keys in the registry.

Running XnView MP 0.98.4 64bit on w10 and 7 64bit

Thanks

drugo wrote: Mon Aug 02, 2021 2:19 pm
Would be amazing full portable, xnview mp is a beautiful software but leaves registry keys, trolltech junk keyd and other keys in the registry.

when using .ini?

xnview wrote: Tue Aug 03, 2021 2:29 pm

drugo wrote: Mon Aug 02, 2021 2:19 pm
Would be amazing full portable, xnview mp is a beautiful software but leaves registry keys, trolltech junk keyd and other keys in the registry.

when using .ini?

hi
yes , i use ini

which keys do you have?

AFAIK the portable version is totally portable. HOWEVER when I moved to the portable version there were left over registry keys which I hunted out of the registry
Next I made a settings folder inside of the portable version to hold the ini file and the thumbs database and all that sort of thing then a "batch" folder to hold my batch renaming configurations. Then open the portable program and adjust the locations. Then close the program and move the old database and ini file into the portable prog folder then restart and you are good to go

@Pierre

Could the ZIP download default ini and similar file locations be set to Program (XnView) for immediate full portability without configuration?

Or would that be too difficult for you?

i don't think that's a good idea to put a .ini for the ZIP package, but perhaps add a ZIP (portable version) with a basic .ini?

xnview wrote: Thu Aug 05, 2021 10:33 am i don't think that's a good idea to put a .ini for the ZIP package, but perhaps add a ZIP (portable version) with a basic .ini?

I didn't express that very well, possibly an editing error:

What I was thinking was for the default locations for the ini and similar files to be set to Program (XnView) rather than to User (System), so that the portable version would be fully portable immediately.

That would avoid users having to change the locations, and quite possibly not knowing that is necessary for full portability...

Would that create a problem for you?

cday wrote: Thu Aug 05, 2021 10:55 am What I was thinking was for the default locations for the ini and similar files to be set to Program (XnView) rather than to User (System), so that the portable version would be fully portable immediately.

That would avoid users having to change the locations, and quite possibly not knowing that is necessary for full portability...

Would that create a problem for you?

The only way is with .ini

I just discovered XnView while looking for a fully portable FOSS image viewer for Windows. So even with the .zip version, when I first run it, it will still create registry keys and use default Windows file locations? The whole point of being portable is specifically to not do that. Creating registry keys before you can "set" the app to portable is counter-productive. I don't see why it's a problem to package a basic .ini in a zip specifically labeled as portable, or provide a link to a portable .ini with a note telling users to download the .ini and stick it in the XnViewMP dir before running XnView. You should never have to clean up registry keys and files from system dirs using a portable app.

So, what exact hoops do I currently have to jump through to make XnView fully portable? Just creating an empty .ini before ever running the .exe?

xnview wrote: Wed Aug 04, 2021 7:52 amwhich keys do you have?

On my old XP SP3 box:

XnTriq wrote: Sat Apr 25, 2015 8:45 pm

• Files/folders
  • %AppData%\XnViewMP\
  • %TEMP%\par-{username}\cache-exiftool-{version}\*.* (Installing ExifTool » Windows » Uninstalling)
  • %TEMP%\qtsingleapp-xnview-????-0-lockfile (Qt)
• Registry
  • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\xnview.exe
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\xnview.exe
  • HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications » XnViewMP
  • HKEY_LOCAL_MACHINE\SOFTWARE\XnViewMP
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.bmp
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.cr2
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.crw
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.dds
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.gif
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.iff
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.img
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jif
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jp2
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jpc
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jpe
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jpeg
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.jpg
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.nef
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.pbm
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.pcd
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.pcx
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.pgm
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.pic
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.png
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.ppm
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.psd
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.raf
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.ras
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.rle
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.tga
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.tif
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.tiff
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.xbm
  • HKEY_CURRENT_USER\Software\Classes\XnViewMP.xpm
  • HKEY_CURRENT_USER\Software\kde.org\libphonon (Qt)
  • HKEY_CURRENT_USER\Software\QtProject (Qt)
  • HKEY_CURRENT_USER\Software\Trolltech (Qt)
  • HKEY_CURRENT_USER\Software\XnView\XnViewMP