As qBittorrentPortable.ini shows, qBittorent Portable is all over the registry and app data folders, not to mention a whole custom code in custom.nsh.
That's a lot of writes which are not needed since qBittorent has an official portable mode which can also be achieved with a command line parameter and/or an environmental variable (see both here). It's also mentioned here.
So there are 3 ways to activate portable mode, why not using any of them?
In addition, it includes in vain a folder called $PLUGINDIR.
This might also apply to qBittorrent Enhanced Portable, and might solve issues like this and that.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
there are many levels of portability.
john makes real portable apps.
if he would use it it would be not full portable.
that's what i figured out.
the settings problem is not only here.
i have a port app from developer, same problem.
i help out but get ignored and bullied here.
hopefully i'm not making very bad at the moment.
we need here slowly a not mobing hint.
edit:
one can get here mental problems, don't let get bullied.
fight against bulling!
i help were i can. maybe you can help me too. threads in account/track.
if you don't want to help don't post crap!
qBittorrent Portable Enhanced has used the -profile command line switch from the beginning. qBittorrent Portable does as of a recent release. That doesn't make qBittorrent fully portable though.
You're welcome to use the standard ZIP version from the publisher with the PA.c Platform if you want to directly associate it with files, you just lose out on automatic updates and stuff.
Sometimes, the impossible can become possible, if you're awesome!
Officially this switch is only for Linux. Why not using one of the methods mentioned in the OP?
Using those methods it seems none of the keys mentioned in [RegistryKeys] of qBittorrentPortable.ini exist in my standard ZIP version, not even HKLM\SOFTWARE\Microsoft\ESENT itself.
As for custom.nsh it checks that "a second instance of qBittorrent doesn't occur". But since it was there before using "-profile" are you sure it's still needed?
Plus it seems to fix something about qBittorent's automated translation, but I'm not sure why.
The -profile switch works the same way as the environment variable. The registry keys used to still be created at some point. Hopefully they don't know as that would simply things.
Using the -profile switch rather than the profile directory means that it can stay within qBittorrentPortable\Data so it doesn't have to be moved back and forth. Data needs to stay in Data for PA.c Platform backups and for better PA.c Installer upgrades.
The custom.nsh makes sure we're using the system TEMP. This is in case you're running it from the PA.c Platform with a contained TEMP directory on your drive. Or something similar from another menu launcher app. Otherwise, qBittorrent doesn't handle secondary launches properly and will result in a second instance. It also handles portablizing drive letters within qBittorrent-resume.ini so things will keep moving as your drive moves computers. I'm going to expand that to full paths in a later release when I have the time.
What's the translation issue you're referring to?
Sometimes, the impossible can become possible, if you're awesome!
Followed by many other languages.
As for secondary launches with alternate %TEMP% it might be worth it to try again. Maybe it's no longer an issue just like those registry keys.
Seems the old language hack is no longer needed so that'll be gone in the next release.
The TEMP code will only be used when the end user has specifically configured the PA.c Platform to use a custom contained TEMP directory on the same drive as the PA.c Platform. If you haven't done this, it isn't activated.
Sometimes, the impossible can become possible, if you're awesome!