New: HomeBank (Sep 03, 2023), Platform 26.2.1 (Sep 17, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Jack Haller, Advisor and Father of Our Founder, Has Passed Away
Welcome PortableApps.com 
I found a little bug.
The settings are stored in the file \PeaZipPortable\App\peazip\res\conf.txt and not in the Data folder.
Solution: Delete this file.
Furthermore the file \PeaZipPortable\App\peazip\res\rnd should be moved to the Data folder, because this file and the conf.txt are changed at the same time.
BTW the file \PeaZipPortable\App\peazip\res\empty.fnd is unnecessary.
Cheers, a new fan.
Good catch. Looks like I forgot to delete the default conf.txt file before posting this package.
Fix posted here: https://portableapps.com/node/14733
Thanks!
But i can´t test it. I have a very slow internet connection at the moment.
Hi, empty.fnd should not be deleted, it is invoked when using "search and drag here" functions.
It is a Windows .fnd file, triggering the system to open the search system's dialog (from which files and folders can be dragged to PeaZip, i.e. to populate an archive's layout); it is empty (0 B) as it starts search form without any filter applied (on path, name, extension, date, size etc).
Search dialog could be called in other ways, but I chose to use a .fnd file since an advanced user could like to customize it to pass search parameters to the search form, which would not be feasible/practical if I made PeaZip to invoke the search dialog in other ways.
Thanks for clarification. I thought empty.fnd doesn't belong to Peazip. But I'm not the dev 
Keep up the good work!
Thanks for clarifying. The only change I made to my launcher was to fix the conf.txt issue the OP mentioned.
As long as you're here, would it be possible to add a command line parameter to PeaZip to tell it where to look for the settings file?
I think I could make the executable to parse parameters to get the conf.txt's path, but I have to think a bit about how to integrate it in current startup procedure since PeaZip jet parses parameters to point to internal functions (i.e. peazip -ext2here file.ext file2.ext extracts file.ext and file2.ext in their respective directories without needing further interaction) to allow scripting, and with the same mechanism it allows internal functions to be reachable from registry and links (i.e. SendTo) in Windows and .desktop files for Konqueror's and Nautilus menus in Linux.
About rnd file, I would let it in the executable's path rather than in configuration's path, it's just 256 bit of persistent randomess collection updated at each iteration of PeaZip and Pea executables.
thanks. if you figure it out, that'll be great.
i'll leave the rnd file where it is.
thanks for such a great app, and your willingness to work with our community to improve it
PortableApps's applications were so often lifesavers for me and for many people who asked me help that I'm very glad to do something for this community!
I fixed the configuration problem for the upcoming 2.2 version.
I found quite unpractical declaring configuration path as parameter when launching PeaZip, so I used a file (altconf.txt) in res folder to declare an alternative location (absolute path or, more useful for PortableApps purpose, relative path) to store all files which needs to be accessed for reading/writing.
In this way all invariant data (binaries, graphic, language files etc) which is accessed only for reading during normal program's usage can be stored in program's path, which so may be even set read-only.
All variable data files (conf.txt, rnd, and bookmarks.txt, PeaZip 2.2 will support bookmarking archives and folders) which can need to be accessed for writing during normal program's usage will be stored in res folder by default, unless differently specified in altconf.txt, which can be changed only once when building the software's package.
In example, to store configuration in PeaZipPortable\App\DefaultData\settings, the second line of altconf.txt will become ..\DefaultData\settings
Or, to store configuration in PeaZipPortable\Data\settings, the relative path will be declared as ..\..\Data\settings
PortableApps' laucher application will not need to be changed, and of course the user may decide in any moment to customize the configuration path (or to keep alternative configuration files) just editing the altconf.txt file.
thanks looking forward to the new release
Visit the Community page
Join our forums
Follow us on BlueSky