XYplorer Beta Club

When updating a portable installation that contains no startup.ini file, the XYplorer installer recreates startup.ini, which moves the program's appdata path. Instead, the updating process should not create or modify startup.ini if XYplorer already exists.

As a workaround, instead of deleting startup.ini as directed, I keep startup.ini but modify its Appdata section to point to the correct path.

Wouldn't updating a portable installation rather be done by extracting the content of the new versions zip file to the existing directory, thus not creating the problem you describe?
Using an installer to create a portable version seems a bit awkward to me.

Your no-installer method is likely more common for portable installations, but unlike most programs' installers, XYplorer's installer is designed to accommodate portable installations as well as the standard ones. As such, it should avoid breaking them!

it's portable. it does not care whether you install into bjdki\jfkbur\dbf or what
install manually. just unpack and replace what you need

mikeyww wrote: ↑13 Mar 2019 03:00 When updating a portable installation that contains no startup.ini file, the XYplorer installer recreates startup.ini, which moves the program's appdata path.

Cannot confirm. No startup.ini created on self-updating a portable installation. (Has been fixed in v17.30.0205 - 2016-11-19 12:58)

Had you already deleted startup.ini before the update? That is when the issue arises. Steps are below.

1. Delete startup.ini from your portable installation.
2. Run the installer to update your portable installation.
3. Notice that a new default startup.ini file was just created.

As noted, above, step #1 is actually recommended for portable installations, but also see there for my workaround.

Use self-updating. It's much easier than via installer and does not have that problem.

I have no difficulty getting the program installed and working for me. I do still suggest that this is a bug in the installer and so should be fixed.

Agreed. Will be handled in next version.

Thank you!